[
https://issues.apache.org/jira/browse/CASSANDRA-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968216#comment-13968216
]
Benedict commented on CASSANDRA-6060:
-------------------------------------
Bumping to 3.0, as this won't make it into 2.1 now
> 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: Vijay
> Labels: performance
> Fix For: 3.0
>
>
> 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.2#6252)
