It's certainly possible to have a CompositeType key_validation_class. What
made you think that you cannot?
On Mon, Jul 9, 2012 at 7:48 AM, prasenjit mukherjee wrote:
> Any reason we dont have CompositeType data structure for
> key_validation_class ( ref:
>
> http://www.data
Any reason we dont have CompositeType data structure for
key_validation_class ( ref:
http://www.datastax.com/docs/0.8/configuration/storage_configuration#key-validation-class)
? I would like to create row_names in the form username:mmddhhmm
( e.g. joe:201206092312 ). I can still do that
Thanks a bunch.
On Wed, Feb 29, 2012 at 12:51 PM, juri wrote:
> This is a good example.
>
> https://gist.github.com/1847261
>
> I couldn't make it work with DynamicComposite though.
>
>
>
This is a good example.
https://gist.github.com/1847261
I couldn't make it work with DynamicComposite though.
d the second value will be the length of that date
range.
Each column inside each row will represent metadata related to a
specific product on during that date range.
My question would be do I get any advantages with using the
CompositeType for my row key versus doing manual concatenation of the
advantages with using the CompositeType
for my row key versus doing manual concatenation of the two values in my
code?
On Tue, Feb 28, 2012 at 10:41 AM, Chris Gerken
wrote:
> Phil,
>
> That's the problem with examples :)
>
> Row keys can be composite values. That works j
25 AM, Philip Shon wrote:
> I have not found any examples of utilizing a CompositeType of
> DynamicCompositeType as a row key. Is doing this frowned upon? All the
> examples I've seen have been using a CompositeType only for Column names (or
> values).
>
> My particular use
I have not found any examples of utilizing a CompositeType of
DynamicCompositeType as a row key. Is doing this frowned upon? All the
examples I've seen have been using a CompositeType only for Column names
(or values).
My particular use case involves having the two components in the key be
hen delete by name.
>
> Cheers
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 23/02/2012, at 8:08 PM, Praveen Baratam wrote:
>
>> More precisely,
>>
>> Lets say we have a CF with
> You need to read and then delete by name.
>
> Cheers
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 23/02/2012, at 8:08 PM, Praveen Baratam wrote:
>
> More precisely,
>
> Lets say we have a CF with the fol
---
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 23/02/2012, at 8:08 PM, Praveen Baratam wrote:
> More precisely,
>
> Lets say we have a CF with the following spec.
>
> create column family Test
> with comparator = 'CompositeType(UTF8Ty
More precisely,
Lets say we have a CF with the following spec.
create column family Test
with comparator = 'CompositeType(UTF8Type,UTF8Type,UTF8Type)'
and key_validation_class = 'UTF8Type'
and default_validation_class = 'UTF8Type';
And I have col
It was developed for 0.7x but we then made a few changes so that it
would work with 0.8-rc1 that broke the 0.7 compatibility. The idea at
the time was to do a 0.7 branch for it but it looks like that never
got checked in. If you roll back to the previous commit it should
give you a version that w
If your version of Cassandra does not support composite you need to
upgrade, If the server is not aware the column is composite it will not be
able to use them to full effect. You likely will not get the sorting and
slicing capabilities you want.
Edward
On Sat, Nov 5, 2011 at 4:44 AM, Guy Incogni
Is this a lib I can just drop into a 0.7 instance of cassandra and use?
I'm not sure what to make of the README about not using it with versions
earlier than 0.8.0-rc1.
https://github.com/riptano/hector-composite
the goal is to start using CompositeTypes in 0.7 (which I can't upgrade
to 0.8
> definition for comparator org.apache.cassandra.db.marshal.CompositeType.
> at
> org.apache.cassandra.db.marshal.TypeParser.getRawAbstractType(TypeParser.java:319)
> at
> org.apache.cassandra.db.marshal.TypeParser.getAbstractType(TypeParser.java:247)
> at org.apache.cassandra.db.marshal.TypeParser.parse(TypeParser.ja
.
> at
> org.apache.cassandra.db.marshal.TypeParser.getRawAbstractType(TypeParser.java:319)
> at
> org.apache.cassandra.db.marshal.TypeParser.getAbstractType(TypeParser.java:247)
> at org.apache.cassandra.db.marshal.TypeParser.parse(TypeParser.java:83)
> at org.ap
.cassandra.db.marshal.CompositeType.
at
org.apache.cassandra.db.marshal.TypeParser.getRawAbstractType(TypeParser.java:319)
at
org.apache.cassandra.db.marshal.TypeParser.getAbstractType(TypeParser.java:247)
at org.apache.cassandra.db.marshal.TypeParser.parse(TypeParser.java:83)
at
You should give a look at https://github.com/edanuff/CassandraIndexedCollections
This is a rather good starting point for Composites.
2011/8/15 Stephen Pope :
> Hey, is there any documentation or examples of how to use the CompositeType?
> I can't find anything about it on the
Hey, is there any documentation or examples of how to use the CompositeType? I
can't find anything about it on the wiki or the datastax docs.
Cheers,
Steve
column name are
> these keys
>
> On Fri, Jul 22, 2011 at 12:37 PM, Nate McCall wrote:
> >> yes,but why would you use CompositeType if you don't need range query?
> >
> > If you were doing composite keys anyway (common approach with time
> > series data for ex
Exactly. In any case, I just answered my own question. If I need
range, I can just make another column family where the column name are
these keys
On Fri, Jul 22, 2011 at 12:37 PM, Nate McCall wrote:
>> yes,but why would you use CompositeType if you don't need range query?
>
> yes,but why would you use CompositeType if you don't need range query?
If you were doing composite keys anyway (common approach with time
series data for example), you would not have to write parsing and
concatenation code. Particularly useful if you had mixed types in the
key.
On 22/07/2011 17:56, Patrick Julien wrote:
I can still use it for keys if I don't need ranges then? Because for
what we are doing we can always re-assemble keys
yes,but why would you use CompositeType if you don't need range query?
On Fri, Jul 22, 2011 at 11:38 AM, Donal Zang wrot
I can still use it for keys if I don't need ranges then? Because for
what we are doing we can always re-assemble keys
On Fri, Jul 22, 2011 at 11:38 AM, Donal Zang wrote:
> If you are using OPP, then you can use CompositeType on both key and column
> name; otherwise(Random Partition
If you are using OPP, then you can use CompositeType on both key and
column name; otherwise(Random Partition), just use it for columns.
On 22/07/2011 17:10, Patrick Julien wrote:
With the current implementation of CompositeType in Cassandra 0.8.1,
is it recommended practice to try to use a
With the current implementation of CompositeType in Cassandra 0.8.1,
is it recommended practice to try to use a CompositeType as the key?
Or are both, column and key, equally well supported?
The documentation on CompositeType is light, well non-existent really, with
key_validation_class set to
e ("---0000-") and end of time
> ("----")
>
> I want to slice only across the Time component of the Composite.
>
> Is this possible?
>
> Anthony
>
>
> On Mon, Jul 18, 2011 at 10:52 AM, A
y across the Time component of the Composite.
Is this possible?
Anthony
On Mon, Jul 18, 2011 at 10:52 AM, Anthony Ikeda wrote:
> Is this possible? I'm trying to create a Column Family with a CompositeType
> comparator, but I keep getting an error:
>
> create column fami
Is this possible? I'm trying to create a Column Family with a CompositeType
comparator, but I keep getting an error:
create column family Transactions with comparator = CompositeType(UTF8Type,
UUIDType) and keys_cached=1 and rows_cached=1000;
Syntax error at position 84: missing E
30 matches
Mail list logo
