[
https://issues.apache.org/jira/browse/LUCENE-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891654#action_12891654
]
Jason Rutherglen commented on LUCENE-2555:
------------------------------------------
Shai, I think Mike has outlined the pros and cons in other
postings see:
https://issues.apache.org/jira/browse/LUCENE-2324?focusedCommentId=12891256&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acommenttabpanel#action_12891256
Basically when going to DWPTs we're losing shared doc stores
completely, and sharing between threads probably doesn't make
sense. However we can keep the reading of shared doc stores for
back compat. I think the confusing part in the code is the
writing of shared doc stores, and I'm glad that's going away. In
addition the DWPT code completely streamlines some of the most
confusing parts of the IndexWriter class tree (the wait notify,
and per thread logic in particular). Overall this will help
future folks when they're trying to customize IndexWriter, and
in addition, remove a layer of complexity, as we add yet another
layer of complexity with the RT code.
> Remove shared doc stores
> ------------------------
>
> Key: LUCENE-2555
> URL: https://issues.apache.org/jira/browse/LUCENE-2555
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: Realtime Branch
>
>
> With per-thread DocumentsWriters sharing doc stores across segments doesn't
> make much sense anymore.
> See also LUCENE-2324.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
