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.
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
Add methods for constructing
LogSegment
for Snapshot and for TableChanges #495Add methods for constructing
LogSegment
for Snapshot and for TableChanges #495Changes from 1 commit
c7913dc
6b331ac
f1f9886
8122113
46185ae
471a858
4ac35da
6297805
e569719
5edf4db
0b8463a
5300a7b
81d0de0
6b85932
1384ea3
0182326
d053a77
52f57e5
aa6c9f4
dca491c
bf5cdd4
748bab9
2a6eb3e
841f17f
1ce29d8
a2f9810
5f7a680
6d8e35f
6b78d56
c959b1d
f121f67
6fbecb7
7338834
362900b
de941f7
8c5a218
a9c529d
5dcff78
ba079e6
ccaed09
62be3d7
d22d661
c7042ce
4b79a33
1a2fcb9
8aec522
d88e31e
4370737
6fccf58
b83c74b
87b3247
83436d2
a7c2461
f7f05f2
11032a5
84027cb
4b7ff17
4c9c96b
a53f38a
b0b6514
5654a6d
2630a9e
db5dddb
6f9b459
a1531ee
33c4039
1f077b0
bee5659
9d0a24f
f8457d9
9c44a69
3a214de
d5adae1
6a5484c
1f5b7f1
669ae84
1fbb563
dd7bd7d
673381f
9873380
b1e12a6
04a7ecf
a16c71c
8cbf2ff
a2ef014
3995579
fc296a4
6926857
e8f3405
f31ec8a
634661a
b94e2dd
ff8ad65
60a8a08
04d2665
2f02d19
38fb7d3
6a7a624
13da708
8d20941
7c45564
1718d85
5819e49
ef28095
e49fdfa
b83dafe
358ed16
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty these used to be sorted in reverse order; did log replay get updated to use a reverse iterator?
(and do we have any tests that could catch such a bug?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update: yes, the action iterator was updated with a
rev
call.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverse iterator is in use. I don't have a test for checking that it's reverse sorted because that would require that we
replay
. This needs a read schema, engine, and some engine data wrangling. This seems out of scope for this PR.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
qq: Would it be more self-describing to call this
ascending_commit_files
?(your call, just a wild late-night idea)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hm I agree more self-describing but knee-jerk reaction is it's generally less readable? no strong opinion