[
https://issues.apache.org/jira/browse/CASSANDRA-21722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18120667#comment-18120667
]
Arvind Kandpal commented on CASSANDRA-21722:
--------------------------------------------
I checked this on trunk and cep-45-mutation-tracking.
The issue is present on cep-45-mutation-tracking. In BigFormat.java, the
version comment says mutation tracking metadata was added in "pb", but the code
checks version.compareTo("ob") >= 0.
On trunk, this code does not exist yet, since mutation tracking has not been
merged there.
> Fix incorrect SSTable version threshold for Mutation Tracking metadata
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-21722
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21722
> Project: Apache Cassandra
> Issue Type: Task
> Reporter: Saranya Krishnakumar
> Priority: Normal
>
> BigFormat.BigVersion sets hasMutationTrackingMetadata =
> version.compareTo("ob") >= 0, but mutation tracking metadata was introduced
> in the pb SSTable version, imports of versions before such as pa is causing
> StatsMetadata deserialization to expect and read fields that were never
> written for that version. The fix changes the threshold to compareTo("pb") >=
> 0, matching the version that introduced mutation tracking metadata.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
