[
https://issues.apache.org/jira/browse/CASSANDRA-12997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15804664#comment-15804664
]
Aleksey Yeschenko commented on CASSANDRA-12997:
-----------------------------------------------
Sorry. Heavy-handed was an unnecessary exaggeration.
But this way in a multiple-node cluster the outcome would still depend on which
node gets the schema statement, and that node's {{lastTimestampMicros}} value,
making it generally non-deterministic. So this change doesn't fundamentally fix
the problem, just feels a bit more right.
That said, who really cares? Go ahead with either option. +1 to the original
patch.
> dtest failure in
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName
> -------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-12997
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12997
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sean McCarthy
> Assignee: Sylvain Lebresne
> Labels: test-failure, testall
>
> example failure:
> http://cassci.datastax.com/job/trunk_testall/1298/testReport/org.apache.cassandra.cql3.validation.operations/AlterTest/testDropListAndAddListWithSameName
> {code}
> Error Message
> Invalid value for row 0 column 2 (mycollection of type list<text>), expected
> <null> but got <[first element]>
> {code}{code}Stacktrace
> junit.framework.AssertionFailedError: Invalid value for row 0 column 2
> (mycollection of type list<text>), expected <null> but got <[first element]>
> at org.apache.cassandra.cql3.CQLTester.assertRows(CQLTester.java:908)
> at
> org.apache.cassandra.cql3.validation.operations.AlterTest.testDropListAndAddListWithSameName(AlterTest.java:87)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
