[
https://issues.apache.org/jira/browse/CASSANALYTICS-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANALYTICS-24:
-----------------------------------
Fix Version/s: 0.5
Source Control Link:
https://github.com/apache/cassandra-analytics/commit/30e69988976526fe208aefab7f8204897e647470
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> SSTable-version-based bridge determination
> ------------------------------------------
>
> Key: CASSANALYTICS-24
> URL: https://issues.apache.org/jira/browse/CASSANALYTICS-24
> Project: Apache Cassandra Analytics
> Issue Type: Task
> Components: Writer
> Reporter: Doug Rohrer
> Assignee: Shailaja Koppu
> Priority: Normal
> Fix For: 0.5, 1.0
>
> Time Spent: 13h
> Remaining Estimate: 0h
>
> Post TCM {{storage_compatibility_mode}} decides what formats we write various
> things in. The analytics library should take the versions a cluster knows how
> to read into account when interacting with and authoring files on a node.
> Ideally we’d be able to query from the cluster what SSTable versions the
> cluster can read, what version it may _prefer_ (storage compatibility mode is
> a good example of prefer vs. support), and analytics can make a choice as to
> what version of SSTable to write to the cluster given which sstable versions
> it supports.
> Today the write format appears to be determined, essentially, by the
> MessagingService version. We should leverage that through the sidecar → C*
> node pathway so we know what version to write with the SBW.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
