cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul R. Brown (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-626) Polymorphic status of keys as byte[] and String is confusing
Date Wed, 13 Jan 2010 20:53:54 GMT

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

Paul R. Brown commented on CASSANDRA-626:
-----------------------------------------

@jbellis:
I can't find the specific point in the wiki that confused me.  It might be that the various
partitioners support byte-level ordering of keys while the Thrift API only supports UTF-8
encoding on the wire?  I think that if you were to add a simple explanation on the API page
(http://wiki.apache.org/cassandra/API) that keys are always Strings and encoded as UTF-8 on
the wire and on disk, then that would work for me.

btw, as you guys edge toward graduation, you'll have to be careful about having only committers
edit artifacts; otherwise, changes have to go through the submission and patch process to
be clean.

@forsini:
I have to go back and reread the documentation.  When I first read through the Cassandra documentation,
I didn't pick up that row keys are always Strings.  

> Polymorphic status of keys as byte[] and String is confusing
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-626
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-626
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Documentation & website
>    Affects Versions: 0.5
>            Reporter: Paul R. Brown
>            Priority: Minor
>
> As part of some experiments with Cassandra, I wanted to build a column space with row
keys that are Long (64-bit binary blocks) and column names that are Long, and this seems to
be supported by the data configuration infrastructure:
> {code}<ColumnFamily ColumnType="Super"
>   CompareWith="LongType"
>   CompareSubcolumnsWith="LongType"
>   Name="UserEvent"/>{code}
> But there is no obvious way to perform the insert over the Thrift interface via Java;
I tried various ways of turning the Long bits into Strings for the API call, but the insert
call returns:
> {code}Exception in thread "main" InvalidRequestException(why:A long is exactly 8 bytes){code}
> The status of keys as either byte[] or String and the mechanisms for inserting need to
be clarified and surfaced in the API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message