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

Steve Rowe commented on SOLR-11943:
-----------------------------------

Under Maven, compilation was failing due to this issue causing the solr-core 
module to start using commons-math3 classes in a compile scope, while declaring 
it as test scope in the ivy.xml.
 
This didn’t cause a problem for the Ant build, since all Solrj’s compile-scope 
dependencies are included in solr-core’s compilation classpath.  The Maven 
build was affected because the POMs are automatically generated from the Ant 
build’s *direct* classpaths.


I fixed the problem by switching the scope of the solr-core commons-math3 
dependency from test to compile scope in solr-core’s ivy.xml, so that the Maven 
POMs would be correctly generated.

> Add machine learning functions for location data
> ------------------------------------------------
>
>                 Key: SOLR-11943
>                 URL: https://issues.apache.org/jira/browse/SOLR-11943
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Joel Bernstein
>            Assignee: Joel Bernstein
>            Priority: Major
>             Fix For: master (8.0), 7.5
>
>         Attachments: SOLR-11943.patch
>
>
> This ticket will add the following functions / features:
> 1) *latlonVectors* function: Reads a list of tuples that contain a *location* 
> field type  of lat, lon pairs and returns a *matrix* of lat,lon vectors. 
> 2) Add support for *haversinMeters* distance measure.
> With the addition of these two functions we'll have the ability to do various 
> distance based machine learning algorithms (distance matrices, clustering, 
> knn regression etc...) with location data.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to