[
https://issues.apache.org/jira/browse/CASSANDRA-12123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357760#comment-15357760
]
Tyler Hobbs commented on CASSANDRA-12123:
-----------------------------------------
Actually, it's not a recent regression. I wrote this test for CASSANDRA-11930
to reproduce a range tombstone problem. However, I was testing that with the
two-node RF=1 upgrade scenario. This is failing with the three-node RF=3
scenario, and like I mentioned, it's a problem with the sanity query, not
tombstones. So, it seems that in mixed version clusters, the different
ordering for static columns is causing the coordinator to duplicate them in the
final results.
> dtest failure in
> upgrade_tests.cql_tests.TestCQLNodes3RF3_Upgrade_next_2_1_x_To_current_3_x.cql3_non_compound_range_tombstones_test
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-12123
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12123
> Project: Cassandra
> Issue Type: Test
> Reporter: Philip Thompson
> Assignee: Tyler Hobbs
> Labels: dtest
> Fix For: 3.x
>
>
> example failure:
> http://cassci.datastax.com/job/upgrade_tests-all-custom_branch_runs/37/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3_Upgrade_next_2_1_x_To_current_3_x/cql3_non_compound_range_tombstones_test
> Failed on CassCI build upgrade_tests-all-custom_branch_runs #37
> Failing here:
> {code}
> File "/home/automaton/cassandra-dtest/upgrade_tests/cql_tests.py", line
> 1667, in cql3_non_compound_range_tombstones_test
> self.assertEqual(6, len(row), row)
> {code}
> As we see, the row has more data returned. This implies that data isn't
> properly being shadowed by the tombstone. As such, I'm filing this directly
> as a bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
