Hi Devs!
As this is related to a future improvement in Cassandra I thought this is
the appropriate mailing list.
I was reading a bit on HBase, it provides a facility to version rows with
number of version, etc can be specified in schema.
Although this can be easily achieved in cassandra as well
be
created from existing classes pls let me know as well would love to build
and share one.
Best Regards,
Bhuvan Rawal
Hi Matt,
I suggested the resources keeping in mind the ease with which one can
learn. My idea was not to disrespect Apache or community in any form, it
was just to facilitate learning of a Newbie.
While having a good wiki would be amazing and I believe we all agree on
this Thread that current
Hi Deepak,
You can try Datastax Docs, they are most extensive and updated
documentation available.
As Cassandra is a fast developing technology I wonder if there is a Book in
the market which covers latest features like Materialized Views/ SASI Index
or new SSTable Format. I believe the best
Hi Tyler/Doan,
If we have already reached till the cell level and put the LWT condition on
it im sure from a design standpoint it shouldnt be really difficult to get
the cell write time and verify the same, maybe to be considered in a future
release. In this case it looks cleaner and if
Now try to use the write time in LWT
superuser@cqlsh:test_keyspace> update test set count=8 where part_k=2390
and clust_k='Test Ck Value' if writetime(count)=1462974475292000;
SyntaxException:
Best Regards,
Bhuvan Rawal
Hi,
We are modelling schema for database revamp from mysql to Cassandra. It has
been recommended in several places that column names must be kept as small
as possible to optimise disk storage.
I have a doubt here, why can't we map column names and store it as an
index, say in memory. I mean,
