[
https://issues.apache.org/jira/browse/LUCENE-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208381#comment-13208381
]
Uwe Schindler commented on LUCENE-3788:
---------------------------------------
I did not want to complain, it was just already the idea behind LUCENE-3734!
Thanks for reminding that we may need some documentation!
Sorry for problems, but maybe the code pasted above helps. The whole reason
behind the issue LUCENE-3734 was to support this special case regading Solr and
the use of ParallelReaders, so I already did the work - because I expected that
this issue will be opened. I only wanted to help and prevent cluttering up the
Lucene API again and I am happy to support your further.
ParallelCompositeReader was also implemented to support a non-slow parallel
reader, I did a lot of work together with Mike to support PCR.
> Separate getting Directory from IndexReader from its concrete subclasses
> ------------------------------------------------------------------------
>
> Key: LUCENE-3788
> URL: https://issues.apache.org/jira/browse/LUCENE-3788
> Project: Lucene - Java
> Issue Type: Improvement
> Components: core/index
> Reporter: Andrzej Bialecki
> Attachments: LUCENE-3788.patch
>
>
> Currently only subclasses of DirectoryReader expose the underlying Directory
> via public final directory(). IMHO this aspect should be separated from
> DirectoryReader so that other IndexReader implementations could expose any
> underlying Directory if they wanted to. Specifically, I have a use case where
> I'd like to expose a synthetic Directory view of resources used for
> ParallelCompositeReader.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
