Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

inability to close WT_CURSORs might impact performance for new iterator implementation #79

Open
JackLiJXL opened this issue Jun 17, 2022 · 2 comments
Assignees

Comments

@JackLiJXL
Copy link
Contributor

currently once we get a new iterator for a graph, we do not have a handle for the WT_CURSOR used in graph. This means we can only close the specific WT_CURSOR from the iterator.

@JackLiJXL
Copy link
Contributor Author

right now WT Cursors are not closed when iterators are destroyed, this makes us lose all handles to the cursor

@artorhem
Copy link
Collaborator

Having the cursor tied to the iterator class is by design. We don't want the iterator to access other cursors.

In the future, if a usecase arises where we do need this functionality, we will mark iterator classes as friends.

@artorhem artorhem self-assigned this Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants