Sylvain Lebresne created CASSANDRA-11075:
--------------------------------------------
Summary: Consider making SASI the default index implementation
Key: CASSANDRA-11075
URL: https://issues.apache.org/jira/browse/CASSANDRA-11075
Project: Cassandra
Issue Type: Improvement
Reporter: Sylvain Lebresne
We now have 2 secondary index implementation in tree: the old native ones and
SASI. Moving forward, that feels like one too much to maintain, especially
since it seems that SASI is an overall better implementation.
So we should gather enough data to decide if SASI is indeed always better (or
at least sufficiently better than we're convinced no-one would want to stick
with the native implementation), and if that's the case, we should consider
making it the default (and ultimately get rid of the current implementation).
So first, we should at least:
# double check that SASI handles all cases that the native implementation
handles. A good start would probably be run all our dtest and utests on a
version where SASI is hard-coded as default.
# compare the performance of SASI and native indexes. In particular our native
indexes, in all their weaknesses, have the advantage of not doing a
read-before-write. Haven't looked at SASI much so I don't know if it's the case
but anyway, we need numbers on both reads and writes.
Once we have that, if we do decide to make SASI the default, then we need to
figure out what is the upgrade path (and whether we add extra syntax for SASI
specific options).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
