You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2012/12/13 18:26:13 UTC

[jira] [Commented] (CASSANDRA-5063) Aliasing Keyspaces

    [ https://issues.apache.org/jira/browse/CASSANDRA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531215#comment-13531215 ] 

Sylvain Lebresne commented on CASSANDRA-5063:
---------------------------------------------

That honestly sound like something you can do as easily client side than we can do in Cassandra, and with actually greater flexibility client side if you want to only redirect some of your clients on the keyspace and not other.
                
> Aliasing Keyspaces
> ------------------
>
>                 Key: CASSANDRA-5063
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5063
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Carl Yeksigian
>
> The way we are working with our cassandra is that we have multiple keyspaces, each of them representing the same data in different forms. We would like to have a single name representing the current production keyspace, while we are working on backloading our development keyspaces.
> The proposed work flow would be:
> - create keyspace prod1
> - alias keyspace prod to prod1
> - create keyspace prod2
> - backload prod2
> - alias keyspace prod to prod2
> - drop keyspace prod1
> It would be really nice if we weren't referring to "prod1" and "prod2", rather always referencing "prod", and the aliasing would happen in Cassandra.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira