[
https://issues.apache.org/jira/browse/GEODE-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker closed GEODE-3206.
--------------------------------
> lucene search results in gfsh are listed in reverse relevancy order
> -------------------------------------------------------------------
>
> Key: GEODE-3206
> URL: https://issues.apache.org/jira/browse/GEODE-3206
> Project: Geode
> Issue Type: Bug
> Components: lucene
> Reporter: Diane Hardman
> Assignee: Deepak Dixit
> Priority: Major
> Fix For: 1.3.0
>
>
> Using the lucene example in the pull request for GEODE-3202, execute one of
> the lucene searches that returns multiple results. For example:
> search lucene --name=simpleIndex --region=example-region
> --queryStrings="firstName:pat OR lastName:chive~" --defaultField=lastName
> The results should list employee with name 'Pat' first since it is an exact
> match and has a higher relevancy score. Instead it lists:
> key | value
> | score
> ----- |
> ---------------------------------------------------------------------------------------------------------------
> | ----------
> 10015 | EmployeeData [firstName=Jamie, lastName=Jive, emplNumber=10015,
> email= [email protected], salary=60000, .. | 0.14384104
> 10028 | EmployeeData [firstName=Pat, lastName=Puts, emplNumber=10028, email=
> [email protected], salary=75000, hour.. | 0.2876821
> Note the higher relevancy score is listed second.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
