Hi Ard,
Thanks for your reply, well, I think I have done right.
>Closing the IndexSearcher is best only after a deleteDocuments with a
>reader or changes with a writer.
>
>For performance reasons, it is better to not close the IndexSearcher if not
> needed
>
>Regarsd Ard
>
>>
>>
>> sorry, th
Closing the IndexSearcher is best only after a deleteDocuments with a reader or
changes with a writer.
For performance reasons, it is better to not close the IndexSearcher if not
needed
Regarsd Ard
>
>
> sorry, the subject should be "Should the IndexSearcher be
> closed after
> every sear
sorry, the subject should be "Should the IndexSearcher be closed after
every search completed"
~
>Hi,
>
>Should the IndexSearcher instance be closed after very search completed.
>
>I wrote a sample, but I have not closed the singleton instatnce of
>IndexSearcher unless IndexReader#isCurrent()
Hi,
Should the IndexSearcher instance be closed after very search completed.
I wrote a sample, but I have not closed the singleton instatnce of
IndexSearcher unless IndexReader#isCurrent() return false.
Now the sample runs well, but I saw almost other samples would close the
IndexSearcher ins
