cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail
Date Tue, 10 May 2011 12:48:47 GMT

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

Jonathan Ellis edited comment on CASSANDRA-2497 at 5/10/11 12:48 PM:
---------------------------------------------------------------------

That is working as designed, if you don't want to use assume you need to add a key_validation_class.

      was (Author: jbellis):
    That is working as designed, if you don't want to use assume you need to add a column_definition.
  
> CLI: issue with keys being interpreted as hex and causing SET statement to fail
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2497
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2497
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>         Environment: * Single Node instance on MacOSX
> * Nightly Compiled Build from 4/18/2011
> * Installed from: https://builds.apache.org/hudson/job/Cassandra/lastSuccessfulBuild/artifact/cassandra/build/apache-cassandra-2011-04-18_11-02-29-bin.tar.gz
>            Reporter: Cathy Daw
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 0.8.0 beta 2
>
>         Attachments: CASSANDRA-2497.patch
>
>
> *Original Summary*: Issues with Update Column Family and adding a key_validation_class
> _Changed summary because the issue repros on drop/create.  see comment._
> *Reproduction Steps*
> {code}
> create column family users with comparator = UTF8Type 
> and column_metadata = [{column_name: password, validation_class: UTF8Type}];
> update column family users with key_validation_class=UTF8Type;
> set users['jsmith']['password']='ch@ngem3';          
> {code}
> *EXPECTED RESULT:* After the UPDATE statement, the SET statement should go through successfully.
> *ACTUAL RESULT:*  The SET statement gives the same error message, regardless of the UPDATE
statement: 
> {code}
> org.apache.cassandra.db.marshal.MarshalException: cannot parse 'jsmith' as hex bytes
> {code}
> *Output from describe keyspace*
> {code}
>     ColumnFamily: users
>       Key Validation Class: org.apache.cassandra.db.marshal.UTF8Type
>       Default column value validator: org.apache.cassandra.db.marshal.BytesType
>       Columns sorted by: org.apache.cassandra.db.marshal.UTF8Type
>       Row cache size / save period in seconds: 0.0/0
>       Key cache size / save period in seconds: 200000.0/14400
>       Memtable thresholds: 0.29062499999999997/62/1440 (millions of ops/MB/minutes)
>       GC grace seconds: 864000
>       Compaction min/max thresholds: 4/32
>       Read repair chance: 1.0
>       Replicate on write: false
>       Built indexes: []
>       Column Metadata:
>         Column Name: password
>           Validation Class: org.apache.cassandra.db.marshal.UTF8Type
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message