Is SASI index in Cassandra efficient for high cardinality columns?

I understand Secondary Indexes in general are inefficient on high cardinality columns but since SASI is built from scratch I wonder if the same argument applies there? If not, Why? Because I believe primary keys in Cassandra are indeed indexed and since Primary key is supposed to be the column

Re: Is SASI index in Cassandra efficient for high cardinality columns?

Define precisely what you mean by "high cardinality columns". Do you mean: 1) a single indexed value is present in a lot of rows 2) a single indexed value has only a few (if not just one) matching row On Sat, Oct 15, 2016 at 8:37 AM, Kant Kodali wrote: > I understand

Re: Is SASI index in Cassandra efficient for high cardinality columns?

Well I went with the definition from wikipedia and that definition rules out #1 so it is #2 and it is just one matching row in my case. On Sat, Oct 15, 2016 at 2:40 AM, DuyHai Doan wrote: > Define precisely what you mean by "high cardinality columns". Do you mean: > > 1)

Re: Is SASI index in Cassandra efficient for high cardinality columns?

If each indexed value has very few matching rows, then querying using SASI (or any impl of secondary index) may scan the whole cluster. This is because the index are "distributed" e.g. the indexed values stay on the same nodes as the base data. And even SASI with its own data-structure will not

[GitHub] cassandra issue #76: CASSANDRA-12541, CASSANDRA-12542, CASSANDRA-12543 and C...

Github user doanduyhai commented on the issue: https://github.com/apache/cassandra/pull/76 Can you give some description of the issue ? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] cassandra issue #76: CASSANDRA-12541, CASSANDRA-12542, CASSANDRA-12543 and C...

Github user deshpamit commented on the issue: https://github.com/apache/cassandra/pull/76 HP Fortify Analysis flagged Portability Flaw: Locale Dependent Comparison https://issues.apache.org/jira/browse/CASSANDRA-12541 same issue for all defects --- If your project is set up for

[GitHub] cassandra pull request #76: CASSANDRA-12541, CASSANDRA-12542, CASSANDRA-1254...

GitHub user deshpamit opened a pull request: https://github.com/apache/cassandra/pull/76 CASSANDRA-12541, CASSANDRA-12542, CASSANDRA-12543 and CASSANDRA-12545 You can merge this pull request into a Git repository by running: $ git pull https://github.com/deshpamit/cassandra

[GitHub] cassandra issue #76: CASSANDRA-12541, CASSANDRA-12542, CASSANDRA-12543 and C...

Github user edwardcapriolo commented on the issue: https://github.com/apache/cassandra/pull/76 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if