On the same lines as Erik suggested but using facet stats instead. you can get stats on your facet fields in the first pass and then include the facets that you need in the second pass.
> On Apr 27, 2016, at 1:21 PM, Mark Robinson <mark123lea...@gmail.com> wrote: > > Thanks Eric! > So that will mean another call will be definitely required to SOLR with the > facets, before the results can be send back (with the facet fields being > derived traversing through the response). > > I was basically checking on whether in the "process" method (I believe > results will be accessed in the process method), we can dynamically > generate facets after traversing through the results and identifying the > fields for faceting, using some aggregation function or so, without having > to make another call using facet=on&facet.field=<field_name>, before the > response is send back to the user. > > Cheers! > > On Wed, Apr 27, 2016 at 2:27 PM, Erik Hatcher <erik.hatc...@gmail.com> > wrote: > >> Results will vary based on how you indexed those fields, but sure… >> &facet=on&facet.field=<field_name> - with sufficient RAM, lots of fun to be >> had! >> >> — >> Erik Hatcher, Senior Solutions Architect >> http://www.lucidworks.com <http://www.lucidworks.com/> >> >> >> >>>> On Apr 27, 2016, at 12:13 PM, Mark Robinson <mark123lea...@gmail.com> >>> wrote: >>> >>> Hi, >>> >>> If I don't have my facet list at query time, from the results can I >> select >>> some fields and by any means create a facet on them? ie after I get the >>> results I want to identify some fields as facets and send back facets for >>> them in the response. >>> >>> A kind of very dynamic faceting based on the results! >>> >>> Cld some one pls share their idea. >>> >>> Thanks! >>> Anil. >> >>
