[
https://issues.apache.org/jira/browse/CASSANDRA-10267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14875725#comment-14875725
]
Sylvain Lebresne commented on CASSANDRA-10267:
----------------------------------------------
bq. This commit fixes {{TestCQL.static_columns_cas_test}}, but I have a
feeling that it may have some unintended consequences
Yes, I'm pretty sure this breaks deletion of static collection columns. The
handling of static in slice query command is indeed not fully correct, but I
don't think we can't fix it in {{LegacyLayout.decodeBound()}}. I've pushed a
commit [here|https://github.com/pcmanus/cassandra/commits/10267] that I think
provide a more correct fix (the commit message attempts to explain a bit more
precisely what's going on). As far as I can tell, this fixes
{{TestCQL.static_columns_cas_test}} (and I say "as far as I can tell" because
the test is flaky is the first place, so it's possible I've just be really
lucky in the 5 run or so that I tried so far).
> Failing tests in upgrade_trests.paging_test
> -------------------------------------------
>
> Key: CASSANDRA-10267
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10267
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Sylvain Lebresne
> Assignee: Blake Eggleston
> Fix For: 3.0.0 rc1
>
>
> This is a continuation of CASSANDRA-9893 to deal with the failure of the
> {{upgrade_trests.paging_test}} tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
