Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 14 Dec 2012 15:34:15 +0000 (UTC)
From: "T Jake Luciani (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12623777.1355416207913.7613.1355499255244@arcas>
In-Reply-To: <JIRA.12623777.1355416207913@arcas>
References: <JIRA.12623777.1355416207913@arcas>
Subject: [jira] [Commented] (CASSANDRA-5063) Aliasing Keyspaces
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

bq.  I'd rather support it more generally (for table and maybe columns (the latter being useful if you want short name on disk, but human readable aliases)) than just for keyspaces.

I'm fine with that
                
> 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