[
https://issues.apache.org/jira/browse/CASSANDRA-15086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847125#comment-16847125
]
Cameron Zemek commented on CASSANDRA-15086:
-------------------------------------------
[~samt] appears I misread the patch on 15086. I thought I detected an overlap
of code change. My bad.
> Illegal column names make legacy sstables unreadable in 3.0/3.x
> ---------------------------------------------------------------
>
> Key: CASSANDRA-15086
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15086
> Project: Cassandra
> Issue Type: Bug
> Components: Local/SSTable
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 3.0.19, 3.11.5
>
>
> CASSANDRA-10608 adds extra validation when decoding a bytebuffer representing
> a legacy cellname. If the table is not COMPACT and the column name component
> of the cellname refers to a primary key column, an IllegalArgumentException
> is thrown. It looks like the original intent of 10608 was to prevent Thrift
> writes from inserting these invalid cells, but the same code path is
> exercised on the read path. The problem is that this kind of cells may exist
> in pre-3.0 sstables, either due to Thrift writes or through side loading of
> externally generated SSTables. Following an upgrade to 3.0, these partitions
> become unreadable, breaking both the read and compaction paths (and so also
> upgradesstables). Scrub in 2.1 does not help here as it blindly reproduces
> the invalid cells.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
