cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12910) SASI: calculatePrimary() always returns null
Date Tue, 06 Dec 2016 16:48:58 GMT


Alex Petrov commented on CASSANDRA-12910:

I've used a simple test to verify and I think your fix is good. Although I do not see a good
way to test it without exposing a lot of internals for now.

So what happens is in {{getView}} instead of querying all SSTables, we're going to query only
those which would (possibly) yield results for the expression that involves the least amount
of sstables. The order does not matter, as it's going to be changed later in {{RangeIntersectionIterator}},
depending on the size of token trees. 

I've tested the patch on our CI: 


> SASI: calculatePrimary() always returns null
> --------------------------------------------
>                 Key: CASSANDRA-12910
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: sasi
>            Reporter: Corentin Chary
>            Assignee: Corentin Chary
>            Priority: Minor
>             Fix For: 3.x
>         Attachments: 0002-sasi-fix-calculatePrimary.patch
> While investigating performance issues with SASI  (
if you want to know more) I ended finding calculatePrimary() in which
apparently should return the "primary index".
> It lacks documentation, and I'm unsure what the "primary index" should be, but apparently
this function never returns one because primaryIndexes.size() is always 0.
> I'm unsure if the proper fix is checking if the collection is empty or reversing the
operator (selecting the index with higher cardinality versus the one with lower cardinality).

This message was sent by Atlassian JIRA

View raw message