Hi Amit,
could you tell me is this problem fix in Solr 4.6.0?
because i still having this problem or any suggestion?
please help.
thank you very much,
Chun.
--
View this message in context:
http://lucene.472066.n3.nabble.com/group-ngroups-behavior-in-response-tp4033924p4132473.html
Sent from
A new response attribute would be better but it also complicates the patch
in that it would require a new way to serialize DocSlices I think
(especially when group.main=true)? I was looking to set group.main=true so
that my existing clients don't have to change to parse the grouped
resultset format
I'd think adding a new response attribute would be more flexible and
powerful, thinking about clients, UIs, etc.
Otis
--
Solr & ElasticSearch Support
http://sematext.com/
On Thu, Jan 17, 2013 at 10:15 AM, Tomás Fernández Löbbe <
tomasflo...@gmail.com> wrote:
> Bu Amit is right, when you use
Bu Amit is right, when you use group.main, the number of groups is not
displayed, even if you set grop.ngroups.
I think in this case NumFound should display the number of groups instead
of the number of docs matching. Other option would be to keep "numFound" as
the number of docs matching and add
There's a parameter to enable that. :D
In solrJ
solrQuery.setParam("group.ngroups", true);
http://wiki.apache.org/solr/FieldCollapsing
--
View this message in context:
http://lucene.472066.n3.nabble.com/group-ngroups-behavior-in-response-tp4033924p4034187.html
Sent from the Solr - User maili
Hi all,
I recently discovered the group.main=true/false parameter which really has
made life simple in terms of ensuring that the format coming out of Solr
for my clients (RoR app) is backwards compatible with the non-grouped
results which ensures no special "handle grouped results" logic.
The on
