Hi Joel,
Had missed this email .. Some issue with my gmail setting.
The reason CollapsignQParserPlugin is more performant than regular grouping
is because
1. QParser refers to global ords for group.field and avoids storing
strings in a set. This has two advantage.
a) Terms of memory (storin
Umesh, this is a good summary.
So, the question is what is the cost (performance and memory) of having the
CollapsingQParserPlugin choose the group head by using the Solr sort
criteria?
Keep in mind that the CollapsingQParserPlugin's main design goal is to
provide fast performance when collapsing
Continuing the discussion on mailing list from Jira.
An Example
*id group f1 f2*1 g1
5 10
2 g1 5 1000
3 g1 5 1000
4 g1 10 100
5 g2
Thanks Joel for the quick response. I have opened a new jira ticket.
https://issues.apache.org/jira/browse/SOLR-6168
On 13 June 2014 17:45, Joel Bernstein wrote:
> Let's open a new ticket.
>
> Joel Bernstein
> Search Engineer at Heliosearch
>
>
> On Fri, Jun 13, 2014 at 8:08 AM, Umesh Prasad
Let's open a new ticket.
Joel Bernstein
Search Engineer at Heliosearch
On Fri, Jun 13, 2014 at 8:08 AM, Umesh Prasad wrote:
> The patch in SOLR-5408 fixes the issue with sorting only for two sort
> fields. Sorting still breaks when 3 or more sort fields are used.
>
> I have attached a test cas
