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

Andrés Beck-Ruiz updated CASSSIDECAR-373:
-----------------------------------------
    Description: 
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.

  was:
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.


> 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
>            Priority: Major
>              Labels: CEP-53
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to