You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/09/23 20:03:02 UTC

[jira] [Updated] (CASSANDRA-6060) Remove internal use of Strings for ks/cf names

     [ https://issues.apache.org/jira/browse/CASSANDRA-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-6060:
--------------------------------------

    Summary: Remove internal use of Strings for ks/cf names  (was: Remove internal use of Strings for ks/cf namaes)
    
> 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: Jason Brown
>              Labels: performance
>             Fix For: 2.1
>
>
> 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 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