[
https://issues.apache.org/jira/browse/CASSANDRA-18576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730493#comment-17730493
]
Piotr Kolaczkowski edited comment on CASSANDRA-18576 at 6/8/23 10:30 AM:
-------------------------------------------------------------------------
Actually cannot reproduce that with only 2 restrictions and the reproduction on
the ticket was invalid (wrong order of parameters in the execute).
BTW: That does not mean the algorithm for merging the restrictions is correct.
It only means I failed to trigger this with only 2 restrictions on the same
column. ;)
was (Author: pkolaczk):
Actually cannot reproduce that with only 2 restrictions and the reproduction on
the ticket was invalid (wrong order of parameters in the execute).
> Mixed single-column and multi-column clustering restrictions are not merged
> correctly
> -------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18576
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18576
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
> Reporter: Piotr Kolaczkowski
> Assignee: Piotr Kolaczkowski
> Priority: Normal
>
> During working on CEP-29, I found that single-column and multi-column
> clustering restrictions are not merged correctly and cause query failures or
> incorrect results.
> The algorithm used in {{RestrictionSet.mergeRestrictions}} is incorrect, as
> its results depend on the (undefined) order of restrictions in a hashset.
> In more complex scenarios, when there are more restrictions to merge, the
> algorithm results can even differ between the test runs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
