lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3792) Remove StringField
Date Thu, 16 Feb 2012 20:20:59 GMT


Robert Muir commented on LUCENE-3792:

Hossman I think KEYWORD_ANALYZED is the ideal name for 3.x actually. I think in combination
with the javadocs it would be more clear.

This still leaves the question for trunk (currently StringField):
positives are that its actually a "nice" name, concise and to the point.
another positive is that StringField omits things like positions, and in trunk we don't silently
fail if you form a phrase from this.

one negative is that both StringField and TextField confusingly take String in their ctors,
(I've chosen the wrong one myself before on accident).

Basically to me, this is a combination of traps. Trunk is somewhat better because it throws
exceptions for positional queries if
you actually excluded positions...

in all cases in 3.x, the wrong 'configuration' here creates a situation where the user just
'does not get results' and they have
no idea why... despite the fact they used the same Analyzer at query-time and index-time like
a good user. thats what I find so frustrating.
> Remove StringField
> ------------------
>                 Key: LUCENE-3792
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Task
>    Affects Versions: 4.0
>            Reporter: Robert Muir
>             Fix For: 4.0
>         Attachments: LUCENE-3792_javadocs_3x.patch, LUCENE-3792_javadocs_3x.patch
> Often on the mailing list there is confusion about NOT_ANALYZED.
> Besides being useless (Just use KeywordAnalyzer instead), people trip up on this
> not being consistent at query time (you really need to configure KeywordAnalyzer for
the field 
> on your PerFieldAnalyzerWrapper so it will do the same thing at query time... oh wait
> once you've done that, you dont need NOT_ANALYZED).
> So I think StringField is a trap too for the same reasons, just under a 
> different name, lets remove it.

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