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

ASF subversion and git services commented on LUCENE-8638:
---------------------------------------------------------

Commit 26093735cc4731a3079f36293cf185e1afb6a128 in lucene's branch 
refs/heads/main from Alan Woodward
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=2609373 ]

LUCENE-8638: Expressions haversin() method should continue to return its value 
in km (#299)

SloppyMath had a deprecated haversin() function that returned its values in
km, which has been replaced by a haversinMeters() function that is explicit
about its units. As part of removing this function, we changed the expressions
module haversin function to point instead to haversinMeters. However, this
may silently change the behaviour of expressions on upgrade.

This commit instead adds a haversinKilometers method to the expressions
module and maps the haversin function to it. It also adds a new
haversinMeters expression function to be more explicit for future users.

> Remove deprecated code in main
> ------------------------------
>
>                 Key: LUCENE-8638
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8638
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Alan Woodward
>            Assignee: Alan Woodward
>            Priority: Blocker
>             Fix For: main (9.0)
>
>          Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> There are a number of deprecations in master that should be removed. This 
> issue is to keep track of deprecations as a whole, some individual 
> deprecations may require their own issues.
>  
> Work on this issue should be pushed to the `master-deprecations` branch on 
> gitbox



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to