Cursor API for Sequential Storage #11
Merged
Conversation
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
hkimura
added a commit
that referenced
this pull request
May 28, 2015
Cursor API for Sequential Storage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
API, Implementation, and Testcases for one of the critical missing feature; scan for sequential storage. Before this merge, there was only an internal hacky methods to read appended records in sequential storage.
Although this merge passes testcases, there is one TODO.
It has only OCC option for serializable xcts reading tail of each volatile linked-list.
This could cause lots of aborts. We should consider locking option too.
So far this is enough. Left a TASK comment. later. in beta.