[
https://issues.apache.org/jira/browse/SOLR-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531410#comment-13531410
]
Cassandra Targett edited comment on SOLR-4181 at 11/10/17 10:17 PM:
--------------------------------------------------------------------
The way to demonstrate this bug (and or that the bug is fixed) is to remove
this line in TestDistributedGrouping...
{noformat}
handle.put(t1 + ":this_will_never_match", SKIP); // :TODO: SOLR-4181
{noformat}
...which currently tells the test framework to ignore that value when
recursively comparing the respons structures since it's only in the single node
response, and not the distributed response.
was (Author: hossman):
The way to demonstrate this bug (and or that the bug is fixed) is to remove
this line in TestDistributedGrouping...
{noformat}
handle.put(t1 + ":this_will_never_match", SKIP); // :TODO: SOLR-4181
{nofromat}
...which currently tells the test framework to ignore that value when
recursively comparing the respons structures since it's only in the single node
response, and not the distributed response.
> grouping response format inconsistent in distributed search when no docs
> match group.query
> ------------------------------------------------------------------------------------------
>
> Key: SOLR-4181
> URL: https://issues.apache.org/jira/browse/SOLR-4181
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
>
> if a group.query does not match any documents, then in distribued search
> (aka: solrcloud) that group.query will be completley excluded frm the final
> result.
> This is inconsistent with single node grouping behavior, where the
> group.query will be included in the final result (in the orde that it's pat
> of the request) with a numFound=0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
