Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C7323200C37 for ; Sun, 19 Mar 2017 14:25:50 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C5BAE160B7D; Sun, 19 Mar 2017 13:25:50 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1A1F2160B6E for ; Sun, 19 Mar 2017 14:25:49 +0100 (CET) Received: (qmail 32956 invoked by uid 500); 19 Mar 2017 13:25:49 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 32945 invoked by uid 99); 19 Mar 2017 13:25:49 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Mar 2017 13:25:49 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id D757AC00BE for ; Sun, 19 Mar 2017 13:25:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.651 X-Spam-Level: X-Spam-Status: No, score=0.651 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id BQNvoycFGMyb for ; Sun, 19 Mar 2017 13:25:48 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 161445FE2A for ; Sun, 19 Mar 2017 13:25:48 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C757AE0502 for ; Sun, 19 Mar 2017 13:25:43 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6C829254CB for ; Sun, 19 Mar 2017 13:25:42 +0000 (UTC) Date: Sun, 19 Mar 2017 13:25:42 +0000 (UTC) From: "Pascal Schumacher (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Reopened] (LANG-1269) Wrong name or result of StringUtils::getJaroWinklerDistance MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 19 Mar 2017 13:25:51 -0000 [ https://issues.apache.org/jira/browse/LANG-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Schumacher reopened LANG-1269: ------------------------------------- > Wrong name or result of StringUtils::getJaroWinklerDistance > ----------------------------------------------------------- > > Key: LANG-1269 > URL: https://issues.apache.org/jira/browse/LANG-1269 > Project: Commons Lang > Issue Type: Bug > Affects Versions: 3.3, 3.4, 3.5 > Reporter: Jan Martin Keil > Assignee: Pascal Schumacher > Priority: Minor > Fix For: 3.6 > > > The name of the method StringUtils::getJaroWinklerDistance is misleading. > Currently for equal strings {{1}} is returned, for completely different strings {{0}} is returned. That is a measure of similarity, not of a distance. A distance must be {{0}} for equal strings. I read on the issues LANG-591 and LANG-944, that it was decided to have a similar name to StringUtils::getLevenshteinDistance, but that requires also the change of the methods result. > Could you please (1) rename the method to StringUtils::getJaroWinklerSimilarity or (2) change the method to return {{1 - currentResult}}? > First option has the disadvantage to lose the similar naming of the similar methods, second option implies the risk to unnoticed introduce bugs in depending code. So I think it is preferable to use the first option. -- This message was sent by Atlassian JIRA (v6.3.15#6346)