[
https://issues.apache.org/jira/browse/CASSANDRA-18254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109766#comment-18109766
]
Lakshay Madan Gopal commented on CASSANDRA-18254:
-------------------------------------------------
I've opened a PR with the fix for the older branches:
[https://github.com/apache/cassandra/pull/5077]
It applies the raw-hex-bytes approach to PartitionerDefinedOrder.toJSONString
on cassandra-4.0, matching the reporter's reference patches (#2167/#2168) and
the CASSANDRA-17698 approach, plus a unit test and an integration test that
dumps a secondary-index sstable (both confirmed to fail without the fix).
Since 17698 already covers 5.0 and later, my understanding is this is needed
on 4.0 and 4.1. I've based it on 4.0 (which shares the ProtocolVersion
signature with 3.11). Happy to prepare the 4.1 change as well, or however
you'd prefer to handle the forward-merge. Please let me know.
> 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: Lakshay Madan Gopal
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 6.0.x, 7.x
>
> Time Spent: 1h 10m
> 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]
