[
https://issues.apache.org/jira/browse/SOLR-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333810#comment-15333810
]
ASF subversion and git services commented on SOLR-7957:
-------------------------------------------------------
Commit 489f386b766882d717d1bf5f740b81c179084d0e in lucene-solr's branch
refs/heads/branch_5_5 from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=489f386 ]
SOLR-8902: don't try to pull return fields from the ResultContext - this
method, added in SOLR-7957, won't be backported to 5.x
> Allow multiple queries per request and simplify ResultContext /
> TransformContext
> --------------------------------------------------------------------------------
>
> Key: SOLR-7957
> URL: https://issues.apache.org/jira/browse/SOLR-7957
> Project: Solr
> Issue Type: Bug
> Components: search
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Fix For: 6.0
>
> Attachments: SOLR-7957.patch
>
>
> Today we have a ResultContext which simply has two public variables query and
> docList. For writing a response, those fields are used to create a
> DocsStreamer which creates a TransformContext for transformers (which just
> copies the values like searcher, req, q, etc again).
> It seems the all the methods on TransformContext could be simply moved to
> ResultContext.
> Only exception is "iterator" needed by ScoreAugmenter, but we could simply
> pass down the score in the transform() method as well.
> This would result in a ResultContext that could do things like support
> multiple queries with different return fields, and things like returning a
> list of docs from another core (think cross-core join).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
