You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Kurt Greaves (JIRA)" <ji...@apache.org> on 2018/03/20 03:11:00 UTC
[jira] [Updated] (CASSANDRA-14104) Index target doesn't correctly
recognise non-UTF column names after COMPACT STORAGE drop
[ https://issues.apache.org/jira/browse/CASSANDRA-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Greaves updated CASSANDRA-14104:
-------------------------------------
Fix Version/s: 3.0.16
3.11.2
4.0
> Index target doesn't correctly recognise non-UTF column names after COMPACT STORAGE drop
> ----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-14104
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14104
> Project: Cassandra
> Issue Type: Bug
> Reporter: Alex Petrov
> Assignee: Alex Petrov
> Priority: Major
> Fix For: 3.0.16, 3.11.2, 4.0
>
> Attachments: ifesdjeen-14104-3.0-dtest.png, ifesdjeen-14104-3.0-testall.png, ifesdjeen-14104-3.11-dtest.png, ifesdjeen-14104-3.11-testall.png, ifesdjeen-14104-trunk-dtest.png, ifesdjeen-14104-trunk-testall.png
>
>
> Creating a compact storage table with dynamic composite type, then running {{ALTER TALBE ... DROP COMPACT STORAGE}} and then restarting the node will crash Cassandra node, since the Index Target is fetched using hashmap / strict equality. We need to fall back to linear search when index target can't be found (which should not be happening often).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org