at 11:27 AM, Mayank <4may...@gmail.com> wrote:
> Hi Aaron,
>
> I did mean 1000 columns. But I see your point.
> The current CF schema has user_id as the row key and unnamed column order_num
> = order info as the col-val pair. The plan is to add named columns
> order_attr1
gt; safely assume that its related indexes will also expire?
> Yes
>
> >
> > http://www.datastax.com/docs/1.1/ddl/indexes
> > Maintaining Secondary Indexes
> Emailed to ask for clarification.
>
> Cheers
>
>
> -----
> Aaron Morton
> Freela
Thanks guys. I am working with Andy on this project.
Further questions on the secondary indexes:
Assuming we have 1000 columns in 1 row of the column family and about
900 of them have
NamedColumn1=1 and of those 900 only 10 of them also have NamedColumn2=1. If I
query for columns which have Named
node, commit logs, tried changing memtablethreadhold too, but
not help.
Am I missing something? I am quite sure people must be using it.
With regards,
Mayank
Sagar,
Consistency level defines how your reads and writes should work. You can
defer it according to your needs, defines what are your expectations
when you are reading/writing data. Hence, they are not static to
Keyspace/CF metadata.
With regards,
Mayank
On 08-03-2011 13:15, Sagar Kohli
ou if I
require help.
With regards,
Mayank
On 28-02-2011 23:07, Jeremy Hanna wrote:
One thing that could be done is the CFRW could be abstracted more so that it's
easier to extend and only the serialization mechanism is required to extend it.
That is, all of the core functionality r
, both thrift and avro mutations are
considered?
Please let me know if I missed some important point.
With regards,
Mayank
tried with another branch [1] of Cassandra 0.7 rc3
But it failed with following exception,
java.lang.ClassCastException: java.nio.HeapByteBuffer cannot be cast to [B
My mapper looks like,
MyMapper extends Mapper, Text,
FloatWritable>
Can some one help me to resolve this issue.
With regards,
May
