[
https://issues.apache.org/jira/browse/LUCENE-6819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890472#comment-15890472
]
Jan Høydahl commented on LUCENE-6819:
-------------------------------------
I like the Atomic part and alternating between WARN on first-time and DEBUG
thereafter!
Should the deprecation patch have a solr/CHANGES.txt entry even if it is a
LUCENE issue? Well, it's a hybrid issue, and we have explicitly referenced
LUCENE issues in solr CHANGES earlier.
> Deprecate index-time boosts?
> ----------------------------
>
> Key: LUCENE-6819
> URL: https://issues.apache.org/jira/browse/LUCENE-6819
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-6819-deprecation.patch,
> LUCENE-6819-deprecation.patch, LUCENE-6819.patch, LUCENE-6819.patch,
> LUCENE-6819-wip.patch
>
>
> Follow-up of this comment:
> https://issues.apache.org/jira/browse/LUCENE-6818?focusedCommentId=14934801&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14934801
> Index-time boosts are a very expert feature whose behaviour is tight to the
> Similarity impl. Additionally users have often be confused by the poor
> precision due to the fact that we encode values on a single byte. But now we
> have doc values that allow you to encode any values the way you want with as
> much precision as you need so maybe we should deprecate index-time boosts and
> recommend to encode index-time scoring factors into doc values fields instead.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
