You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by bu...@apache.org on 2003/04/09 12:26:18 UTC
DO NOT REPLY [Bug 18847] New: -
Parser bug when dealing with new lines.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18847>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18847
Parser bug when dealing with new lines.
Summary: Parser bug when dealing with new lines.
Product: Lucene
Version: CVS Nightly - Specify date in submission
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: QueryParser
AssignedTo: lucene-dev@jakarta.apache.org
ReportedBy: konrad@xtramind.com
Hi,
there seems to be a bug in the Lucene parser in the
treatment of spaces and newlines.
When we search for:
weltbank && identifier: weltbank
over a certain collection of texts, we get 82 hits.
If we write this as:
weltbank &&
identifier: weltbank
with no space after the &&, there still are 82 results. But
the same query with a space or tab after the && and before the newline
gives back 0 results!
Even worse, the same query with a space before the "identifier:", but
not after the &&:
weltbank &&
identifier: weltbank
gives 106 hits, i.e., the same as
weltbank || identifier: weltbank
Arrrgh!
There is a simple workaround - flattening the query string -
but this is probably only a problem of newlines not being treated
similar to whitespace in the parser code.
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org