-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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-20156: To improve accord interoperability test coverage, need to extend the harry model domain to handle more possible CQL states #3844
base: trunk
Are you sure you want to change the base?
Conversation
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.
+1, no blocking comments
* This test exists to help isolate issues with {@link SingleNodeTableWalkTest} and related classes. | ||
*/ | ||
@Ignore | ||
public class RepoTest extends TestBaseImpl |
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 don't see this on cep-15-accord
is it temporary?
} | ||
else if (ctx.eq.keySet().containsAll(factory.partitionColumns)) | ||
{ | ||
// tested |
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.
Are these comments supposed to stay? Are they just tracking what you already wrote tests for?
{ | ||
validate(actual, results.rows); | ||
throw new AssertionError("Unexpected results for query: " + StringUtils.escapeControlChars(select.visit(StandardVisitors.DEBUG).toCQL()), e); |
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.
Should this use the visitor in StatefulASTBase
?
@@ -534,7 +534,7 @@ public boolean allowNonPartitionMultiColumnQuery() | |||
|
|||
private List<Symbol> multiColumnQueryColumns() | |||
{ | |||
List<Symbol> allowedColumns = model.factory.selectionOrder; | |||
List<Symbol> allowedColumns = searchableColumns; |
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 don't quite understand why the number of columns in the partition key determines the usage of selectionOrder
vs nonPartitionColumns
. selectionOrder
is all columns and nonPartitionColumns
I assume the non-pkey columns.
4dc411b
to
95cf28b
Compare
…history on single node
…now show actual as well
…lude partitions with only static rows
…lustering column search happened... regression after unifying search with include
…to static column deletetion
…ally need to make the select/assert logic cleaner
…stream collection, and added a new withTimestamp to add timestamps after the fact
8f893ca
to
08da2d5
Compare
No description provided.