From user-return-37407-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Tue Nov 5 06:44:51 2013 Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A8416100DE for ; Tue, 5 Nov 2013 06:44:51 +0000 (UTC) Received: (qmail 80073 invoked by uid 500); 5 Nov 2013 06:44:48 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 80037 invoked by uid 500); 5 Nov 2013 06:44:42 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 80027 invoked by uid 99); 5 Nov 2013 06:44:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Nov 2013 06:44:41 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.220.54] (HELO mail-pa0-f54.google.com) (209.85.220.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Nov 2013 06:44:37 +0000 Received: by mail-pa0-f54.google.com with SMTP id fa1so8196307pad.27 for ; Mon, 04 Nov 2013 22:44:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:message-id:mime-version :subject:date:references:to:in-reply-to; bh=XVJ7pV4VGhnVJTV5xcAnv///D7vbKjruNZcpZzNj1dE=; b=InUo1xTKzXtxy0gIi8JBG4fLhRznV4/EhwF2vFVI13zv+V9YPc3nJ3CBUlFB0XShYr +BP70c/DbhSZXbf/36IA9oT7BZOxiir2kJ5dk367zNJaX/uLId/uScUKqUkSGJ9Wa9Jy MOLlv1eusqIeWovH2qEx1HxkVXnBi7TuRCAW1AQLYa2GXbH1AYMQKxEOg6lYzDgphZfT 7tMDOdOrDJs3zbQ99xN0830E+TfE6MPxKtmxpU3ULxY1JwKKe7Ciqpqe2WJKUWB47pak Cr2I5OSD5ZwPKaT17JRg7kycPZY5UzruJY/TQXrPOVzbLcKpPtbdHad8aXo7mWPQGnXk NiXg== X-Gm-Message-State: ALoCoQnyaIIhuotjoq/0CzAgxFZx5xJp1ZqZo9Nm3qSyhUloV9TOwovwMcOFucRCqcJRXtc7jge+ X-Received: by 10.68.225.9 with SMTP id rg9mr21601690pbc.122.1383633856510; Mon, 04 Nov 2013 22:44:16 -0800 (PST) Received: from [172.16.1.20] ([203.86.207.101]) by mx.google.com with ESMTPSA id j9sm38021082paj.18.2013.11.04.22.44.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Nov 2013 22:44:15 -0800 (PST) From: Aaron Morton Content-Type: multipart/alternative; boundary="Apple-Mail=_48347E8A-9BC7-470C-BA19-E024BE00AFEE" Message-Id: <96AA2923-C113-4F79-8B91-C69760A5868F@thelastpickle.com> Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) Subject: Re: CF name length restrictions (CASSANDRA-4157 and CASSANDRA-4110) Date: Tue, 5 Nov 2013 19:44:12 +1300 References: To: Cassandra User In-Reply-To: X-Mailer: Apple Mail (2.1816) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_48347E8A-9BC7-470C-BA19-E024BE00AFEE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii My understanding of CASSANDRA-4110 is that the file name (not the total = path length) has to be <=3D 255 chars long.=20 On not windows platforms in 1.1.0+ you should be ok with KS + CF names = that combined go up to about 230 chars. Leaving room for the extra few = things Cassandra dds to the SStable file names.=20 Cheers ----------------- Aaron Morton New Zealand @aaronmorton Co-Founder & Principal Consultant Apache Cassandra Consulting http://www.thelastpickle.com On 1/11/2013, at 5:54 am, Peter Sanford = wrote: > We're working on upgrading from 1.0.12 to 1.1.12. After upgrading a = test node I ran into CASSANDRA-4157 which restricts the max length of CF = names to <=3D 48 characters. It looks like CASSANDRA-4110 will allow us = to upgrade and keep our existing long CF names, but we won't be able to = create new CFs with names longer than 48 chars.=20 >=20 > Is there any reason that the logic from 4110 wasn't also applied to = the 4157 code path?=20 >=20 > (Our naming convention results in a lot of materialized view CFs that = have names > 48 characters.) >=20 > -psanford --Apple-Mail=_48347E8A-9BC7-470C-BA19-E024BE00AFEE Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii My understanding of  CASSANDRA-4110 is that the file name (not the total path length) has to be <= 255 chars long. 

On not windows platforms in 1.1.0+ you should be ok with KS + CF names that combined go up to about 230 chars. Leaving room for the extra few things Cassandra dds to the SStable file names. 

Cheers

-----------------
Aaron Morton
New Zealand
@aaronmorton

Co-Founder & Principal Consultant
Apache Cassandra Consulting

On 1/11/2013, at 5:54 am, Peter Sanford <psanford@nearbuysystems.com> wrote:

We're working on upgrading from 1.0.12 to 1.1.12. After upgrading a test node I ran into CASSANDRA-4157 which restricts the max length of CF names to <= 48 characters. It looks like CASSANDRA-4110 will allow us to upgrade and keep our existing long CF names, but we won't be able to create new CFs with names longer than 48 chars. 

Is there any reason that the logic from 4110 wasn't also applied to the 4157 code path? 

(Our naming convention results in a lot of materialized view CFs that have names > 48 characters.)

-psanford

--Apple-Mail=_48347E8A-9BC7-470C-BA19-E024BE00AFEE--