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
CASSANDRA-20460: Expand TableWalk tests to include collections and add support for += and -= for these types #3995
CASSANDRA-20460: Expand TableWalk tests to include collections and add support for += and -= for these types #3995
Changes from 34 commits
21c4f30
d1be462
7982756
e99535a
76dfa34
f5a59c2
75143d2
9f7d6a3
3eb4735
289334d
ae18a84
f358d43
1a32d93
8000bf3
f679856
e2fb393
aaa083d
2c994c9
961f618
7915895
b93943d
42588bd
202ba7a
74e084a
b76f2ba
639427b
2ba8dd0
e475980
ccc8a34
ee6c718
171c41a
9eb86e7
5de3604
fbbdfdd
4dda3e6
44a3f1c
3e1d786
c03ccde
34af875
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.
before we used uniform random so each test had the same weights. Now we select a new distribution for each test run (some tests will only be primitives, others will be mostly maps, 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.
not testing UDT serialization so simple names makes it so much easier to read...
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.
ATM we are not testing nested access (will need to eventually) so lowered as the cql literal output was so large it got hard to read (UDT of map of UDT of map of UDT....)
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.
multi cell collections/udt can not be searched, so just using the non-partition columns wasn't enough
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.
when primary keys can be collections there can be issues with having too many bytes and having our mutations be rejected. Keeping it primitive also improves readability for debug output...
Would be good to have a test that overrides this though, just to improve coverage...
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.
each column will have a different distribution for when operators are allowed
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.
Required for CASSANDRA-20449 repro at least 😄
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.
wasn't required; we hit the issue before this change. This change is to better cover different edge cases
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.
We need different assignment operators to repro (
+= v
vs.= {v}
) but not necessarily different distributions of operators, which is what's introduced here - is that right?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.
added to get clean CI. Something is up with multi column queries that touch both SAI and
vector
type. It doesn't look like thevector
must be indexed to get incorrect results, so doesn't feel like we are selecting a bad index hereThere 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 is extra human readable validation logic.
null
vs<empty>
has been super hard to see from the above output, and the use case i was finding is that we had the correct rows returned, but 1 or more columns had a difference... so if this is the case we try to show which columns are off... this was super useful for detecting consistency issues withnull
and<empty>
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 think Alex created a reusable function for this in accord... would need to find it
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.
eval
is nowNullable
but this code path shouldn't really ever see a null... maybe if you did something like[1] - [1]
then we could get anull
here... mostly added to be correct and defensive (and intellij yelled at me)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.
Curious about the
isFancy
name choosing :-)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 felt it was fancy!