> On Friday 26 October 2007 09:36:58 Ard Schrijvers wrote:
> > Hello,
> >
> > I am seeing that a query with boolean queries in boolean
> queries takes
> > much longer than just a single boolean query when the
> number of hits
> > if fairly large. For example
> >
> > +prop1:a +prop2:b +prop3:c
I'm trying to use the class
org.apache.lucene.analysis.ngram.EdgeNGramTokenizer.
I 'm using lucene 2.2.0 and I included i my classpath lucene-core-2.2.0.jar.
I have:
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
When I try to compile my code I'm getting:
package org.apache.l
On Tuesday 30 October 2007 11:57, Marco wrote:
> I'm trying to use the class
> org.apache.lucene.analysis.ngram.EdgeNGramTokenizer.
> I 'm using lucene 2.2.0 and I included i my classpath
> lucene-core-2.2.0.jar. I have:
That class is in contrib/analyzers/lucene-analyzers-2.2.0.jar
Regards
Dani
And where can I download it?
Regards
Marco
Daniel Naber ha scritto:
On Tuesday 30 October 2007 11:57, Marco wrote:
I'm trying to use the class
org.apache.lucene.analysis.ngram.EdgeNGramTokenizer.
I 'm using lucene 2.2.0 and I included i my classpath
lucene-core-2.2.0.jar. I have:
Tha
Sorry.
I found it
Bye
Marco ha scritto:
And where can I download it?
Regards
Marco
Daniel Naber ha scritto:
On Tuesday 30 October 2007 11:57, Marco wrote:
I'm trying to use the class
org.apache.lucene.analysis.ngram.EdgeNGramTokenizer.
I 'm using lucene 2.2.0 and I included i my clas
So I should create a singe IndexWriter but allow multiple threads to
use it?
On Oct 30, 2007, at 12:49 AM, Karl Wettin wrote:
30 okt 2007 kl. 05.08 skrev Michael Prichard:
If I multithread an indexing process can two or more processes
write to the same index?
Multiple threads can add d
You can use a queue to let IndexWriter do its work asychronize
-Original Message-
From: Michael Prichard [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 30, 2007 9:10 PM
To: java-user@lucene.apache.org
Subject: Re: Threading Indexing Processes : Can we write concurrently to
Index?
So I
Tobias Hill wrote:
I want to match on the exact phrase "foo bar dot" on a
specific field on my set of documents.
I only want results where that field has exactly "foo bar dot"
and no more terms. I.e. A document with "foo bar dot alu"
should not match.
A phrase query with slop 0 seems resonable
30 okt 2007 kl. 16.58 skrev Tobias Hill:
I only want results where that field has exactly "foo bar dot"
and no more terms. I.e. A document with "foo bar dot alu"
should not match.
A phrase query with slop 0 seems resonable but how do I
express "but nothing more than these terms".
There is n
On Tuesday 30 October 2007 16:58:09 Tobias Hill wrote:
> I want to match on the exact phrase "foo bar dot" on a
> specific field on my set of documents.
>
> I only want results where that field has exactly "foo bar dot"
> and no more terms. I.e. A document with "foo bar dot alu"
> should not match.
Hi all,
I'm following the suggestion of this forum on how create a suggestion
service like google suggest.
I'm parsing a words/rank file with my words.
For each word, I'm adding a document with content and rank in in index:
then I create a EdgeNGramTokenizer of the word. This gives me N words
It seems that the problem is when I add the token created by
EdgeNGramTokenizer in in the index.
If the token contains a space (for example apple com) I have to add to
the index with Field.Index.TOKENIZED otherwise the search cannot find it.
If there is no space there is no problem even if I use
Hi all the following is using Lucene 2.2.0.
I've been trying to alter the scoring of my search results to boost by
date. My idea was to boost documents while indexing using the date but
it doesn't work. So I put together this little sample piece of code to
investigate further and apparently set
Bruno Dery wrote:
Hi all the following is using Lucene 2.2.0.
I've been trying to alter the scoring of my search results to boost by
date. My idea was to boost documents while indexing using the date but
it doesn't work. So I put together this little sample piece of code to
investigate furthe
Bruno Dery wrote:
Hi all the following is using Lucene 2.2.0.
I've been trying to alter the scoring of my search results to boost by
date. My idea was to boost documents while indexing using the date but
it doesn't work. So I put together this little sample piece of code to
investigate furthe
Thanks for the help, you're right your example works. However looking in
Luke I also see only ones (1 1 1) as the document boost.
I imagine Luke use's Lucene's Document.getBoost() function. Shouldn't
this be considered a bug, as I'd expect to retrieve the same boost
number (or at least some facto
16 matches
Mail list logo
