Hello,
I'll put my comments inline...
--- petite_abeille <[EMAIL PROTECTED]> wrote:
> Hello again,
>
> attached is the source code of the only class interacting directly
> with
> Lucene in my app. Sorry for not providing a complete test case as
> it's
> hard for me to come up with something s
> > I would add some logging to the code
>
> You lost me here... Where should I add some logging?
At the top of every method, or next to every lucene
call, or wherever anything interesting happens.
System.out.println("Calling search()");
or use log4j or whatever you prefer.
> > to get more
Hi petite,
I will try to be brief...
In lucene the number of files created depends on the number of
fields the document has
so lets take an example you want to index 100 files
if each file contains 10 fields
document.add(Field.Text(UNIQUE_ID, "1234
> I would add some logging to the code
You lost me here... Where should I add some logging?
> to get more idea of which Lucene methods are
> actually being called, when, in what sequence.
I typical sequence looks like that:
- search()
- deleteIndexWithID()
- indexValuesWithID()
PA
--
To u
Hello
I can't spot anything but I'm definitely not the
world's greatest Lucene expert and maybe someone
else will. Perhaps the stack trace will help
too. Failing that, and if you still can't come
up with a complete self-contained test case to
show the problem, I would add some logging to the
c
Hello again,
attached is the source code of the only class interacting directly with
Lucene in my app. Sorry for not providing a complete test case as it's
hard for me to come up with something self contained. Maybe there is
something that's obviously wrong in what I'm doing.
Thanks for any h
