[
https://issues.apache.org/jira/browse/CASSSIDECAR-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrés Beck-Ruiz updated CASSSIDECAR-473:
-----------------------------------------
Description:
The initial implementation of the {{CassandraStorageProvider}} uses the managed
Cassandra cluster for durable storage of operational job state. CEP-53 should
also support a single Cassandra cluster maintaining operational data for
multiple clusters. This also allows a separate Cassandra cluster from the one
being managed by the Sidedcar fleet to be used for state storage.
To accomplish this, we need to add logic for updating the schema to optionally
skip create statements if the operational job tables already exist in the
remote Cassandra cluster. We also need to update
{{OperationalJobConfiguration}} and add logic for creating a session to connect
to a remote cluster.
was:
The initial implementation of the {{CassandraStorageProvider}} uses the managed
Cassandra cluster for durable storage of operational job state. CEP-53
describes the option to also support a single Cassandra cluster maintaining
operational data for multiple clusters, which also allows a separate Cassandra
cluster from the one being managed by the Sidedcar fleet to be used for state
storage.
To accomplish this, we need to add logic for updating the schema to optionally
skip create statements if the operational job tables already exist in the
remote Cassandra cluster. We also need to update
{{OperationalJobConfiguration}} and add logic for creating a session to connect
to a remote cluster.
> Add support to CassandraStorageProvider for connecting to remote Cassandra
> cluster
> ----------------------------------------------------------------------------------
>
> Key: CASSSIDECAR-473
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-473
> Project: Sidecar for Apache Cassandra
> Issue Type: Sub-task
> Reporter: Andrés Beck-Ruiz
> Priority: Major
>
> The initial implementation of the {{CassandraStorageProvider}} uses the
> managed Cassandra cluster for durable storage of operational job state.
> CEP-53 should also support a single Cassandra cluster maintaining operational
> data for multiple clusters. This also allows a separate Cassandra cluster
> from the one being managed by the Sidedcar fleet to be used for state storage.
> To accomplish this, we need to add logic for updating the schema to
> optionally skip create statements if the operational job tables already exist
> in the remote Cassandra cluster. We also need to update
> {{OperationalJobConfiguration}} and add logic for creating a session to
> connect to a remote cluster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]