[
https://issues.apache.org/jira/browse/CASSANDRA-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345250#comment-14345250
]
Brian Hess commented on CASSANDRA-6060:
----------------------------------------
I know this ticket is closed, but there is another use case that might make
this more useful. Namely, with the advent of CTAS (CASSANDRA-8234), you could
want to change the primary key of a table. To do that, you could create a new
table with the new primary key and select the old data into it. The last step,
for cleanliness, might be to drop the original table alter the name of the new
table to the original table name - thereby completing the change of the primary
key.
> Remove internal use of Strings for ks/cf names
> ----------------------------------------------
>
> Key: CASSANDRA-6060
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6060
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Ariel Weisberg
> Labels: performance
>
> We toss a lot of Strings around internally, including across the network.
> Once a request has been Prepared, we ought to be able to encode these as int
> ids.
> Unfortuntely, we moved from int to uuid in CASSANDRA-3794, which was a
> reasonable move at the time, but a uuid is a lot bigger than an int. Now
> that we have CAS we can allow concurrent schema updates while still using
> sequential int IDs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
