[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-07-05 Thread Igor Yagolnitser (JIRA) 

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

Igor Yagolnitser commented on CASSANDRA-2497:
-

apache-cassandra-0.8.1

set Users['user1']['fname']='fname1';
rg.apache.cassandra.db.marshal.MarshalException: cannot parse 'fname' as hex 
bytes

assume Users keys as ascii;

no effect, set still gives the same error.

 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: 20.0/14400
   Memtable thresholds: 0.290624997/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

[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-07-05 Thread Pavel Yaskevich (JIRA) 

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

Pavel Yaskevich commented on CASSANDRA-2497:


As you can see from your example this is not a problem with key but rather with 
column name. So use `assume cf comparator as type;` or re-create your CF 
with a valid comparator.

 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: 20.0/14400
   Memtable thresholds: 0.290624997/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

[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-06-16 Thread donghwan Ahn (JIRA) 

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

donghwan Ahn commented on CASSANDRA-2497:
-

if when you 'create column family User'
you need all class type definition.

create column family Users with comparator=UTF8Type and 
default_validation_class=UTF8Type
and key_validation_class=UTF8Type;

Add key_validation_class=UTF8Type;

 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: 20.0/14400
   Memtable thresholds: 0.290624997/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

[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-06-16 Thread donghwan Ahn (JIRA) 

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

donghwan Ahn commented on CASSANDRA-2497:
-

Thanks !

I Have been very helpful

 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: 20.0/14400
   Memtable thresholds: 0.290624997/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

[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-05-10 Thread Bilal Ahmed (JIRA) 

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

Bilal Ahmed commented on CASSANDRA-2497:


I am getting the same issue in 0.8.0.beta2 version.

 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: 20.0/14400
   Memtable thresholds: 0.290624997/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

[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-05-10 Thread Bilal Ahmed (JIRA) 

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

Bilal Ahmed commented on CASSANDRA-2497:


Thanks Jonathan!

Regards,
Bilal

Sent from my iPhone




 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: 20.0/14400
   Memtable thresholds: 0.290624997/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

[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-04-26 Thread Cathy Daw (JIRA) 

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

Cathy Daw commented on CASSANDRA-2497:
--

Retested and verified this is fixed in current build.

 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

 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: 20.0/14400
   Memtable thresholds: 0.290624997/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

[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-04-20 Thread Pavel Yaskevich (JIRA) 

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

Pavel Yaskevich commented on CASSANDRA-2497:


The problem was in the getKeyAsBytes method - it wasn't using information 
provided by cfdef.getKey_validation_class() (only comparator set by 'assume' 
statement or BytesType if it wasn't set). 

The fix was pretty trivial - make getKeyAsBytes use 
cfdef.getKey_validation_class() + printSliceList method was fixed to use 
getKeyComparatorForCF instead of just value from 'assume' statement.

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

 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: 20.0/14400
   Memtable thresholds: 0.290624997/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

[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-04-20 Thread Hudson (JIRA) 

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

Hudson commented on CASSANDRA-2497:
---

Integrated in Cassandra-0.8 #30 (See 
[https://builds.apache.org/hudson/job/Cassandra-0.8/30/])


 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

 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: 20.0/14400
   Memtable thresholds: 0.290624997/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

[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-04-19 Thread Jonathan Ellis (JIRA) 

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

Jonathan Ellis commented on CASSANDRA-2497:
---

Pavel, can you describe the problem + fix?

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

 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: 20.0/14400
   Memtable thresholds: 0.290624997/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

[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-04-18 Thread Cathy Daw (JIRA) 

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

Cathy Daw commented on CASSANDRA-2497:
--

Restarting the CLI did not fix the issue.
Adding an assume for the key type did.

{code}
[default@cathy] set users['jsmith']['password']='ch@ngem3';
org.apache.cassandra.db.marshal.MarshalException: cannot parse 'jsmith' as hex 
bytes

[default@cathy] assume users keys as ascii;
Assumption for column family 'users' added successfully.

[default@cathy] set users['jsmith']['password']='ch@ngem3';
Value inserted.
{code}


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


 *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: 20.0/14400
   Memtable thresholds: 0.290624997/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

[jira] [Commented] (CASSANDRA-2497) CLI: issue with keys being interpreted as hex and causing SET statement to fail

2011-04-18 Thread Pavel Yaskevich (JIRA) 

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

Pavel Yaskevich commented on CASSANDRA-2497:


Than it seems to be a problem in the core as CLI always runs 
system_update(add)_column_family with the newest attributes passed in the 
executeUpdate(Add)ColumnFamily and then re-caches CF by calling 
describe_keyspace. Looks like value from the key_validation_class is not stored 
properly on the cassandra end (just tested that). 

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


 *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: 20.0/14400
   Memtable thresholds: 0.290624997/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