CREATE KEYSPACE data WITH replication = {'class': 'NetworkTopologyStrategy',
'dc1': '3', 'dc2': '3'} AND durable_writes = true;
cqlsh> select * from system_schema.keyspaces ;
keyspace_name | durable_writes | replication
++
Partition key has value as:
MWY4MmI0MTQtYTk2YS00YmRjLTkxNDMtOWU0MjM1OWU2NzUy other column is blob.
On Tuesday, June 19, 2018, 6:07:59 PM EDT, Joshua Galbraith
wrote:
> id text PRIMARY KEY
What values are written to this id field? Can you give us some examples or
explain the general
Okay, that string appears to be a base64-encoded version 4 UUID. Why not
use Cassandra's UUID data type to store that directly rather than storing
the longer base64 string as text? What does the UUID represent? Is it
identifying a unique product, an image, or some other type of object? When
and how
Hi Joshua,
Okay, that string appears to be a base64-encoded version 4 UUID. Why not use
Cassandra's UUID data type to store that directly rather than storing the
longer base64 string as text? --> It's an old application and the person who
coded it, has left the company.What does the UUID repr
>Also, our partition keys are not distributed evenly as I had pasted output
earlier.
Thanks, I see that now. Can you share the full output of nodetool tablestats
and nodetool tablehistograms?
Out of curiosity, are you running repairs on this cluster? If so, what type
of repairs are you running a
Hello!
Using Cassandra 2.2.11, I observe behaviour, that is very similar to
https://issues.apache.org/jira/browse/CASSANDRA-12860
Steps to reproduce:
1. Set up a cluster: ccm create five -v 2.2.11 && ccm populate -n 5
--vnodes && ccm start
2. Import some keyspace into it (approx 50 Mb of data)
3.
Yes, Server uses the encryption client-node and server-server both and
running fine with JDKSSL options but problem is with NettySSLOptions.
On Tue, Jun 19, 2018 at 7:04 PM, Jonathan Haddad wrote:
> Is the server configured to use encryption?
>
> On Tue, Jun 19, 2018 at 3:59 AM Jahar Tyagi wrot
Hi,
I think LWT feature is introduced for your kind of usecases only - you
don't want other requests to be updating the same data at the same time
using Paxos algo(2 Phase commit).
So, IMO your usecase makes perfect sense to use LWT to avoid concurrent
updates.
If your issue is not the concurren
