[
https://issues.apache.org/jira/browse/LUCENE-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254166#comment-13254166
]
Dawid Weiss commented on LUCENE-3971:
-------------------------------------
bq. This code is one hairy bastard
Btw, nothing personal, Koji. It's just me being slow on understanding how those
indexes are calculated.
> MappingCharFilter rarely has wrong correctOffset (for finalOffset)
> -------------------------------------------------------------------
>
> Key: LUCENE-3971
> URL: https://issues.apache.org/jira/browse/LUCENE-3971
> Project: Lucene - Java
> Issue Type: Bug
> Components: modules/analysis
> Reporter: Robert Muir
> Assignee: Dawid Weiss
> Fix For: 4.0
>
> Attachments: LUCENE-3971.patch, LUCENE-3971_test.patch
>
>
> Found this bug over on LUCENE-3969, but I'm currently tracking a ton of bugs,
> so
> I figure I would open an issue and see if this one is obvious to anyone:
> Consider this input string: "gzw f quaxot" (length = 12) with a
> WhitespaceTokenizer.
> If i have mapping rules like this, then it works!:
> {noformat}
> "t" => ""
> {noformat}
> But if I have mapping rules like this:
> {noformat}
> "t" => ""
> "tmakdbl" => "c"
> {noformat}
> Then it will compute final offset wrong:
> {noformat}
> [junit] junit.framework.AssertionFailedError: finalOffset expected:<12>
> but was:<11>
> {noformat}
> Looks like some logic/recursion bug in the correctOffset method? The second
> rule is not even "used" for this string,
> it just happens to also start with 't'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
