Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A8CC917B97 for ; Tue, 3 Mar 2015 16:04:08 +0000 (UTC) Received: (qmail 93308 invoked by uid 500); 3 Mar 2015 16:04:05 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 93270 invoked by uid 500); 3 Mar 2015 16:04:05 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 93247 invoked by uid 99); 3 Mar 2015 16:04:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2015 16:04:05 +0000 Date: Tue, 3 Mar 2015 16:04:05 +0000 (UTC) From: " Brian Hess (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)