Fix repeated key misses slowing down Version Controlled datasets #1458
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.
🚀 🚀 Pull Request
Checklist:
coverage-rate
upChanges
Closes #1456
New commits were created without a CommitChunkSet (until any new data was added), leading to repeated key misses that slow down iteration. If any data was added to the commit, this wasn't a problem.
This PR changes the logic to create a new empty CommitChunkSet every time a new commit/branch is created, to avoid these repeated key misses. It also tries to fix existing datasets that don't have a CommitChunkSet in any of their commits by adding it (if write access is available).