We had a comparable situation. We created an extra field and at index time
copy the value if there is one and create a unique dummy value if there is
none. We couldn't just make the initial field required, because it has a
meaning other than just a grouping key.
Teun
Op 22 feb. 2013 20:47 schreef "
ssama" het
volgende:
> Oh this is a good one ! Thank you very much Teun (But I will have to ask
> you how do you generate a unique value for the copy field when the original
> one is empty? Do you do this manualy or solr can do it?)
> And thanks again.
> On Feb 24, 2013 12:11 P
You have to set group.ngroups=true (see
http://wiki.apache.org/solr/FieldCollapsing). Be aware that including the
number of groups is a surprisingly heavy operation, though.
Teun
2013/2/25 Nicholas Ding
> Hello,
>
> I grouped the result, and set group.main=true. I was expecting the numFound
>
Ah, I see. The docs say "Although this result format does not have as much
information, it may be easier for existing solr clients to parse". I guess
the ngroups value could be added to this format, but apparently it isn't. I
do agree with you that to be usefull (as in possible to read for a client
What I really miss in the SimpleFaceting component is the ability to get
facets not of the full term, but grouped by the first letter(s). I wrote a
Jira issue on this ( https://issues.apache.org/jira/browse/SOLR-4496). I
also wrote a patch with a rather simplistic first try of an implementation.
N
