Agree on this, I wouldn't be surprised if there is a JIRA for it already, have you checked? Pass-through params are quite useful, so we could provide a special prefix 'x.' that would still be allowed, e.g. "x.myCustom=foo"
Jan > 12. nov. 2021 kl. 00:06 skrev Shawn Heisey <[email protected]>: > > On 11/4/2021 4:42 PM, Shawn Heisey wrote: >> This is possibly a pipe dream: > > Most of us are probably already aware that the original API ignores unknown > parameters sent in with a request. Some of our users utilize this for log > parsing -- by including some custom parameter on the request that Solr > ignores, they can easily locate requests they are looking for in solr.log. > > An interesting problem came up on the #solr slack channel. Solr was silently > ignoring the user's request to return facets. Eventually that user figured > out that they had unknowingly disabled the facet component on the request > handler as they were working on the config. > > I think Solr should have the ability, at least on the v2 api, to throw an > error when a parameter is not consumed and used by one of the handler's > components. An option with a name something like > "strictParameterValidation". That option should probably default to disabled > in current releases and 9.x, and then if it makes sense, we could possibly > choose to enable it by default in a later major release like 10.0. > > Thanks, > Shawn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
