cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-11075) Consider making SASI the default index implementation
Date Thu, 28 Jan 2016 09:22:39 GMT


Sylvain Lebresne updated CASSANDRA-11075:
    Assignee: Pavel Yaskevich

> Consider making SASI the default index implementation
> -----------------------------------------------------
>                 Key: CASSANDRA-11075
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Pavel Yaskevich
> 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
> 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

View raw message