Re: Decide on facets from results

Thanks for the suggestion Joe. I will check on it. Thanks! Mark. On Fri, Apr 29, 2016 at 11:56 AM, Joel Bernstein wrote: > Check out the new docs for the gatherNodes streaming expression. it Allows > you to aggregate and then use those aggregates as input for another >

Re: Decide on facets from results

Check out the new docs for the gatherNodes streaming expression. it Allows you to aggregate and then use those aggregates as input for another expression. You can even do this across collections. https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62693238 This is slated for Solr

Re: Decide on facets from results

Thanks much everyone! Appreciate your responses. Best, Mark On Thu, Apr 28, 2016 at 10:52 AM, Jay Potharaju wrote: > 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 >

Re: Decide on facets from results

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 wrote: > > Thanks Eric! > So that

Re: Decide on facets from results

Maybe you could do this: - MyFacetComponent extends FacetComponent - MyFacetComponent.process(): The results will be available at this point; look at them and decide which facets to fetch and return Best, Georg Alexandre Rafalovitch schrieb am Do., 28. Apr. 2016

Re: Decide on facets from results

What about a custom component? Something similar to spell-checker? Add it last after everything else. It would have to be custom because you have some domain magic about how to decide what fields to facet on. Regards, Alex. Newsletter and resources for Solr beginners and intermediates:

Re: Decide on facets from results

Mark: You can do anything you want that Java can do ;). Smart-alec comments aside, there's no mechanism for doing this in Solr that I know of. The first thing I'd do is try the two-query- from-the-client approach to see if it was "fast enough". Best, Erick (the other one) On Wed, Apr 27, 2016

Re: Decide on facets from results

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

Re: Decide on facets from results

Results will vary based on how you indexed those fields, but sure… =on= - with sufficient RAM, lots of fun to be had! — Erik Hatcher, Senior Solutions Architect http://www.lucidworks.com > On Apr 27, 2016, at 12:13 PM, Mark Robinson