[
https://issues.apache.org/jira/browse/CASSANDRA-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296582#comment-16296582
]
Alex Petrov commented on CASSANDRA-14104:
-----------------------------------------
Committed to 3.0 as
[0521f8dc5d5e05c0530726e9549fa2481726a818|https://github.com/apache/cassandra/commit/0521f8dc5d5e05c0530726e9549fa2481726a818]
and merged up to
[3.11|https://github.com/apache/cassandra/commit/adc32ac836e90b8c4503030feb76ce031998ad80]
and
[trunk|https://github.com/apache/cassandra/commit/8764ef2da367fac64adad0821a34e6fa15da13c6].
> 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
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
