cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5063) Aliasing Keyspaces
Date Fri, 14 Dec 2012 15:30:13 GMT

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

T Jake Luciani commented on CASSANDRA-5063:
-------------------------------------------

http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_7001.htm
                
> 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

Mime
View raw message