Java API Auto close iterators #13132
Draft
+143
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In an analogous way to owning column family handles, and closing them when the DB itself is closed, we make iterators be “child” objects of the DB.
Iterator lifecycle is generally shorter than DB, so we give them a lambda to remove themselves from the DB on iterator close().
Add tests to check that iterators which remain open when the DB is requested to close, are now closed when the DB is closed.
This fixes #5234