Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 17 Jun 2016 14:46:05 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12921716.1450113202000.22144.1466174765625@Atlassian.JIRA>
In-Reply-To: <JIRA.12921716.1450113202000@Atlassian.JIRA>
References: <JIRA.12921716.1450113202000@Atlassian.JIRA> <JIRA.12921716.1450113202219@arcas>
Subject: [jira] [Commented] (CASSANDRA-10857) Allow dropping COMPACT STORAGE
 flag from tables in 3.X
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 17 Jun 2016 14:46:08 -0000


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

Sylvain Lebresne commented on CASSANDRA-10857:
----------------------------------------------

bq. The grammar is updated to support empty strings for identifiers, too.

Note that if we do that (and I certainly wouldn't mind a better solution cause that's still ugly at the end of the day), I suggest still rejecting it when declaring columns/field (for table, MVs, UDT, function parameters, ...). We only want to solve our problem of selecting/inserting into that server-side defined column, but I doubt allowing user to create column with empty names is a good idea.

> Allow dropping COMPACT STORAGE flag from tables in 3.X
> ------------------------------------------------------
>
>                 Key: CASSANDRA-10857
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10857
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL, Distributed Metadata
>            Reporter: Aleksey Yeschenko
>            Assignee: Alex Petrov
>             Fix For: 3.x
>
>
> Thrift allows users to define flexible mixed column families - where certain columns would have explicitly pre-defined names, potentially non-default validation types, and be indexed.
> Example:
> {code}
> create column family foo
>     and default_validation_class = UTF8Type
>     and column_metadata = [
>         {column_name: bar, validation_class: Int32Type, index_type: KEYS},
>         {column_name: baz, validation_class: UUIDType, index_type: KEYS}
>     ];
> {code}
> Columns named {{bar}} and {{baz}} will be validated as {{Int32Type}} and {{UUIDType}}, respectively, and be indexed. Columns with any other name will be validated by {{UTF8Type}} and will not be indexed.
> With CASSANDRA-8099, {{bar}} and {{baz}} would be mapped to static columns internally. However, being {{WITH COMPACT STORAGE}}, the table will only expose {{bar}} and {{baz}} columns. Accessing any dynamic columns (any column not named {{bar}} and {{baz}}) right now requires going through Thrift.
> This is blocking Thrift -> CQL migration for users who have mixed dynamic/static column families. That said, it *shouldn't* be hard to allow users to drop the {{compact}} flag to expose the table as it is internally now, and be able to access all columns.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)