A couple of ideas. If this is 5x consider Streaming Aggregation. The idea here is that you stream the docs back to a SolrJ client and slice and dice them there. SA is designed to export 400K docs/sec, but the returned values must be DocValues (i.e. no text types, strings are OK).
Have you seen the CollapsingQParserPlugin? That might help. Or push back at the product manager and say "why are we wasting time supporting something nobody uses?" ;) Best, Erick On Wed, May 11, 2016 at 1:45 AM, Callum Lamb <cl...@mintel.com> wrote: > We have a horrible Solr query that groups by a field and then sorts by > another. My understanding is that for this to happen it has to sort by the > grouping field, group it and then sort the resulting result set. It's not a > fast query. > > Unfortunately our documents now need to be grouped as well (product > variants into items) and that grouping query needs to work on that grouping > instead. As far as I'm aware you can't do nested grouping in Solr. > > In summary we want to have product variants that get grouped into Items and > then they get grouped by field and then sorted by another. > > The solution doesn't need to be fast, it's a rarely ever used legacy part > of our application that's basically never used and we just need it to work. > Our dataset isn't huge so it doesn't matter if Solr has to scan the entire > index (I think the query does this atm anyway). But downloading the entire > document set and doing the operations in ETL isn't something we really want > to dedicate time to unless it's impossible to represent this in Solr > queries. > > Any ideas? > > Cheers, > > Callum. > > -- > > Mintel Group Ltd | 11 Pilgrim Street | London | EC4V 6RN > Registered in England: Number 1475918. | VAT Number: GB 232 9342 72 > > Contact details for our other offices can be found at > http://www.mintel.com/office-locations. > > This email and any attachments may include content that is confidential, > privileged > or otherwise protected under applicable law. Unauthorised disclosure, > copying, distribution > or use of the contents is prohibited and may be unlawful. If you have > received this email in error, > including without appropriate authorisation, then please reply to the > sender about the error > and delete this email and any attachments. >
