You know about the 'invariant' that can be set in the request handler,
right? Not sure if that will do for you or not, but sounds related.
Added recnetly to some wiki page somewhere although the feature has been
there for a long time. Let's see if I can find the wiki page...Ah yes:
http://wiki.apache.org/solr/SearchHandler#Configuration
Markus Jelsma wrote:
Hi,
Thanks for the suggestion and pointer. We've implemented it using a single
regex in Nginx for now.
Cheers,
: Anyone knows useful method to disable or prohibit the per-field override
: features for the search components? If not, where to start to make it
: configurable via solrconfig and attempt to come up with a working patch?
If your goal is to prevent *clients* from specifying these (while you're
still allowed to use them in your defaults) then the simplest solution is
probably something external to Solr -- along the lines of mod_rewrite.
Internally...
that would be tough.
You could probably write a SearchComponent (configured to run "first")
that does it fairly easily -- just wrap the SolrParams in an impl that
retuns null anytime a component asks for a param name that starts with
"f." (and excludes those param names when asked for a list of the param
names)
It could probably be generalized to support arbitrary rules i na way
that might be handy for other folks, but it would still just be
wrapping all of hte params, so it would prevent you from using them
in your config as well.
Ultimatley i think a general solution would need to be in
RequestHandlerBase ... where it wraps the request params using the
defaults and invariants ... you'd want the custom exclusion rules to apply
only to the request params from the client.
-Hoss
