Thanks Joel, really appreciate your help. I'll keep an eye on the 4.6.1
release.
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-Result-Grouping-vs-CollapsingQParserPlugin-tp4111331p4111486.html
Sent from the Solr - User mailing list archive at Nabble.com.
ot;
> If we split shards, will Result Grouping / CollapsingQParserPlugin and
> number of results still work ?
>
> Last but not the least, when are you planning to release 4.6.1 ?
>
> Again, appreciate your help on this.
>
> - Thanks
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/SolrCloud-Result-Grouping-vs-CollapsingQParserPlugin-tp4111331p4111375.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-Result-Grouping-vs-CollapsingQParserPlugin-tp4111331p4111375.html
Sent from the Solr - User mailing list archive at Nabble.com.
Also, there are a number of bugs in the CollapsingQParserPlugin in Solr 4.6
that are resolved in Solr 4.6.1 which should be out soon.
Joel Bernstein
Search Engineer at Heliosearch
On Tue, Jan 14, 2014 at 10:00 PM, Joel Bernstein wrote:
> Shamik,
>
> You still need to keep docs in the same grou
Shamik,
You still need to keep docs in the same group on the same shard with the
CollapsingQParserPlugin. If you use the group id as the shard-key with
SolrCloud's automatic document routing (
http://searchhub.org/2013/06/13/solr-cloud-document-routing/), the groups
will automatically end up on th
Hi,
I'm planning to upgrade to Solr 4.6 to move from using Result Grouping to
CollapsingQParserPlugin. I'm currently using SolrCloud, couple of issues
with Result Grouping are :
1. Slow performance
2. Incorrect result count from ngroup
My understanding is that CollapsingQParserPlugin is aimed
