[
https://issues.apache.org/jira/browse/SOLR-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152987#comment-13152987
]
Ryan McKinley commented on SOLR-2037:
-------------------------------------
TransformerContext != Request.getContext() it has lots of info about the query
that made the DocList -- this is necessary for things that need to know the
actual Query and DocIterator -- see ExplainAugmenterFactory.
Rather then adding SolrQueryRequest to the transform, we could also add it to
the TransformerContext.
Yes, setContext() is potentially more error prone then passing it along with
every transform call -- but this also gives us a consistent way to avoid lazy
loading. We know setContext is called before any documents are transformed.
Rather then have the lazy load logic i suggested earler, what about putting
that in setContext?
> 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
>
>
> 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]
