: initialized... I tried to create a seacher everytime but that lead me to
: the Too-Many-Files-Open exception. So no matter what I do I face a show
: stopper.
were you closing the old searcher before opening the new one?
even if that was the cause of your problem, i still wouldn't recomend
reop
My two cents:
Lucene often offers the least common denominator...for example: out of
the box, Lucene best handles either a single user / single thread
experience or a mostly 'read only' experience. I believe that the main
reason for this is that it serves the greatest variety uses. You can,
a
I agree those are benefits when you batch process the indexes once or once in a
while.
The beauty of AOP is that I can intercept writes and do change the index on the
spot. At that point I'd need to let the search know or drop it. If I do that
that will face issues on the search side since this
Indeed, having to re-open a searcher/reader in order for searches
to reflect index modification, can sometimes not best fit with the
logic of a certain application.
But see the features made possible with this design:
(+) searches do not feel index modifications until desired.
(++) no need to sync
That part is self understood. However as I describe the problem initially - and
the use case is a very practical way of dealing with documents in real live -
they change, we edit them, I don't want to run a batch re-indexing thing every
night... I just wanted done on the spot. One instance Index
<1>. Every time you close/open a reader, you pay a significant penalty
to warm up caches, etc. You may have to do some tricky dancing
to coordinate among the sessions to be able to close/reopen
the reader to allow updates to show up though.
Erick
On 3/5/07, Mohammad Norouzi <[EMAIL PROTECTED]>
Hi Erick
I am completely confused about this IndexReader.
in my case, I have to keep the reader opened because of pagination of the
result so I have to had a reader per session. the thing that baffled me is
can only one reader service all the session at the same time?
I mean
1- having one reader
There was quite a long discussion thread on this topic relatively
recently, try searching the archive for concurrence, perhaps
IndexReader, etc.
The short take-away is that you should share a single instance
of the reader, since opening one is an expensive operation, and
the first searches you pe
Daniel,
Thanks for replying. THe only reason I don't close my indexSearcher is
that I got the "Too Many File Open Exception" and I decided to make my
searcher static in the SearchService.
If I do go and close then open a new one I may expose myself to some
concurent access issues while people can
MC Moisei wrote:
Hi to all members of the user group!
Let me get to my problem. I use Lucene in two different parts of the
application. One is the SearchService and one is an AOP interceptor that
intercepts any changes in the Searcheable entities. This last part is
removing the document from the
10 matches
Mail list logo
