lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Updated) (JIRA)" <>
Subject [jira] [Updated] (LUCENE-3765) trappy ignoreCase behavior with StopFilter/ignoreCase
Date Thu, 09 Feb 2012 16:21:59 GMT


Robert Muir updated LUCENE-3765:

    Attachment: LUCENE-3765.patch

Updated patch for trunk.

I found two traps/bugs and fixed them here as well (these will go in the backport too along
with the StopFilter deprecations):
* DutchAnalyzer confusingly only used its default 'stem dictionary' (e.g. kind/kinder, fiets)
for the no-arg ctor, for other ctors, it would remain empty. This means stemming would be
different if you passed an empty stopset. 
* Standard/ClassicAnalyzer had a ctor that takes File, i think we should deprecate this one,
for the one that takes Reader.

> trappy ignoreCase behavior with StopFilter/ignoreCase
> -----------------------------------------------------
>                 Key: LUCENE-3765
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: modules/analysis
>            Reporter: Robert Muir
>             Fix For: 3.6, 4.0
>         Attachments: LUCENE-3765.patch, LUCENE-3765.patch
> Spinoff from LUCENE-3751:
> {code}
> * If <code>stopWords</code> is an instance of {@link CharArraySet} (true
> * <code>makeStopSet()</code> was used to construct the set) it will be
> * directly used and <code>ignoreCase</code> will be ignored since
> * <code>CharArraySet</code> directly controls case sensitivity.
> {code}
> This is really confusing and trappy... we need to change something here.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message