lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <>
Subject [jira] [Resolved] (LUCENE-2644) LowerCaseTokenizer Does Not Behave As One Might Expect (or Desire)--Given Its Name
Date Tue, 18 Sep 2012 17:48:08 GMT


Steven Rowe resolved LUCENE-2644.

       Resolution: Won't Fix
    Fix Version/s:     (was: 4.1)

Scott, I agree with [~rcmuir] - LowerCaseTokenizer has been around since at least 2001 (when
Lucene came to the ASF) with well-defined behavior.

I think the way forward here is to make a new issue that creates a new tokenizer performing
the things you want to see, with a new name.

Resolving as Won't Fix.
> LowerCaseTokenizer Does Not Behave As One Might Expect (or Desire)--Given Its Name
> ----------------------------------------------------------------------------------
>                 Key: LUCENE-2644
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Wish
>          Components: modules/analysis
>    Affects Versions: 3.0.2
>            Reporter: Scott Gonyea
>         Attachments: LowerCaseTokenizer.patch
> While I understand some of the reasons for its design, the original LowerCaseTokenizer
should have been named LowerCaseLetterTokenizer.
> I feel that LowerCaseTokenizer makes too many assumptions about what too tokenize, and
I have therefore patched it.  The *default* behavior will remain as it always has--to avoid
breaking any implementations for which it's being used.
> I have changed LowerCaseTokenizer to extend CharTokenizer (rather than LetterTokenizer).
 LetterTokenizer's functionality was merged into the default behavior of LowerCaseTokenizer.
> Getter/Setter methods have been added to the LowerCaseTokenizer Class, allowing you to
turn on / off tokenizing by white space, numbers, and special (Non-Alpha/Numeric) characters.

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

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

View raw message