[
https://issues.apache.org/jira/browse/SOLR-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152998#comment-13152998
]
Grant Ingersoll commented on SOLR-2037:
---------------------------------------
@Ryan, that clarifies things. I have left it as is.
@Yonik:
bq. The only question left then is if the augmenter/transformer should be on by
default if QEC is being used (i.e. forceElevation==true?) Or should the user
explicitly put [elevated] in their field list? I'm thinking the latter, for
folks who put fl=id and expect only the id field to be returned.
Agreed, I think it should be off by default.
bq. It would also be nice if one didn't have to define this
EditorialMarkerFactory in solr.xml... seems like from the user perspective it
should "just work" (either the QEC can dynamically register it, or it can
always be registered by default like explain, docid, etc).
Good point. Consider it done.
> Distinguish Editorial Results from "normal" results in the
> QueryElevationComponent
> ----------------------------------------------------------------------------------
>
> Key: SOLR-2037
> URL: https://issues.apache.org/jira/browse/SOLR-2037
> Project: Solr
> Issue Type: Improvement
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Attachments: EditorialMarkerFactory.java,
> SOLR-2037-editoral-marker.patch, SOLR-2037.patch, SOLR-2037.patch
>
>
> In many cases, it would be nice if the results that are provided by the
> QueryElevationComponent were identified as such so that one could make a
> decision at rendering time whether to treat them differently or not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
