[ 
https://issues.apache.org/jira/browse/TEXT-188?focusedWorklogId=495135&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-495135
 ]

ASF GitHub Bot logged work on TEXT-188:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Oct/20 23:10
            Start Date: 04/Oct/20 23:10
    Worklog Time Spent: 10m 
      Work Description: kinow closed pull request #174:
URL: https://github.com/apache/commons-text/pull/174


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 495135)
    Time Spent: 1h 20m  (was: 1h 10m)

> Speed up LevenshteinDistance with threshold
> -------------------------------------------
>
>                 Key: TEXT-188
>                 URL: https://issues.apache.org/jira/browse/TEXT-188
>             Project: Commons Text
>          Issue Type: Improvement
>    Affects Versions: 1.9
>            Reporter: Jakob Vesterstrøm
>            Assignee: Bruno P. Kinoshita
>            Priority: Major
>             Fix For: 1.9.1
>
>         Attachments: improvement.patch
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The calculation made by the LevenshteinDistance class can often be made 
> faster, when the class in initialized with a threshold, and when the distance 
> is found to be larger than the threshold. In those cases, it is often not 
> necessary to iterate through the whole string, since a lower bound for the 
> result can be established after each iteration. If that lower bound is larger 
> than the threshold, the method can simply exit early with the same result as 
> without this improvement. 
> A patch with the proposed change is attached to this issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to