I suspected you would be interested in this issue, Jan.
Yes, it could be as simple as an extends attribute there. That was my initial idea. Two other questions:
- Is there an implied default inherited request handler? Here you could specify "df", "q.op", "f.myfieldname.facet.method", ...
- Could/should you be able to declare a handler that is only for extension and not for direct use? If so then how would it be declared as such?
- multiple extended request handlers resulting in mixin capability? – e.g extends="base,foo,bar" Or is this overkill?
There is something to be said for simplicity of how it works. So maybe simply one parent, no way to prevent a search of a RH aside from avoiding a leading '/' (assuming handleSelect is disabled) which is good enough... and maybe no default extends since all the RH definitions declared in solrconfig.xml out of the box could refer to a base one.
This should be easy to implement.