Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Coordinates instantiate/close in spatial/temporal indexes
With one-to-one native indexes like number or string, updates or interactions after call to close() is prohibited and coordinated inside GBPTree. With the spatial/temporal index structure, which has lazy instantiation of sub-indexes there was no such coordination. This meant that a call to close() could race with an instantiation of one or more sub-indexes. This in turn would result in opened sub-indexes (GBPTree instances) that would never get closed. Contractually this is very good to tighten up so that they all behave the same. Practically this was found in a population scenario where an index population was cancelled while running.
- Loading branch information
Showing
8 changed files
with
221 additions
and
98 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.