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

donal zang commented on CASSANDRA-2231:
---------------------------------------

In CompositeType.java I find this:
 37  * 'end-of-component' byte should always be 0 for actual column name.
 38  * However, it can set to 1 for query bounds. This allows to query for the
 39  * equivalent of 'give me the full super-column'. That is, if during a slice
 40  * query uses:
 41  *   start = <3><"foo".getBytes()><0>
 42  *   end   = <3><"foo".getBytes()><1>
 43  * then he will be sure to get *all* the columns whose first component is 
"foo".

Is this also apply to DynamicCompositeType ? When I use it in a  query end with 
'0x01', there's an Exception "Invalid bytes remaining after an end-of-component 
at component0"

> Add CompositeType comparer to the comparers provided in 
> org.apache.cassandra.db.marshal
> ---------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2231
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2231
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Contrib
>            Reporter: Ed Anuff
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 0.8.1
>
>         Attachments: 
> 0001-Add-compositeType-and-DynamicCompositeType-v2.patch, 
> 0001-Add-compositeType-and-DynamicCompositeType-v3.patch, 
> 0001-Add-compositeType-and-DynamicCompositeType-v4.patch, 
> 0001-Add-compositeType-and-DynamicCompositeType_0.7.patch, 
> CompositeType-and-DynamicCompositeType.patch, 
> edanuff-CassandraCompositeType-1e253c4.zip
>
>
> CompositeType is a custom comparer that makes it possible to create 
> comparable composite values out of the basic types that Cassandra currently 
> supports, such as Long, UUID, etc.  This is very useful in both the creation 
> of custom inverted indexes using columns in a skinny row, where each column 
> name is a composite value, and also when using Cassandra's built-in secondary 
> index support, where it can be used to encode the values in the columns that 
> Cassandra indexes.  One scenario for the usage of these is documented here: 
> http://www.anuff.com/2010/07/secondary-indexes-in-cassandra.html.  Source for 
> contribution is attached and has been previously maintained on github here: 
> https://github.com/edanuff/CassandraCompositeType

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

Reply via email to