Uwe
Thank you very much for your prompt responses. Yes, the old JRockit JVM version
is the likely culprit. Initial testing with -XNoOpt has not yet produced the
failure, although it is too early to be certain this fixes it.
I am very interested in attending your talk on testing Lucene/Solr with
Hi,
JRockit is unfortunately very buggy with Lucene, especially this very old
version (1.6.0_03 is more than antique). The current one is
jrockit-jdk1.6.0_45-R28.2.7-4.1.0. Unfortunately the later version still have
bugs, that may also lead to corrupt indexes. Because of this we are running
ni
complete java version info:
java version "1.6.0_03"Java(TM) SE Runtime Environment (build 1.6.0_03-b05)BEA
JRockit(R) (build
R27.5.0-110_o_CR366951-99572-1.6.0_03-20080529-1718-linux-x86_64, compiled mode)
> From: u...@thetaphi.de
> To: java-user@lucene.apache.org
> Subject: RE: intermittent NPE
jrockit-jre1.6.0_03-Xms3000M-Xmx3000M-Djava.awt.fonts=$fontsdir
range query: timefield:[1366740416 TO 1366826816}
We index and search the date-time field as long values. We do plan on someday
updating to a recent Sun JRE, but we have to get around to solving some
server-agent NIO API conflicts fi
Hi,
This looks crazy! What Java version from which JVM vendor are you using? What
are your JVM settings and how does the range query look like?
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Lynn
Hello,
Using Lucene 4.1.0, my application is designed to automatically run the exact
same facet search every few minutes, varying only by range on a date-time
field. However, occasionally the app fails with the below exception. Once this
occurs, all Lucene searches begin to fail - even if the pr
On Tue, Apr 30, 2013 at 7:57 PM, Beale, Jim (US-KOP) wrote:
> We've just upgraded to 4.2 from 3.6 and suffered some performance degradation
> in both indexing and retrieval. We've had to eliminate compression, even
> supplying our own NoCompression codec since there doesn't appear to be any
>
Hi
I don't think it's possible, not with the default configuration. The
problem is that drill-down terms are created with a default delimiter,
which is \u001F, and you can't really type that character.
One way is to override FacetIndexingParams.getFacetDelimChar() to return a
human readable chara
Hi all,
I think somebody already did this question in the mailing list, but I
can't find it.
Is possible to execute a search with facets in luke? then use the
$facets field in searches?
Nicola.
-
To unsubscribe, e-mail: java-
Hi Ivan,
i was aware of that thread i also asked to learn about overriding
DefaultSimilarity stuff or similar other approach.
Thanks.
On 30/04/2013 17:24, Ivan Brusic wrote:
There was a similar question asked a couple of months ago, with a great
answer by Uwe Schindler:
http://search-lucene.c
10 matches
Mail list logo
