On 9/8/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: > The main use case is to allow configuration of a requestHandler that the
: > clients don't have to be aware of at all it "just works" ..
:
: That sounds fine then for things that are optinally appended, but not
: being able to override that doesn't make sense unless it's for some
: security purpose.
But if i'm the onwer of the index shouldn't that be my decision?
Yes, if that's what they really want.
The usecase you gave of setting reasonable append defaults for lists
seems like the most common one. If the only configuration option
available to people is to have non-overridable appends, it will get
used as convenience (or error) and end up being a pain.
I guess I'd like to see both problems solved so one mechanism isn't abused.
if i
want people to be able to have free reign over my index, i'll do this...
<requestHandler name="dismax" class="solr.DisMaxRequestHandler" />
Yeah, that would work, but most people will take an evolutionary
approach, adding defaults to existing handlers I think. Having
separate handlers for this is also a take-it-or-leave-it approach...
if you want to override just one useful default, you need to supply
them all.
: Parameters that must always be appended seem to be the exception
: rather than the rule.
: But if that's the only mechanism to provide good defaults for
: appendable lists, people might use it and unnecessarily lock down the
: view of their data, even if it's not what they *really* meant to do.
why would it be the only mechanism?
Because we don't currently have any mechanism to specify an additive
default. If you added something like <appends>, it *would* be the
only mechanism ;-)
-Yonik
