i second UUID they're your friend
On Sat, Feb 28, 2015 at 10:56 AM, Brian Sam-Bodden wrote:
> I agree with Peter. I typically keep in Cassandra just the data that will
> benefit from it's distribution and replication capabilities. Most of the
> applications in which I use Cassandra also use a re
I agree with Peter. I typically keep in Cassandra just the data that will
benefit from it's distribution and replication capabilities. Most of the
applications in which I use Cassandra also use a relational DB, so best
tool for the job type of approach.
And for the PK it's implied; some identifier
Hate to be the one to point this out, but that is not the ideal use case
for Cassandra.
If you really want to brute force it and "make it fit" cassandra, the
easiest way is to create a class called Index. The index class would have
name, phone and address fields. The hashcode and equals method wou
As far as I know there is no such thing. You could make that value a single
PK for the table therefore guaranteeing uniqueness and check on insert with
`IF NOT EXISTS` to prevent dups. Of course that works just for one value,
if you have multiple values a compound PK will still let dups in for a
gi
I want to make unique constraint in Cassandra . As i want that all the
value in my column be unique in my column family
example : name-rahul ,phone-123, address-abc
now i want that in this row no values equal to rahul ,123 and abc get
inserted again on searching on datastax i found that i can ac
