[jira] [Resolved] (CASSANDRA-4968) CQL3 Descrepancies

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-4968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-4968.
---------------------------------------

    Resolution: Fixed
    
> CQL3 Descrepancies
> ------------------
>
>                 Key: CASSANDRA-4968
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4968
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.0 beta 2
>            Reporter: T Jake Luciani
>            Priority: Minor
>             Fix For: 1.2.0 rc1
>
>
> I upgraded an environment from 1.1.6 to 1.2 beta
> We found the following differences between cql3 versions:
> The CLUSTERING ORDER BY requires all columns be specified in 1.2 whereas 1.1 defaulted to ASC
> {code}
> CREATE TABLE table1(
>    col1 text,
>    classtype ascii,
>    kt bigint,
>    id uuid,
>    PRIMARY KEY (col1,classtype,kt)
> ) WITH COMPACT STORAGE
> AND CLUSTERING ORDER BY(classtype ASC, kt DESC)
> {code}
> 1.1 didn't require classtype in the ORDER BY, 1.2 does.
> ----------
> In docs/cql3.textile there is mention of 'compaction_strategy' CREATE option but the actual option is 'compaction'
> ----------
> cqlsh for some reason renders all bytes fields as strings in 1.2 whereas in 1.1 they were hex.

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