Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 23 Nov 2015 21:31:11 +0000 (UTC)
From: "Ariel Weisberg (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12669477.1379605339000.166100.1448314271186@Atlassian.JIRA>
In-Reply-To: <JIRA.12669477.1379605339000@Atlassian.JIRA>
References: <JIRA.12669477.1379605339000@Atlassian.JIRA>
 <JIRA.12669477.1379605339050@arcas>
Subject: [jira] [Updated] (CASSANDRA-6060) Remove internal use of Strings
 for ks/cf names
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ariel Weisberg updated CASSANDRA-6060:
--------------------------------------
    Component/s: Streaming and Messaging

> 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: Streaming and Messaging
>            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)