[
https://issues.apache.org/jira/browse/LUCENE-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844168#action_12844168
]
Michael McCandless commented on LUCENE-1879:
--------------------------------------------
I like the ParallelWriter (index slices) approach!
It sounds quite feasible and more "direct" in how the PW controls each
sub writer. It should be as simple as setting null merge
policy/scheduler on the subs would mean they do no merging themselves,
but then the PW invokes their .merge methods to explicitly merge at
the right times. Vs the current approach that makes "faker" merge
policy/scheduler (I think?).
Some of this will require IW to open up some APIs -- eg making docID
assignment a separate method call. Likely many of these will just be
protected APIs w/in IW.
> Parallel incremental indexing
> -----------------------------
>
> Key: LUCENE-1879
> URL: https://issues.apache.org/jira/browse/LUCENE-1879
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Index
> Reporter: Michael Busch
> Assignee: Michael Busch
> Fix For: 3.1
>
> Attachments: parallel_incremental_indexing.tar
>
>
> A new feature that allows building parallel indexes and keeping them in sync
> on a docID level, independent of the choice of the MergePolicy/MergeScheduler.
> Find details on the wiki page for this feature:
> http://wiki.apache.org/lucene-java/ParallelIncrementalIndexing
> Discussion on java-dev:
> http://markmail.org/thread/ql3oxzkob7aqf3jd
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
