Re: cassandra_migration_wait

2020-01-13 Thread Ben Mills
Hi Reid, Many thanks! Very helpful. Will have a look at that source. Ben On Mon, Jan 13, 2020 at 2:08 PM Reid Pinchback wrote: > I can’t find it anywhere either, but I’m looking at a 3.11.4 source > image. From the naming I’d bet that this is being used to feed the >

Re: cassandra_migration_wait

2020-01-13 Thread Reid Pinchback
I can’t find it anywhere either, but I’m looking at a 3.11.4 source image. From the naming I’d bet that this is being used to feed the cassandra.migration_task_wait_in_seconds property. It’s already coded to have a default of 1 second, which matches what you are seeing in the shell script

cassandra_migration_wait

2020-01-13 Thread Ben Mills
Greetings, We are running Cassandra 3.11.2 in Kubernetes and use a run.sh to set some environment variables and a few other things. This script includes: CASSANDRA_MIGRATION_WAIT="${CASSANDRA_MIGRATION_WAIT:-1}" setting this environment variable to "1". I looked for documentation on this but

Re: [E] bug in cluster key push down

2020-01-13 Thread Hannu Kröger
No, I think it was originally correct. If partition key has multiple parts, then you need parenthesis around parts of partition key. Hannu > On 13. Jan 2020, at 14.30, Saha, Sushanta K > wrote: > >> primary key (partition, clustering1, clustering2) >> >> So, the partitioning key has three

Re: [E] Re: bug in cluster key push down

2020-01-13 Thread Saha, Sushanta K
*primary key (partition, clustering1, clustering2)* So, the partitioning key has three columns. You need to specify values for all three columns. For clustering columns, you need another parenthesis like *primary key (partition, (clustering1, clustering2))* * Sushanta* On Sun, Jan 12, 2020