cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10934) upgrade_test map_keys_indexing_test is failing
Date Wed, 20 Jan 2016 15:10:39 GMT


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|]

> upgrade_test map_keys_indexing_test is failing
> ----------------------------------------------
>                 Key: CASSANDRA-10934
>                 URL:
>             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,
> {{upgrade_tests.cql_tests.TestCQLNodes3RF3.map_keys_indexing_test}} and {{upgrade_tests.cql_tests.TestCQLNodes2RF1.map_keys_indexing_test}}
are both failing. See
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

View raw message