[
https://issues.apache.org/jira/browse/LUCENE-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028858#comment-17028858
]
Alessandro Benedetti commented on LUCENE-9171:
----------------------------------------------
Hi [~romseygeek], thanks for your feedback again, that is very kind of you.
But I am not fully convinced of moving back to terms and a separate array of
boosts, that will be effectively ignored in Lucene and only used by
implementations (such as Solr).
Furthermore, I move the conditional parameter to extract them from the payload
info in Solr, but if we move back this to Lucene, it will be necessary to move
back the conditional extraction in Lucene?
What are the cons of [~dsmiley]suggestion of generalise this to use the
tokenstream instead?
In this way the Lucene signature will look all right as it uses the tokenstream
and Solr will use the tokenstream to extract payload info if the conditional
parameter is there.
What do you think?
> Synonyms Boost by Payload
> -------------------------
>
> Key: LUCENE-9171
> URL: https://issues.apache.org/jira/browse/LUCENE-9171
> Project: Lucene - Core
> Issue Type: New Feature
> Components: core/queryparser
> Reporter: Alessandro Benedetti
> Priority: Major
>
> I have been working in the additional capability of boosting queries by terms
> payload through a parameter to enable it in Lucene Query Builder.
> This has been done targeting the Synonyms Query.
> It is parametric, so it meant to see no difference unless the feature is
> enabled.
> Solr has its bits to comply thorugh its SynonymsQueryStyles
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
