If you just need to transform an individual result, that can be done by a custom DocTransformer. But from your email, I think you need a custom SearchComponent.
On Fri, Jan 23, 2015 at 6:23 PM, tedsolr <tsm...@sciquest.com> wrote: > Hello! With the help of this community I have solved 2 problems on my way > to > creating a search that collapses documents based on multiple fields. The > CollapsingQParserPlugin was key. > > I have a new problem now. All the custom stats I generate in my custom > QParser makes for way to much data to simply write out in the response. I > need to filter that data so I only return the stats the user will see on > one > page. Say my search returns 800K collapsed docs - in the > DelegatingCollector's collect() method I am computing some info for each > collapsed group - that's 800K map entries. > > I can't filter the stats in my post filter implementation because the > results have not been sorted. So I need a new downstream component that can > read the sorted results, and grab the custom stats from my post filter. Can > someone recommend a suggestion? Is this a SearchComponent extension? Where > is the proper hook for examining results after sorting? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/How-to-inject-custom-response-data-after-results-have-been-sorted-tp4181545.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- Regards, Shalin Shekhar Mangar.
