p and the suggestions.
Polina
-Original Message-
From: Morus Walter [mailto:[EMAIL PROTECTED]
Sent: September 17, 2004 2:31 AM
To: Lucene Users List
Subject: RE: QueryParser.parse() and Lucene1.4.1
Polina Litvak writes:
> Hi Daniel,
>
> I just downloaded the latest version of Lucene and
004 5:07 PM
To: Lucene Users List
Subject: Re: QueryParser.parse() and Lucene1.4.1
On Wednesday 15 September 2004 21:58, Polina Litvak wrote:
> Does anyone know how to work around this new feature ?
I can't remember any changes in this area, but I just tried with the
current version from CVS and t
I have a question regarding QueryParser and lucene-1.4.1.jar:
When using lucene-1.3-final.jar, a query of the form: Field:(A AND -(B))
was parsed into +Field:A -Field:B (using QueryParser.parse()).
After making the switch to lucene-1.4.1.jar, the same query is being
parsed into Field:A Field:- F
);
query = QueryParser.parse(searchQuery,"contents",analyzer);
-Original Message-
From: Polina Litvak [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 08, 2004 10:19 AM
To: 'Lucene Users List'
Subject: RE: Problem with match on a non tokenized field.
Thanks a lot for your
I tried to create my own analyzer so it returns fields as they are
(without any tokenizing done), using code posted on lucene-user a short
while a go:
private static class NullAnalyzer
extends Analyzer
{
public TokenStream tokenStream(String fieldName, Reader reader)
{
"contents",
analyzer);
-Original Message-
From: Polina Litvak [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 07, 2004 4:20 PM
To: [EMAIL PROTECTED]
Subject: Problem with match on a non tokenized field.
I have a Lucene Document with a field named Code which is stored
and index
I have a Lucene Document with a field named Code which is stored
and indexed but not tokenized. The value of the field is ABC5-LB.
The only way I can match the field when searching is by entering
Code:"ABC5-LB" because when I drop the quotes, every Analyzer I've tried
using breaks my
query into C
I was trying to search my index for a term of the form a*-b* (e.g.
ABC-DEFG). While tracing the code I noticed that Lucene breaks this term
into two terms, "ABC" and "DEFG". To prevent this, I tried escaping the
special character "-" with "\" to form the term "ABC\-DEFG" and now
Lucene search can't
;t work a lot on
it and it'll be better to write it on your own to have something clean.
Franck
Polina Litvak wrote:
> Since it is not allowed to use "*" or "?" symbols as the first
character
> of a search, I tried the following query as an alternative:
> &
Since it is not allowed to use "*" or "?" symbols as the first character
of a search, I tried the following query as an alternative:
"Field_1: ([a* TO z*] OR [A* TO Z*] OR [0* TO 9*])"
but the QueryParser complains saying:
"org.apache.lucene.search.BooleanQuery$TooManyClauses".
Any idea why this
10 matches
Mail list logo
