lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Salem" <>
Subject Re: ComplexPhraseQueryParser with multiple fields
Date Tue, 03 May 2011 13:19:25 GMT
That seems to work.  Thank you!
Chris Salem 
Development Team 
Main Sequence Technologies, Inc. - PCRecruiter Support
P: 440.946.5214 ext 5458 
F: 440.856.0312

This email and any files transmitted with it may contain confidential information intended
solely for the use of the individual or entity to whom they are addressed. If you have received
this email in error please notify the sender. Please note that any views or opinions presented
in this email are solely those of the author and do not necessarily represent those of the
company. Finally, the recipient should check this email and any attachments for the presence
of viruses. The company accepts no liability for any damage caused by any virus transmitted
by this email. Main Sequence Technologies, Inc. 4420 Sherwin Rd. Willoughby OH 44094

----- Original Message ----- 
To: "" <>, Chris Salem <>
From: Ahmet Arslan <>
Sent: 5/2/2011 6:42:37 AM
Subject: Re: ComplexPhraseQueryParser with multiple fields

I've just started using the ComplexPhraseQueryParser and it works great with one field but
is there a way for it to work with multiple fields?  For example, right now the query:
job_title: "sales man*" AND NOT contact_name: "Chris Salem"
throws this exception 
Caused by: org.apache.lucene.queryParser.ParseException: Cannot have clause for field "job_title"
nested in phrase for field "contact_name"
What is the best way to work around this?

There is "Lucene-1486 non default field.patch" for that but it requires :

"Fixing this would require changing the package name of 
ComplexPhraseQueryParser or changing the visibility of "field" in the 
QueryParser base class to "protected".
Anyone have any strong feelings about which of these is the most acceptable?"

To unsubscribe, e-mail:
For additional commands, e-mail:

(The following links were included with this email:)

(The following links were included with this email:)

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message