(Please note that ThreadedIndexWriter is source code available with
the upcoming revision to Lucene in Action.)
Phil, is it possible you are using an older version of the book's
source code? In particular, can you check whether your version of
ThreadedIndexWriter.java has this:
public void clo
http://code.google.com/p/bobo-browse
looks like it may be the ticket.
Marc
--
View this message in context:
http://www.nabble.com/Group-by-in-Lucene---tp13581760p24767693.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
Hi Mike,
It's Jibo, not me, having the problem. But thanks for the link. I was
interested to look at the code. Will be buying the book soon.
Phil
On Sat, Aug 1, 2009 at 2:08 AM, Michael McCandless
wrote:
>
> (Please note that ThreadedIndexWriter is source code available with
> the upcoming revi
I guess in that case, my users will be angry :)
the fact is, plural (as an example) is not supported, and that is one of
the most common things that a person doing some search will expect to
not have to worry about.
anyway, will roll it out and see the users' reaction :)
thank you.
-walid
On Fr
Hi,
I'm starting to work on an app to list all of the terms in the "path" field.
I'm including the beginning of my code below.
When I run this, pointing it to a directory named "index" containing the Lucene
indexes, I am getting a java.io.IOException.
Here's the output when I run:
Index in d
Hi Jim,
I cannot see anything obvious, but both open() and terms() throw
IOException's. You could try putting these in separate try..catch
blocks to see which one it's coming from. Or using e.printStackTrace()
in the catch block will give more info to help you debug what's
happening.
On Sat, Aug
Phil,
Yes, that exception is not very helpful :)!!
I'll try your suggestions and post back.
Thanks,
Jim
Phil Whelan wrote:
> Hi Jim,
>
> I cannot see anything obvious, but both open() and terms() throw
> IOException's. You could try putting these in separate try..catch
> blocks to see
Phil,
I posted in haste. Actually, from the output that I posted, doesn't it it look
like the .next() itself is throwing the exception?
That is what has been puzzling me. It looks like it got through the open() and
terms() with no problem, then it blew up when calling the next()?
Jim
Hi,
BTW, the next() method is an abstract method in the Javadocs. Does that mean
that I'm suppose to have my own implementation?
Jim
oh...@cox.net wrote:
> Phil,
>
> I posted in haste. Actually, from the output that I posted, doesn't it it
> look like the .next() itself is throwing t
Hi,
I changed the beginning of the try to:
try {
System.out.println("About to call .next()...");
boolean foo = termsEnumerator.next();
System.out.println("Finished calling first .next()");
Hi,
I don't know what happened, but all of a sudden, it started working :(...
Jim
oh...@cox.net wrote:
> Hi,
>
> I changed the beginning of the try to:
>
> try {
> System.out.println("About to call .next()...");
> boolean foo = t
11 matches
Mail list logo
