[
https://issues.apache.org/jira/browse/LUCENE-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208374#comment-13208374
]
Andrzej Bialecki commented on LUCENE-3788:
-------------------------------------------
Hi Uwe,
bq. It would be good if you would communicate with Robert about that
Lucid-internal problem
bq. this issue was created explicitely for Solr and your company.
This is not helpful ... this was IMHO a legitimate doubt about the use of trunk
APIs, and if there's a possible confusion about how to use the new IR-s then
probably I'm not the only one confused, and it's irrelevant whether I'm working
today for Lucid or for any other company.
bq. but it's easy to solve, I can also help.
And this is helpful. :) Thanks, let's close this issue.
> 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]
