Re: Secondary Index

Thanks for the reply. I just have one more doubt, please do clarify this. Will be there any performance difference between these 2 queries for the above table. 1. select * from ks1.cf1 where status=1; 2. select * from ks1.cf1 where id1=123456 and status=1; where id1 is partition key and status

Re: Secondary Index

Hi, beyond scope of your question (as you use 2.1.17) but starting from v3.4 SASI is avaialble, doc is about DSE, but is applicable for free version as well. Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting On Mon, 19 Jun 2017 14:00:40 -0400 techpyaasa .

Re: Secondary Index

Thanks for the reply vladimir but we can't upgrade c* binary that soon as we have a quick requirement for the use case I said in my first mail. So just wanted to know the difference between the 2 queries I asked in my last mail 1. select * from ks1.cf1 where status=1; 2. select * from ks1.cf1 wh

Re: Repairing question

> Not sure since what version, but in 3.10 at least (I think its since 3.x > started) full repair does do anti-compactions and marks sstables as repaired. Thanks for the correction, anti-compaction after full repairs was added on 2.2 CASSANDRA-7586 but removed on 4.0 by CASSANDRA-9143. Just for c

Re: Large temporary files generated during cleaning up

Thanks for the reply. I tried with "./nodetool cleanup -j 1". It's very useful because the command reduces the amount of free space needed while only one sstable is being processed at a time. From: Alain RODRIGUEZ Date: 2017-06-20 17:03 To: user Subject: Re: Large temporary files generated duri