2008/9/6 叶双明 <[EMAIL PROTECTED]>
> In my opinion, you can use MultiSearcher, or if there isn't huge data
> in index, you can put them in one index, no matter the fields in
> indices are not the same. You can get Docoument match your query, but
> I think, you will think about the query that you wan
Unless my understanding is wrong, there is a memory leak for Lucene search
from Lucene-1195.(svn r659602, May23,2008)
This patch brings in a ThreadLocal cache to TermInfosReader.
It's usually recommended to keep the reader open, and reuse it when
possible. In a common J2EE application, the http r
Have you ignore any Exception during query? make sure of it.
2008/9/5, Erick Erickson <[EMAIL PROTECTED]>:
>
> I've been tracking this list for a year or more, and this is the
> first I've ever heard of such a thing. Which leads me to wonder
> what *else* changed besides your index size. Classpa
The main reason behind having one index per table is that the tables
grow to be very big and we want to keep updating the index as the
table gets modified (may be at specified intervals). So, if table A
changes (row modified, added or deleted) we want this change to be
reflected in the index and we
Well, what is the higher-level task you're trying to accomplish? I have
real trouble understanding why you're using Lucene at all. Especially
because scoring will be irrelevant *between* searches, since they're
going at completely different "documents". That is, there is no relation
between the sco
In my opinion, you can use MultiSearcher, or if there isn't huge data
in index, you can put them in one index, no matter the fields in
indices are not the same. You can get Docoument match your query, but
I think, you will think about the query that you want to put into the
IndexSearcher.
2008/9/6
Sounds good. If other people find it useful, I'm all for it. I just didn't
want to burden you guys to change the index format only for my use-case :-)
On Sat, Sep 6, 2008 at 3:44 PM, Michael McCandless <
[EMAIL PROTECTED]> wrote:
>
> I think this may also be useful for a reader to have richer log
I think this may also be useful for a reader to have richer logic as
to whether it's time to reopen. It's a way for the writer to do some
minimal communication to the readers on what changes were just
committed.
Ie we have the static IndexReader.getVersion method, that opens the
latest
Hello,
I am a newbie user of Lucene Java. I am trying to use Lucene to enable in
search in my application. I am stuck a little in actual Search. I'm facing a
design issue and want help from experts here.
Here is my scenario:
* I have 7-8 tables in the database and I create a separate index for ea
Hello,
I am a newbie user of Lucene Java. I am trying to use Lucene to enable in
search in my application. I am stuck a little in actual Search. I'm facing a
design issue and want help from experts here.
Here is my scenario:
* I have 7-8 tables in the database and I create a separate index for ea
10 matches
Mail list logo
