[
https://issues.apache.org/jira/browse/SOLR-11834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552385#comment-16552385
]
Munendra S N commented on SOLR-11834:
-------------------------------------
[~mkhludnev]
I encountered a problem using subquery transformer with multi-sharded
collections.
In all others cases (standalone and single sharded), it works as expected.
With multi-sharded collections, subquery's fl should always be a subset of main
query's fl
I wanted to know why it works for standalone/single sharded but doesn't work
for multi-sharded. So, did a little digging into the code
In case of standalone/single sharded, subquery response would be added as
result Context and Response Writer handle writing result context(here,
subquery's fl is available)
In case of multi-sharded, first pass is similar to standalone/single sharded.
In case of a sharded request, all shard responses would be collected then the
final response would be formed (as per my understanding, please correct if I'm
wrong).
In the final response, subquery's response would SolrDocumentList. In case of
SolrDocumentList, main's query fl is used in the responseWriter hence, this
issue
> [Ref-Guide] Wrong documentation for subquery transformer
> --------------------------------------------------------
>
> Key: SOLR-11834
> URL: https://issues.apache.org/jira/browse/SOLR-11834
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Munendra S N
> Priority: Major
> Fix For: 7.3, master (8.0)
>
> Attachments: SOLR-11834.patch, SOLR-11834.png
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Documentation for subquery transformation mentioned that to retrieve the
> field, it should be specified in both fl parameter
> https://lucene.apache.org/solr/guide/7_2/transforming-result-documents.html#subquery-result-fields
> But there is no such restriction in code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
