Hello, I tried finding information about this from past mailing list
emails, but couldn't find anything. I'm using Lucene 1.4 series and
wondered if it is safe for two different JVMs opening and searching the
same physical index located on the local file system, with one of the JVMs
performing writ
java-user/200504.mbox/%3
> [EMAIL PROTECTED]
>
> - Monsur
>
>
>
>> -Original Message-
>> From: Matt Magoffin [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, November 17, 2005 11:05 PM
>> To: java-user@lucene.apache.org
>> Subject: Re: Reference
I've been watching our servers today, and now there are 2500 "deleted"
file handles open like this. Seems to be quite large. Still don't know why
there are so many. I'm using the compound index format already to reduce
the number of open files.
-- m@
> Hello, I use Lucene in a long-running server
Hello, I use Lucene in a long-running server application on a Linux
server, and the other day I got the "Too many open files" exception. I've
increased the number of allowed file handles, but was checking out the
open file handles using "lsof", and see about 300 files listed like the
following:
ja
> : I'm wondering if there a more efficient way to accomplish this?
>
> I believe there is -- provided the terms are index.
>
> 1) Get yourself a BitSet representing the Documents you are interested in
> (you mentioned having a a date range, you can either use a RangeFilter nad
> call the bits meth
I've used the example posted at
http://wiki.apache.org/jakarta-lucene/LuceneFAQ#head-a801793d7479264e29157d92440199b35266dc18
to find all terms used in a complete index, but was wondering if there is
an efficient way to find all terms used within only a set of Documents
matching a query?
For examp
I'm having a problem getting the QueryParser to correctly parse a string
like the following:
addr:"Foo \"Bar\" Street"
Should this work, or is there some other way to escape double quotes
within a quoted query term? Here is a unit test that shows the problem:
import junit.framework.TestCase;
im
gt; email?
>
> : Date: Fri, 12 Aug 2005 12:09:55 -0700 (PDT)
> : From: Matt Magoffin <[EMAIL PROTECTED]>
> : Reply-To: java-user@lucene.apache.org
> : To: java-user@lucene.apache.org
> : Subject: Re: QueryParser exception on escaped backslash preceding )
> :charact
Sure, here's a test case with the bug and the workaround.
-- m@
> can you provide a JUnit test that genertes the exception ... if it's
> coming from the parse call it should only require a 1 line test.
>
> : Date: Fri, 12 Aug 2005 10:29:41 -0700 (PDT)
> : From: Matt M
> the paren grouping.
>
> how are you passing that string to the QP, is it embedded in your java
> code? if so the java compiler is interpreting your \\ and your java app
> is never seeing it.
>
> : Date: Fri, 12 Aug 2005 07:30:19 -0700 (PDT)
> : From: Matt Magoffi
When I try to parse a query with an escaped backslash character like this
(using Lucene 1.4.3):
-id:20677 +(addr:Street143 AND zip:\\)
the QueryParser thows an Exception:
Encountered "" at line 1, column 289.
Was expecting one of: ... ...
... "+
In Re: to a post from 24-Mar-2005 by Matt Quail, in reference ... I'm
seeing this same exception (Windows, Lucene 1.4.3, Sun JDK 1.5.0_03) that
occurs repeatedly for me, but only during the course of running all my
application's unit tests in Ant. When I run the individual unit test I
can't get the
I ran into the following exception during an index update process (1.4.3
on Windows)... and was wondering if any one had an idea what might cause
this. It occured after a new IndexWriter was opened, a document added, and
then IndexWriter.close() was called. This occurs after many successful
updates
> It took some sleep to realize this:
> This exception can happen when a scorer is add()'ed to the BooleanScorer
> after
> the query search has begun. Given that it is difficult to reproduce, the
> odds
> are that there two threads not properly synchronized: one add()ing
> to the BooleanScorer and
I'm getting a strange exception with Lucene 1.4.3 that occurs when I run a
unit test from Ant, but not when I run the same unit test inside Eclipse.
The exception is
Caused by: java.io.IOException: Cannot delete _5.cfs
at org.apache.lucene.store.FSDirectory.renameFile(FSDirectory.java:232)
at or
Here is a sample query that produces the error:
+dcode:123182 +cdate:[20050501 TO 20050531] +((+gn:m +sn:malen)
phone:3458345730 addr:345 hiller (+sn:malen +zip:34535))
I'll see about getting a test case, but like I said it doesn't happen
every time so I've had a hard time tracking down the probl
The exception does come on the heels of an update to the index by a
different thread than the one the search runs in. These log statements
show the operations going on just prior to the exception:
May-05 12:36:05 DEBUG - Indexing Lead 1024
May-05 12:36:06 TRACE - CON Closing IndexWriter
[EMAIL PRO
Hello, I'm having a tough time trying to get to the root of an exception I
see sometimes on my Lucene 1.4.3 index. The exception is:
java.lang.ArrayIndexOutOfBoundsException: 4
at org.apache.lucene.search.BooleanScorer.score(BooleanScorer.java:126)
at org.apache.lucene.search.Scorer.score(Scorer
18 matches
Mail list logo