[
https://issues.apache.org/jira/browse/CASSANDRA-18254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109662#comment-18109662
]
Brandon Williams commented on CASSANDRA-18254:
----------------------------------------------
Hi [~lakshaym7], I've updated the fix versions to what is current, though
without digging in I'm not sure anything need to be done here for 5.0 and
later, but I'm sure you'll find out.
bq. My plan is to update the JSON serialization path so that when sstabledump
hits the PartitionerDefinedOrder clustering key from a secondary index sstable,
it prints the raw bytes instead of throwing UnsupportedOperationException,
following the approach outlined here.
That sounds good to me.
> sstabledump for secondary index sstable error
> ---------------------------------------------
>
> Key: CASSANDRA-18254
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18254
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Feature/2i Index, Local/SSTable, Tool/sstable
> Reporter: guo Maxwell
> Assignee: guo Maxwell
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 6.0.x, 7.x
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> As [CASSANDRA-17698|https://issues.apache.org/jira/browse/CASSANDRA-17698]
> described , for older branches we open a new ticket and fixed just
> JSON-printing the failing clustering key as raw bytes.
> for Cassandra version that can change the sstable version (may be 5.0) , the
> patch for CASSANDRA-17698 will be applied.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
