[ http://issues.apache.org/jira/browse/LUCENE-372?page=all ]
Steven Parkes updated LUCENE-372:
---------------------------------
Lucene Fields: [Patch Available]
Bugzilla Id: (was: 34447)
Fix Version/s: 2.1
Affects Version/s: 2.0.0
1.9
2.0.1
2.1
Assignee: (was: Lucene Developers)
Priority: Minor (was: Major)
I like it. There are some extra tests that demonstrate where parse exceptions
are going to be thrown, which is nice.
It would be nice if we could, perhaps, be more liberal in what we accept. For
example, I've always thought it would be nice if we could add in missing
terminators, e.g., quotes, parentheses., in the spirit of "being liberal in
what you accept." But I don't see that being too feasible with an automatically
generated parser.
I do think completely ignoring terms, which this patch fixes, is the wrong way
to be liberal.
> Unmatched right parentheses truncates query
> -------------------------------------------
>
> Key: LUCENE-372
> URL: http://issues.apache.org/jira/browse/LUCENE-372
> Project: Lucene - Java
> Issue Type: Bug
> Components: QueryParser
> Affects Versions: 1.4, 2.0.0, 1.9, 2.0.1, 2.1
> Environment: Operating System: Linux
> Platform: PC
> Reporter: Patrick Hochstenbach
> Priority: Minor
> Fix For: 2.1
>
> Attachments: Lucene-372.patch, LUCENE-372.patch.txt
>
>
> The query processor truncates a query when right parentheses are unmatched.
> E.g.:
> secret AND illegal) AND access:confidential
> will not result in a ParseException instead will run as:
> secret AND illegal
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
