h wrote:
incRef/decRef methods are protected. Is there any other way to use
these
methods without extending it?
Regards
Ganesh
- Original Message - From: "Michael McCandless" <
[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 15, 2008 2:31 PM
Subject: Re: Closing Index Rea
essage - From: "Michael McCandless" <
>> [EMAIL PROTECTED]>
>> To:
>> Sent: Wednesday, October 15, 2008 2:31 PM
>> Subject: Re: Closing Index Reader
>>
>>
>>
>>> Ganesh wrote:
>>>
>>> Yes. Once the Indexreader is clos
tober 15, 2008 2:31 PM
Subject: Re: Closing Index Reader
Ganesh wrote:
Yes. Once the Indexreader is closed, you should not do make any
calls with that object.
Extend the IndexReader to add support for reference count. Close
the reader once the count is zero.
Actually you can just use the
incRef/decRef methods are protected. Is there any other way to use these
methods without extending it?
Regards
Ganesh
- Original Message -
From: "Michael McCandless" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 15, 2008 2:31 PM
Subject: Re: Closing Index Reader
Ganesh wrote:
Yes. Once the Indexreader is closed, you should not do make any
calls with that object.
Extend the IndexReader to add support for reference count. Close the
reader once the count is zero.
Actually you can just use the [expert] incRef/decRef methods on
IndexReader to track i
]>
To:
Sent: Wednesday, October 15, 2008 8:05 AM
Subject: Closing Index Reader
Hello, I am using the reopen method in the IndexReader class. In the case
of the IndexReader being updated, I would like to create a new
IndexSearcher
and close the old IndexReader. When closing an instance of IndexRe
Hello, I am using the reopen method in the IndexReader class. In the case
of the IndexReader being updated, I would like to create a new IndexSearcher
and close the old IndexReader. When closing an instance of IndexReader, do I
have to wait for currently executing searches (through an IndexSearche
