Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Fri, 20 Oct 2017 16:05:00 +0000 (UTC)
From: "Pascal Schumacher (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.13109729.1508166960000.19104.1508515500783@Atlassian.JIRA>
In-Reply-To: <JIRA.13109729.1508166960000@Atlassian.JIRA>
References: <JIRA.13109729.1508166960000@Atlassian.JIRA> <JIRA.13109729.1508166960962@jira-lw-us.apache.org>
Subject: [jira] [Commented] (TEXT-103) Add provision to change the cost for
 insert, delete and replace operation in levenshtein distance
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 20 Oct 2017 16:05:09 -0000


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

Pascal Schumacher commented on TEXT-103:
----------------------------------------

[~arohit] Consider this issue assigned to you anyway. Looking forward to the pull request/patch. Thanks in advance! (Sadly it is not possible to assign issues to people who are not part of the commons developer group in jira, so it has to stay unassigned in jira.)

> Add provision to change the cost for insert, delete and replace operation in levenshtein distance
> -------------------------------------------------------------------------------------------------
>
>                 Key: TEXT-103
>                 URL: https://issues.apache.org/jira/browse/TEXT-103
>             Project: Commons Text
>          Issue Type: Improvement
>            Reporter: Rohit Agarwal
>            Priority: Minor
>              Labels: newbie, patch
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> There are two implementation of levenshtein distance, unlimitedCompare and limitedCompare.
> I propose to generalise the levenshtein distance by adding an option to change the value of
> 1) Addition of Character.
> 2) Deletion of Character.
> 3) Substitution of Character.
> Currently they are all set to 1. For backward compatibility this will be the default case.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)