[
https://issues.apache.org/jira/browse/CASSANDRA-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335953#comment-15335953
]
Alex Petrov edited comment on CASSANDRA-10857 at 6/17/16 2:14 PM:
------------------------------------------------------------------
bq. {{ALTER TABLE foo DROP COMPACT STORAGE}} or something along that line,
rather than "random" table property. It's of course mainly a minor syntactic
detail.
I'll add the {{DROP COMPACT STORAGE}} instead of the flag (it was the quickest
way plus the initial patch as actually worked through
And will add the expanded comments to the {{NEWS.txt}} section. We can also add
a special document as SASI does, where we explain thrift updates.
As regards (2), (3), (4) - I mostly wanted to pinpoint it. We may briefly
mention it in case someone wonders what happens in this case when migrating
from thrift or even just dropping {{COMPACT STORAGE}}.
I agree that the default {{BytesType}} is not problem. Might be worth
mentioning it in docs and maybe add some notes about types.
bq. "" (though it's worth checking that such name is actually allowed in
queries).
-Unfortunately, we are not allowing selecting such name at the moment. When try
try type cast, the empty string literal will appear in result instead of the
actual column. We can add '' as a selector.-
The grammar is updated to support empty strings for identifiers, too.
was (Author: ifesdjeen):
bq. {{ALTER TABLE foo DROP COMPACT STORAGE}} or something along that line,
rather than "random" table property. It's of course mainly a minor syntactic
detail.
I'll add the {{DROP COMPACT STORAGE}} instead of the flag (it was the quickest
way plus the initial patch as actually worked through
And will add the expanded comments to the {{NEWS.txt}} section. We can also add
a special document as SASI does, where we explain thrift updates.
As regards (2), (3), (4) - I mostly wanted to pinpoint it. We may briefly
mention it in case someone wonders what happens in this case when migrating
from thrift or even just dropping {{COMPACT STORAGE}}.
I agree that the default {{BytesType}} is not problem. Might be worth
mentioning it in docs and maybe add some notes about types.
bq. "" (though it's worth checking that such name is actually allowed in
queries).
Unfortunately, we are not allowing selecting such name at the moment. When try
try type cast, the empty string literal will appear in result instead of the
actual column. We can add '' as a selector.
> 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)
