[jira] [Updated] (CASSANALYTICS-24) SSTable-version-based bridge determination

["Yifan Cai (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANALYTICS-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yifan Cai updated CASSANALYTICS-24:
-----------------------------------
    Summary: SSTable-version-based bridge determination  (was: Analytics should query a cluster for supported sstable versions and write in the highest known version to the cluster.)

> 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: 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org