Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 5 Oct 2012 21:00:03 +0000 (UTC)
From: "Chris Chiappone (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1711497047.2827.1349470803731.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1672513207.30350.1334610257888.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-4157) Allow KS + CF names up to 48
 characters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470654#comment-13470654 ] 

Chris Chiappone commented on CASSANDRA-4157:
--------------------------------------------

This actually causes a bunch of problems for customers that have used longer the 48 character keyspace and cf names.  How will this affect the upgrade path for those customers?
                
> Allow KS + CF names up to 48 characters
> ---------------------------------------
>
>                 Key: CASSANDRA-4157
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4157
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.1.0
>
>         Attachments: 4157.txt
>
>
> CASSANDRA-2749 imposed a 32-character limit on KS and CF names.  We can be a little more lenient than that and still be safe for path names (see CASSANDRA-4110).

--
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