[
https://issues.apache.org/jira/browse/CASSANDRA-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-11927:
----------------------------------------
Status: Open (was: Patch Available)
bq. applying a mutation to an unknown table/CF should cause the write request
to fail
I'm not convinced about this tbh.
First, I disagree that it is a bug, I would argue rather that the behaviour is
fully intended. As such, changing it would be invalid in 2.2/3.0/3.9 and
debatable even for trunk given that nobody actually reported it as a problem.
Second, the way this is implemented here means that any updates obtained from
the iterator *before* a missing cf is encountered, *would* be applied but the
RTE would *still* be thrown which is pretty confusing.
So given that the actual cause of the test failure has been addressed by
CASSANDRA-12083, I suggest we close this.
> dtest failure in replication_test.ReplicationTest.simple_test
> -------------------------------------------------------------
>
> Key: CASSANDRA-11927
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11927
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sean McCarthy
> Assignee: Paulo Motta
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log,
> node3.log, node3_debug.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_novnode_dtest/387/testReport/replication_test/ReplicationTest/simple_test
> Failed on CassCI build trunk_novnode_dtest #387
> Logs are attached.
> Unexpected error in question:
> {code}
> ERROR [SharedPool-Worker-1] 2016-05-30 16:00:17,211 Keyspace.java:504 -
> Attempting to mutate non-existant table 99f5be60-267f-11e6-ad5f-f13d771494ea
> (test.test)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
