Type: New Feature
Resolution: Won't Fix
Fix Version/s: None
This issue is related to discussion on mailing list:
Idea is to support Cassandra build-in index search over specified set of rows.
From API view:
It can be extension of get_indexed_slices, for example:
List<byte> rowKys = ... ; //list of row keys
IndexClause indexClause = new IndexClause();
indexClause.setKeys(keys); //required API to set list of keys
List finalResult = get_indexed_slices(colParent, indexClause, colPredicate, cLevel);
or create specified API method.
From conceptual view it was noticed:
That would be implementation of sub query.
The index clause is applied to the set of all rows in the database, not a sub set, applying them to a sub set is implicitly supporting a sub query
Benefits of this feature is that search can be split in 2 stages:
1) Search over external engine (for example full text search)
2) Cassandra build-in index search over result from first stage
This combination could solve most of limitations that came with solution based only on external search engine.