[ https://issues.apache.org/jira/browse/CASSANDRA-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108678#comment-15108678 ]
Sam Tunnicliffe commented on CASSANDRA-10934: --------------------------------------------- The failing dtest is incorrect, creating a values index on a map column which already has a keys index is permitted since 3.0. dtest PR [here|https://github.com/riptano/cassandra-dtest/pull/754] > upgrade_test map_keys_indexing_test is failing > ---------------------------------------------- > > Key: CASSANDRA-10934 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10934 > Project: Cassandra > Issue Type: Sub-task > Reporter: Philip Thompson > Assignee: Sam Tunnicliffe > Fix For: 3.0.x, 3.x > > Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log, > node3.log, node3_debug.log > > > {{upgrade_tests.cql_tests.TestCQLNodes3RF3.map_keys_indexing_test}} and > {{upgrade_tests.cql_tests.TestCQLNodes2RF1.map_keys_indexing_test}} are both > failing. See > http://cassci.datastax.com/job/cassandra-3.0_dtest/456/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3/map_keys_indexing_test/ > for an example. > The tests create a secondary index on the keys of a map, then perform an > upgrade, then attempt to create secondary index on the values of that map. > This is expected to fail, as both indices cannot exist at the same time. If > the index creation happens before the upgrade, it does fail. After the > upgrade, however, it works. When I check the cluster schema metadata with the > python driver, I can only see one index after creating the second, rather > than both. > Node logs are attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)