You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2011/08/01 20:55:09 UTC
[jira] [Created] (CASSANDRA-2982) Refactor secondary index api
Refactor secondary index api
----------------------------
Key: CASSANDRA-2982
URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
Project: Cassandra
Issue Type: Sub-task
Components: Core
Reporter: T Jake Luciani
Assignee: T Jake Luciani
Fix For: 1.0
Secondary indexes currently make some bad assumptions about the underlying indexes.
1. That they are always stored in other column families.
2. That there is a unique index per column
In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2982) Refactor secondary index api
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081968#comment-13081968 ]
Jonathan Ellis commented on CASSANDRA-2982:
-------------------------------------------
I don't think full index pluggability is a goal here. So I don't see the point of that.
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2982) Refactor secondary index api
Posted by "Jason Rutherglen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082874#comment-13082874 ]
Jason Rutherglen commented on CASSANDRA-2982:
---------------------------------------------
For the Lucene secondary index, we need to report back the RAM consumed. Then Cassandra can, then when Memtable + Lucene RAM buffer exceeds the threshold we can and will flush both.
Perhaps we can add an additional ram size method?
This brings up another probable issue, if Memtable flushes successfully and then Lucene is not able to commit.
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt, 2982-v2.txt, CASSANDRA-2982-v3.patch
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2982) Refactor secondary index api
Posted by "Pavel Yaskevich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Yaskevich updated CASSANDRA-2982:
---------------------------------------
Attachment: CASSANDRA-2982-v3.patch
v3 with minor formatting/annotation fixes and refactorings. Rebased with latest trunk (0bbc22c00dfcce3d0945e61e94dd91d78ed51a26).
+1 with Jonathan on keeping IndexType as I don't see the point of removing it and think that keeping public indexManager is fine and convenient.
So if nobody has any objections I think this is ready to be committed.
Great work, Jake!
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt, 2982-v2.txt, CASSANDRA-2982-v3.patch
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2982) Refactor secondary index api
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082039#comment-13082039 ]
Jonathan Ellis commented on CASSANDRA-2982:
-------------------------------------------
Want to give a high-level overview of the changes here?
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2982) Refactor secondary index api
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082885#comment-13082885 ]
Jonathan Ellis commented on CASSANDRA-2982:
-------------------------------------------
bq. if Memtable flushes successfully and then Lucene is not able to commit
for the existing indexes, we write the indexes first. if we fail, the "main" memtable will not be written. if we succeed and the "main" memtable fails, the main (technically, both, which is fine since the index flush is idempotent) will be replayed from commitlog.
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt, 2982-v2.txt, CASSANDRA-2982-v3.patch
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CASSANDRA-2982) Refactor secondary
index api
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082884#comment-13082884 ]
Jonathan Ellis edited comment on CASSANDRA-2982 at 8/11/11 3:37 AM:
--------------------------------------------------------------------
+1 v3
was (Author: jbellis):
+1
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt, 2982-v2.txt, CASSANDRA-2982-v3.patch
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2982) Refactor secondary index api
Posted by "Ed Anuff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082149#comment-13082149 ]
Ed Anuff commented on CASSANDRA-2982:
-------------------------------------
Given this level of abstraction, I wonder if Jake's original suggestion about replacing the IndexType enum with a classname makes more sense?
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2982) Refactor secondary index api
Posted by "Jason Rutherglen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082393#comment-13082393 ]
Jason Rutherglen commented on CASSANDRA-2982:
---------------------------------------------
I'd prefer a class name, it's much more pluggable. This makes sense given SecondaryIndex is an abstract class.
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2982) Refactor secondary index api
Posted by "T Jake Luciani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
T Jake Luciani updated CASSANDRA-2982:
--------------------------------------
Attachment: 2982-v1.txt
refactored api, should cover new index types. Should we consider removing IndexType enum and just use classname?
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2982) Refactor secondary index api
Posted by "T Jake Luciani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082123#comment-13082123 ]
T Jake Luciani commented on CASSANDRA-2982:
-------------------------------------------
Sure. I've abstracted the index management for a column family to SecondaryIndexManager. For a particular column a index type can be specified that is implemented by a SecondaryIndex subclass.
Index building and updating works the same but is now encapsulated by this API.
The search API is abstracted by a custom SecondaryIndexSearcher subclass which handles searching a IndexClause for columns of a specific index type.
This does not support searching across index types so all queries must accept index expressions of the same index type. Otherwise you get an exception.
The one thing I might change is not exposing the cfs indexmanager variable and instead expose all the index manager calls as part of the Cfs API that delegates to indexmanager.
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2982) Refactor secondary index api
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082884#comment-13082884 ]
Jonathan Ellis commented on CASSANDRA-2982:
-------------------------------------------
+1
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt, 2982-v2.txt, CASSANDRA-2982-v3.patch
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2982) Refactor secondary index api
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083065#comment-13083065 ]
Hudson commented on CASSANDRA-2982:
-----------------------------------
Integrated in Cassandra #1016 (See [https://builds.apache.org/job/Cassandra/1016/])
Refactoring of the secondary index api
patch by Jake Luciani; reviewed by Pavel Yaskevich for CASSANDRA-2982
xedin : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1156567
Files :
* /cassandra/trunk/src/java/org/apache/cassandra/db/MeteredFlusher.java
* /cassandra/trunk/src/java/org/apache/cassandra/db/index/SecondaryIndexManager.java
* /cassandra/trunk/src/java/org/apache/cassandra/db/Table.java
* /cassandra/trunk/src/java/org/apache/cassandra/cql/QueryProcessor.java
* /cassandra/trunk/test/unit/org/apache/cassandra/db/ColumnFamilyStoreTest.java
* /cassandra/trunk/src/java/org/apache/cassandra/db/index/keys/KeysIndex.java
* /cassandra/trunk/test/unit/org/apache/cassandra/db/CleanupTest.java
* /cassandra/trunk/src/java/org/apache/cassandra/db/compaction/CompactionManager.java
* /cassandra/trunk/src/java/org/apache/cassandra/db/index
* /cassandra/trunk/src/java/org/apache/cassandra/db/index/keys/KeysSearcher.java
* /cassandra/trunk/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
* /cassandra/trunk/src/java/org/apache/cassandra/service/IndexScanVerbHandler.java
* /cassandra/trunk/src/java/org/apache/cassandra/db/index/SecondaryIndex.java
* /cassandra/trunk/src/java/org/apache/cassandra/thrift/ThriftValidation.java
* /cassandra/trunk/CHANGES.txt
* /cassandra/trunk/src/java/org/apache/cassandra/db/index/SecondaryIndexBuilder.java
* /cassandra/trunk/src/java/org/apache/cassandra/db/index/keys
* /cassandra/trunk/src/java/org/apache/cassandra/streaming/StreamInSession.java
* /cassandra/trunk/src/java/org/apache/cassandra/db/index/SecondaryIndexSearcher.java
* /cassandra/trunk/test/unit/org/apache/cassandra/streaming/StreamingTransferTest.java
* /cassandra/trunk/test/unit/org/apache/cassandra/db/DefsTest.java
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt, 2982-v2.txt, CASSANDRA-2982-v3.patch
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2982) Refactor secondary index api
Posted by "T Jake Luciani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
T Jake Luciani updated CASSANDRA-2982:
--------------------------------------
Attachment: 2982-v2.txt
Fix formatting and comments, other git merge problems
> Refactor secondary index api
> ----------------------------
>
> Key: CASSANDRA-2982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2982
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: T Jake Luciani
> Assignee: T Jake Luciani
> Fix For: 1.0
>
> Attachments: 2982-v1.txt, 2982-v2.txt
>
>
> Secondary indexes currently make some bad assumptions about the underlying indexes.
> 1. That they are always stored in other column families.
> 2. That there is a unique index per column
> In the case of CASSANDRA-2915 neither of these are true. The new api should abstract the search concepts and allow any search api to plug in.
> Once the code is refactored and basically pluggable we can remove the IndexType enum and use class names similar to how we handle partitioners and comparators.
> Basic api is to add a SecondaryIndexManager that handles different index types per CF and a SecondaryIndex base class that handles a particular type implementation.
> This requires major changes to ColumnFamilyStore and Table.IndexBuilder
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira