If wildcards and fuzzyies are supported, why not range ?
We have a custom "range in phrase" parser, and it works really well,
but we would like to use standard Lucene is possible.
On Dec 10, 2008, at 12:18 PM, Mark Harwood (JIRA) wrote:
Wildcards, ORs etc inside Phrase queries
----------------------------------------
Key: LUCENE-1486
URL: https://issues.apache.org/jira/browse/
LUCENE-1486
Project: Lucene - Java
Issue Type: Improvement
Components: QueryParser
Affects Versions: 2.4
Reporter: Mark Harwood
Priority: Minor
Fix For: 2.4.1
An extension to the default QueryParser that overrides the parsing
of PhraseQueries to allow more complex syntax e.g. wildcards in
phrase queries.
The implementation feels a little hacky - this is arguably better
handled in QueryParser itself. This works as a proof of concept
for much of the query parser syntax. Examples from the Junit test
include:
checkMatches("\"j* smyth~\"", "1,2"); //wildcards and fuzzies
are OK in phrases
checkMatches("\"(jo* -john) smith\"", "2"); // boolean logic
works
checkMatches("\"jo* smith\"~2", "1,2,3"); // position logic
works.
checkBadQuery("\"jo* id:1 smith\""); //mixing fields in a phrase
is bad
checkBadQuery("\"jo* \"smith\" \""); //phrases inside phrases
is bad
checkBadQuery("\"jo* [sma TO smZ]\" \""); //range queries inside
phrases not supported
Code plus Junit test to follow...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
