You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mayya Sharipova (JIRA)" <ji...@apache.org> on 2018/10/17 20:04:00 UTC

[jira] [Commented] (LUCENE-8529) Use the completion key to tiebreak completion suggestion

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

Mayya Sharipova commented on LUCENE-8529:
-----------------------------------------

Thanks [~jim.ferenczi]. I was wondering if there is any reason why we don't put all this comparison logic (scores, keys, docIds) inside `SuggestScoreDoc::compareTo`, and then just use `a.compare(b)`, where `a` and `b` are `SuggestScoreDoc`?

> Use the completion key to tiebreak completion suggestion
> --------------------------------------------------------
>
>                 Key: LUCENE-8529
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8529
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Jim Ferenczi
>            Priority: Minor
>         Attachments: LUCENE-8529.patch
>
>
> Today the completion suggester uses the document id to tiebreak completion suggestion with same scores. It would improve the stability of the sort to use the surface form of suggestions as the first tiebreaker.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org