[
https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759891#action_12759891
]
Michael McCandless commented on LUCENE-1458:
I wrote up first cut of the tople
[
https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759910#action_12759910
]
John Wang commented on LUCENE-1458:
---
Hi Mike:
Truly awesome work!
Quick ques
[
https://issues.apache.org/jira/browse/LUCENE-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1925.
Resolution: Fixed
Thanks John & Tim!
> In IndexSearcher class, make subReader and
: Thanks Mark for the pointer, I thought somehow that lucene closed them as a
: convenience, I don't know if it did that in previous releases (aka 2.4.1) but
: I'll close them myself from now on.
FWIW: As far as i know, Lucene has always closed the Reader for you when
calling addDocument/updateD
AFAIK, application has always assume the responsibility of closing
IndexReader instances.
However, with 2.9, this is the first time, IndexReader can be instantiated
via a getter from IndexWriter.
Previously, IndexReaders are usually constructed via IndexReader.open
factory method. Having a getter
Oops, I completely misunderstood the question. I thought this is about
IndexReaders :)
-John
On Sun, Sep 27, 2009 at 11:14 AM, John Wang wrote:
> AFAIK, application has always assume the responsibility of closing
> IndexReader instances.
> However, with 2.9, this is the first time, IndexReader c
Wrong Reader ;)
- Mark
http://www.lucidimagination.com (mobile)
On Sep 26, 2009, at 11:14 PM, John Wang wrote:
AFAIK, application has always assume the responsibility of closing
IndexReader instances.
However, with 2.9, this is the first time, IndexReader can be
instantiated via a gette
