You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "paul cannon (JIRA)" <ji...@apache.org> on 2012/07/10 00:49:34 UTC

[jira] [Updated] (CASSANDRA-4385) bug when trying to describe a cf in a pre cql3 case sensitive keyspace

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

paul cannon updated CASSANDRA-4385:
-----------------------------------

    Attachment: 0001-cqlsh-Fix-error-reporting-for-unknown-CFs.patch

Attached patch fixes error reporting when a columnfamily is not found.

Also available in my github, in the 4385 branch; current version tagged pending/4385.

https://github.com/thepaul/cassandra/tree/pending/4385
                
> bug when trying to describe a cf in a pre cql3 case sensitive keyspace
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-4385
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4385
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Drivers
>    Affects Versions: 1.1.0
>         Environment: Linux, Hotspot JDK6, Cassandra 1.1.0 from tarball unmodified, stock config.
>            Reporter: Al Tobey
>            Assignee: paul cannon
>            Priority: Minor
>              Labels: cqlsh
>             Fix For: 1.1.3
>
>         Attachments: 0001-cqlsh-Fix-error-reporting-for-unknown-CFs.patch
>
>
> I can't describe column families in my schema defined via cassandra-cli. Update also seems to fail for the same CF's.
> CREATE KEYSPACE Hastur
>   with placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy'
>   and strategy_options = {replication_factor:2};
> CREATE COLUMN FAMILY LookupByKey
>   with compaction_strategy = 'LeveledCompactionStrategy'
>   and compression_options = null;
> Then later, https://gist.github.com/3006886

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira