[
https://issues.apache.org/jira/browse/LUCENE-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529129#comment-13529129
]
Ryan McKinley commented on LUCENE-4616:
---------------------------------------
Earlier today, I committed a small change on LUCENE-3795 but realize the change
was based on not-understanding some assumptions.
We should clarify the assumptions in javadoc and/or the API.
My understanding now is that the API returned ConstantScoreQuery rather then
Query to explicitly say the score is undefined (not necessarily
distance/overlap/whatever).
I see two directions for this call:
#1 - Return a Query, and in the javadoc for SpatialStrategy say that the score
value is undefined (but strategies may have a meaningful score)
#2 - return ConstantScore and make the javadoc explicit that the score is not
meaningful
I vote for #1 since it is more general and lets applications/implementations
work more easily
> Clarify what the score means in SpatialStrategy#makeQuery()
> -----------------------------------------------------------
>
> Key: LUCENE-4616
> URL: https://issues.apache.org/jira/browse/LUCENE-4616
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Ryan McKinley
> Priority: Trivial
>
> SpatialStrategy#makeQuery() returns a Query, but the docs don't make it clear
> with the score value should be.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
