[jira] [Updated] (CASSANALYTICS-25) Analytics reader should be able to query potential SSTable versions and fail fast on unsupported versions in the cluster
[ https://issues.apache.org/jira/browse/CASSANALYTICS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shailaja Koppu updated CASSANALYTICS-25: Change Category: Operability Complexity: Normal Component/s: Reader Status: Open (was: Triage Needed) > Analytics reader should be able to query potential SSTable versions and fail > fast on unsupported versions in the cluster > > > Key: CASSANALYTICS-25 > URL: https://issues.apache.org/jira/browse/CASSANALYTICS-25 > Project: Apache Cassandra Analytics > Issue Type: Task > Components: Reader >Reporter: Doug Rohrer >Assignee: Shailaja Koppu >Priority: Normal > > On the reader side, we should be able to query a C* cluster for what versions > of sstables it might have on disk and/or write. In other words, we need to > know the +range+ of sstable versions the reader might encounter during a run > so we can determine which bridge to use. If that range includes something we > don’t yet support, we should fail fast. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANALYTICS-25) Analytics reader should be able to query potential SSTable versions and fail fast on unsupported versions in the cluster
[ https://issues.apache.org/jira/browse/CASSANALYTICS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shailaja Koppu updated CASSANALYTICS-25: Source Control Link: https://github.com/apache/cassandra-analytics/pull/169 > Analytics reader should be able to query potential SSTable versions and fail > fast on unsupported versions in the cluster > > > Key: CASSANALYTICS-25 > URL: https://issues.apache.org/jira/browse/CASSANALYTICS-25 > Project: Apache Cassandra Analytics > Issue Type: Task >Reporter: Doug Rohrer >Assignee: Shailaja Koppu >Priority: Normal > Fix For: 1.0 > > > On the reader side, we should be able to query a C* cluster for what versions > of sstables it might have on disk and/or write. In other words, we need to > know the +range+ of sstable versions the reader might encounter during a run > so we can determine which bridge to use. If that range includes something we > don’t yet support, we should fail fast. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANALYTICS-25) Analytics reader should be able to query potential SSTable versions and fail fast on unsupported versions in the cluster
[ https://issues.apache.org/jira/browse/CASSANALYTICS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie updated CASSANALYTICS-25: --- Fix Version/s: 1.0 > Analytics reader should be able to query potential SSTable versions and fail > fast on unsupported versions in the cluster > > > Key: CASSANALYTICS-25 > URL: https://issues.apache.org/jira/browse/CASSANALYTICS-25 > Project: Apache Cassandra Analytics > Issue Type: Task >Reporter: Doug Rohrer >Priority: Normal > Fix For: 1.0 > > > On the reader side, we should be able to query a C* cluster for what versions > of sstables it might have on disk and/or write. In other words, we need to > know the +range+ of sstable versions the reader might encounter during a run > so we can determine which bridge to use. If that range includes something we > don’t yet support, we should fail fast. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
