[jira] [Updated] (CASSSIDECAR-373) Define storage provider interface and Cassandra implementation to support durable job tracking

["Andrés Beck-Ruiz (Jira)" <ji...@apache.org>]

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

Andrés Beck-Ruiz updated CASSSIDECAR-373:
-----------------------------------------
    Priority: Normal  (was: Major)

> Define storage provider interface and Cassandra implementation to support durable job tracking
> ----------------------------------------------------------------------------------------------
>
>                 Key: CASSSIDECAR-373
>                 URL: https://issues.apache.org/jira/browse/CASSSIDECAR-373
>             Project: Sidecar for Apache Cassandra
>          Issue Type: Sub-task
>            Reporter: Andrés Beck-Ruiz
>            Assignee: Andrés Beck-Ruiz
>            Priority: Normal
>              Labels: CEP-53
>          Time Spent: 6h 40m
>  Remaining Estimate: 0h
>
> In order to create a durable operational job tracker, we should implement a provider-agnostic interface, {{{}StorageProvider{}}}. We should also add a {{CassandraStorageProvider}} implementation, which will be the default storage provider class that comes out of the box.
> This class will contain logic for creating and using system tables to store and manage operational jobs, described [here in CEP-53|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-53%3A+Cassandra+Rolling+Restarts+via+Sidecar#CEP53:CassandraRollingRestartsviaSidecar-CassandraSidecarSystemTables]. This provider should also allow clients to either connect to the same cluster that Sidecar is managing or a separate Cassandra cluster for storage.



--
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