[
https://issues.apache.org/jira/browse/CASSANDRA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532366#comment-13532366
]
Sylvain Lebresne commented on CASSANDRA-5063:
---------------------------------------------
That would have to be part of the schema, not a new system table, because this
would have to be replicated everywhere with the schema.
This is definitively doable, but still not sure this isn't a bit feature creep.
But in fact, if we consider that aliases are desirable, 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.
> 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
