Been looking at the code a bit, and it seems it's not disabled per se, it's just not there. The normal searcher has an inbuilt result set cache check before and after executing, where as the Grouping#execute doesn't have any concept of result cache.
Can't they just share the same cache and implementation system? Has this just simply not been "done" yet? There also seems to be a lot of prep and post work around the Grouping#execute call from QueryComponent that doesn't exist around searcher#search. Should this code perhaps be refactored into an intermediate step? I'm looking at: QueryComponent#process Grouping#execute SolrIndexSearcher#search and getDocList Cheers for the info. Antony. -- View this message in context: http://lucene.472066.n3.nabble.com/Why-is-query-result-set-caching-disabled-for-grouping-queries-tp3604540p3604696.html Sent from the Solr - User mailing list archive at Nabble.com.
