On Mon, Apr 9, 2012 at 9:36 PM, Mark Miller <markrmil...@gmail.com> wrote: > Yeah, that's how it works - it ends up hitting the select request handler > (this might be overridable with shards.qt) All the params are passed along, > so in general, it will act the same as the top level req handler - but it can > the remove the shards param so you don't have an infinite recursion of > distrib requests (say in the case you put shards in the tea handler in > solrconfig). > > I think you have to investigate shards.qt > Or look at adding those components to the std select handler as well.
Thanks. > > Sent from my iPhone > > On Apr 9, 2012, at 9:26 PM, Benson Margulies <bimargul...@gmail.com> wrote: > >> Um, maybe I've hit a quirk? >> >> In my solrconfig.xml, my special SearchComponents are installed only >> for a specific QT. So, it looks to me as if that QT is not propagated >> into the request out to the shards, and so they run the ordinary >> request handler without my components in it. >> >> Is this intended behavior I have to tweak via a distribution-aware >> component, or perhaps a bug, or does it make no sense at all and I >> need to look for some mistake of mine?
