You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremy Hanna (Jira)" <ji...@apache.org> on 2019/09/03 19:16:00 UTC
[jira] [Commented] (CASSANDRA-13479) Create schema file for
keyspace as a part of snapshot
[ https://issues.apache.org/jira/browse/CASSANDRA-13479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921673#comment-16921673 ]
Jeremy Hanna commented on CASSANDRA-13479:
------------------------------------------
While potentially useful, for the common case wouldn't you want potentially different options in the new cluster like keyspace name or replication options?
> Create schema file for keyspace as a part of snapshot
> -----------------------------------------------------
>
> Key: CASSANDRA-13479
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13479
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Distributed Metadata
> Reporter: Varun Gupta
> Priority: Low
> Fix For: 3.0.x
>
>
> As of now, snapshot process create schema.cql file per column family. Restoring to new cluster is not feasible if keyspace schema is not present. So similar to schema.cql file created for each column family, a different schema.cql file should be created for keyspace too.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org