[
https://issues.apache.org/jira/browse/SOLR-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn van Groningen updated SOLR-3316:
----------------------------------------
Attachment: SOLR-3316.patch
Thanks for creating the test case!
I dived into the issue and I figured out why the matches is wrong when the top
groups aren't retrieved from all shards. The total hit count (matches) is now
computed in the first phase instead of in the second phase. The test passes now.
What is odd is that the grouping request where stats is being used even fails
when grouping is disabled...
I think this issue also occur in all 3.x versions.
> Distributed Grouping fails in some scenarios.
> ---------------------------------------------
>
> Key: SOLR-3316
> URL: https://issues.apache.org/jira/browse/SOLR-3316
> Project: Solr
> Issue Type: Bug
> Components: SearchComponents - other
> Affects Versions: 4.0
> Environment: Windows 7, JDK 6u26
> Reporter: Cody Young
> Labels: distributed, grouping
> Attachments: SOLR-3316.patch, TestDistributedGrouping.java.patch
>
>
> During a distributed grouping request, if rows is set to 0 a 500 error is
> returned.
> If groups are unique to a shard and the row count is set to 1, then the
> matches number is only the matches from one shard.
> I've put together a failing test.
--
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: [email protected]
For additional commands, e-mail: [email protected]
