Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Sat, 14 Apr 2012 14:53:17 +0000 (UTC)
From: "Koji Sekiguchi (Issue Comment Edited) (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1493141584.25623.1334415197275.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1904536258.12414.1334153118636.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (LUCENE-3971) MappingCharFilter
 rarely has wrong correctOffset (for finalOffset)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LUCENE-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254129#comment-13254129 ] 

Koji Sekiguchi edited comment on LUCENE-3971 at 4/14/12 2:52 PM:
-----------------------------------------------------------------

bq. Thanks again for taking care of this: I think this could be a good candidate for 3.6.1? 

+1
                
      was (Author: koji):
    bq. Thanks again for taking care of this: I think this could be a good candidate for 3.6.1? 
                  
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org