-
Notifications
You must be signed in to change notification settings - Fork 1
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
Replacing collapsing merge tree #7
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
d1 1 5 | ||
d2 1 1 | ||
d3 1 1 | ||
d4 1 3 | ||
d5 1 1 | ||
d6 -1 2 | ||
d1 1 5 | ||
d2 1 1 | ||
d3 1 1 | ||
d4 1 3 | ||
d5 1 1 | ||
d6 -1 2 | ||
d1 1 5 | ||
d2 1 3 | ||
d3 1 3 | ||
d4 1 3 | ||
d5 1 1 | ||
d6 -1 2 |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
CREATE TABLE test (uid String, sign Int8, version UInt32) ENGINE = ReplacingCollapsingMergeTree(sign, version) Order by (uid); | ||
|
||
INSERT INTO test (*) VALUES ('d1', 1, 1), ('d2', 1, 1), ('d6', 1, 1), ('d4', 1, 1), ('d6', -1, 2), ('d3', 1, 1), ('d1', -1, 2), ('d5', 1, 1), ('d4', -1, 2), ('d1', 1, 3), ('d1', -1, 4), ('d4', 1, 3), ('d1', 1, 5); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can we shuffle the input values so that we have:
? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can, I just want to check that if we insert values in "random" order, it doesn't affect the output. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It can still be random, I was just curious about sorting (but it has to work otherwise next tests wouldn't work) |
||
select * from test FINAL; | ||
|
||
-- Test inserting Backup | ||
INSERT INTO test (*) VALUES ('d6', 1, 1), ('d4', 1, 1), ('d6', -1, 2), ('d3', 1, 1), ('d1', -1, 2), ('d5', 1, 1), ('d4', -1, 2); | ||
select * from test FINAL; | ||
|
||
-- test insert second batch with overlaping data | ||
INSERT INTO test (*) VALUES ('d4', 1, 1), ('d6', -1, 2), ('d3', 1, 1), ('d1', -1, 2), ('d5', 1, 1), ('d4', -1, 2), ('d1', 1, 3), ('d1', -1, 4), ('d4', 1, 3), ('d1', 1, 5), ('d2', -1, 2), ('d2', 1, 3), ('d3', -1, 2), ('d3', 1, 3); | ||
select * from test FINAL; |
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.
Why do we have 3 times the same d1?
Why do we have 3 times d2, with different values? etc
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.
This "reference" file is the expected output of the {same name}.sql
If we look at the sql file, we will see 3 calls to
select * from test
; that's why. The three output are following without blank/newline in-between.So you should have 2 times:
and the last insert add overlapping data with new ones, so the output is a little different with
new versions of d2 and d3 are in this new batch.
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.
oh I somehow missed that there're 3 SELECT calls 👍