You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alex Petrov (JIRA)" <ji...@apache.org> on 2017/12/11 18:30:05 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16286383#comment-16286383 ]
Alex Petrov commented on CASSANDRA-14104:
-----------------------------------------
Patch:
|[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...ifesdjeen:14104-3.0]|[3.0|https://github.com/apache/cassandra/compare/cassandra-3.11...ifesdjeen:14104-3.11]|[3.0|https://github.com/apache/cassandra/compare/trunk...ifesdjeen:14104-trunk]|
> 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
>
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org