[
https://issues.apache.org/jira/browse/SOLR-10825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223654#comment-17223654
]
Munendra S N commented on SOLR-10825:
-------------------------------------
+1 to support this.
Currently, user could pass facets and they get computed but won't be returned.
We had some usecase to compute stats on subquery. So, we had to implement
custom Doc transformer. I think we should return the total response returned by
subquery to the user. This change would break backward compatibility
Another thing, currently whole Solr document is converted as parameters to
subquery which would be expensive in case of large fields (ideally shouldn't be
stored in Solr). I understand the reason for passing whole doc as parameters is
that we are not sure on which doc fields are being used in subquery. One
workaround we have implemented in custom Doc transformer is to let user specify
which fields to use from the main document, when not specified it defaults to
current behavior. This might not be best solution (better would be to infer
from subquery parameters) but helped in our case so, share it here
> [subquery] facets support
> --------------------------
>
> Key: SOLR-10825
> URL: https://issues.apache.org/jira/browse/SOLR-10825
> Project: Solr
> Issue Type: Improvement
> Reporter: Mikhail Khludnev
> Priority: Major
>
> Let's also have facets in subquery response. I'm not sure about a particular
> format (where to nest a tag particularly), but I suppose it's worth to
> encourage {{json.facet}} usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
