lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4240) Analyzer.getOffsetGap Improvements
Date Fri, 20 Jul 2012 14:51:34 GMT


Robert Muir updated LUCENE-4240:

    Attachment: LUCENE-4240.patch

initial patch
> Analyzer.getOffsetGap Improvements
> ----------------------------------
>                 Key: LUCENE-4240
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>         Attachments: LUCENE-4240.patch
> From LUCENE-3151 (Robert Muir's comments): there is no need for the Analyzer to take
in an IndexableField object.  We can simplify this API:
> {quote}
> Hey Grant: I know it sounds silly but can we split out the getOffsetGap API change into
a separate issue?
> This would be nice to fix ASAP.
> I dont understand why it takes IndexableField or took Fieldable. All the other methods
here like
> getPositionIncrementGap take "String fieldName". I think this one should too.
> I dont think it needs a boolean for tokenized either: returning a 0 for NOT_ANALYZED
> If you choose NOT_ANALYZED, that should mean the Analyzer is not invoked!
> If you want to do expert stuff control the offset gaps between values for NOT_ANALYZED
> then just analyze it instead, with keyword tokenizer!
> {quote}

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