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=4102>.
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=4102
Prefix Queries cannot be case insensitible
Summary: Prefix Queries cannot be case insensitible
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: andrzej.jarmoniuk@e-point.pl
Hi. I am using a cvs version of Lucene (got on 2001.10.11).
I am having the following problem: while I can achieve case insensibility of the
search engine by using the correct tokenizer (a derivative of
LowerCaseTokenizer, which passes alphanumeric characters instead of letters only
as token components), I cannot have this feature work with prefix queries.
As I am currently working on the problem myself, I can submit a solution fixing
this bug in some future.
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4102>.
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=4102
Prefix Queries cannot be case insensitible
Summary: Prefix Queries cannot be case insensitible
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: andrzej.jarmoniuk@e-point.pl
Hi. I am using a cvs version of Lucene (got on 2001.10.11).
I am having the following problem: while I can achieve case insensibility of the
search engine by using the correct tokenizer (a derivative of
LowerCaseTokenizer, which passes alphanumeric characters instead of letters only
as token components), I cannot have this feature work with prefix queries.
As I am currently working on the problem myself, I can submit a solution fixing
this bug in some future.