Can you describe more about what you're trying to do in the merge? Why does it seem it's too late to drop documents in the merge?
If you can provide a very simple example with some sample records and a sample output, that would be helpful. Joel Bernstein http://joelsolr.blogspot.com/ On Thu, Aug 4, 2016 at 4:25 PM, tedsolr <tsm...@sciquest.com> wrote: > I've been struggling just to get my search plugin working for sharded > collections, but I haven't ascertained if my end goal is even achievable. I > have a plugin that groups documents that are considered duplicates (based > on > multiple fields - like the CollapsingQParserPlugin). When responses come > back from different shards another culling will be necessary to remove > dupes > between the shards. In the merge() method it seems it will be too late to > simply "drop" documents. Is this something that the client will just have > to > deal with? Maybe in the process() method of a search component? I was > expecting to be able to preserve the requested return count, but that seems > really unlikely now. > > Thanks for any suggestions, > Ted v5.2.1 > > > > -- > View this message in context: http://lucene.472066.n3.nabble.com/Can-a- > MergeStrategy-filter-returned-docs-tp4290446.html > Sent from the Solr - User mailing list archive at Nabble.com. >
