[
https://issues.apache.org/jira/browse/SOLR-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153010#comment-13153010
]
Ryan McKinley commented on SOLR-2037:
-------------------------------------
rather then:
{code}
- public abstract void transform(SolrDocument doc, int docid) throws
IOException;
+ public abstract void transform(SolrDocument doc, int docid, SolrQueryRequest
req) throws IOException;
{code}
What about adding SolrQueryRequest to the TransformerContext? This could avoid
the lazy load logic in this Transformer, and also give access to
SolrQueryRequest for things that need batch processing (as yonik discussed)
bq. Or should the user explicitly put [elevated] in their field list?
+1 this should all be explicit
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
