certificate pinning feature

Hello, Is it possible to have a CA certificates in truststores, but do any kind of certificate pinning, i.e. adding extra requirements for certificates (matching hostname or thumbprint) to be trusted by Cassandra for internode and/or client communication? The only way to achieve this I

Re: Partition range incremental repairs

> > I can't recommend *anyone* use incremental repair as there's some pretty > horrible bugs in it that can cause Merkle trees to wildly mismatch & result > in massive overstreaming. Check out > https://issues.apache.org/jira/browse/CASSANDRA-9143 >

Re: Partition range incremental repairs

Hi Anuj, Thanks for the reply. 1). We are using Cassandra 2.2.8, and our repair commands we are comparing are "nodetool repair --in-local-dc --partitioner-range” and "nodetool repair --in-local-dc” Since 2.2 I believe inc repairs are the default - that seems to be confirmed in the logs that

Re: Huge Batches

Hi Justin, We have very few columns in PK(max 2 partition columns , max 2 clustering columns) and it wont have huge data/huge number of primary keys. I just wanted to print the names & values of these columns for huge batches. PS: we are using c*-2.1 Thanks for reply @Justin and @Akhil On Fri,

Re: Reg:- Data Modelling For Hierarchy Data

MV is a good option, but in case of RF, suppose If we are using RF =3 then it will duplicate on 3*3 times which will be unwanted in case we insert a lot of users. But I think we can go with MV also. On Fri, Jun 9, 2017 at 4:41 PM, Jacques-Henri Berthemet < jacques-henri.berthe...@genesys.com>

RE: Reg:- Data Modelling For Hierarchy Data

For query 2) you should have a second table, secondary index is usually never recommended. If you’re planning to use Cassandra 3.x you should take a look at materialized views (MVs): http://cassandra.apache.org/doc/latest/cql/mvs.html

Re: Reg:- Data Modelling For Hierarchy Data

Hi, Yes, I am following with single Users table. Suppose my query patterns are:- 1) Select user by email. 2) Select user by user_type 1st query pattern will satisfy the Users table, but in the case of second query pattern, either have to go with another table like user_by_type or I have to create

RE: Reg:- Data Modelling For Hierarchy Data

Hi, According to your model a use can only be of one type, so I’d go with a very simple model with a single table: string email (PK), string user_type, map attributes user_type can be Buyer, Master_Seller, Slave_Seller and all other columns go into attribute map as long as all