[
https://issues.apache.org/jira/browse/OAK-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393647#comment-15393647
]
Chetan Mehrotra edited comment on OAK-4566 at 7/28/16 10:08 AM:
----------------------------------------------------------------
Feature branch at https://github.com/chetanmeh/jackrabbit-oak/tree/OAK-4566
Change view
https://github.com/chetanmeh/jackrabbit-oak/compare/trunk...chetanmeh:OAK-4566
was (Author: chetanm):
Feature branch at https://github.com/chetanmeh/jackrabbit-oak/tree/OAK-4566
> Multiplexing store support in Lucene Indexes
> --------------------------------------------
>
> Key: OAK-4566
> URL: https://issues.apache.org/jira/browse/OAK-4566
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: lucene
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.6
>
>
> Similar to OAK-3403 we need support multiplexing store in Lucene indexes.
> This can be done by having multiple directories under given index definition.
> For e.g. currently the Lucene indexes for an index /oak:index/assetIndex are
> stored in node /oak:index/assetIndex/:dir. For supporting multiple indexes
> which get stored in different stores we can have structure like
> {noformat}
> /oak:index/assetIndex
> + :oak:mount1-dir
> + :dir
> {noformat}
> In above structure index content for paths which are part of mount1 would be
> store in Lucene files stores under {{:oak:mount1-dir}} while the rest go in
> default location {{:dir}
> # *Writing* - At the time of indexing the {{LuceneIndexEditor}} should pick
> up correct writer i.e. one which is mapped to right directory node in
> repository
> # *Reading* - For reading we would have one {{IndexSearcher}} per directory
> node and then query would be executed against both and a joined cursor would
> be made
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
