: I do understand what they do (at least well enough to use them), but I 
: find it confusing that it's called "defType" as a main param, but "type" 
: in a LocalParam, when to me they both seem to do the same thing -- which 

"type" as a localparam in a query string defines the type of query string 
it is -- picking hte parser.

"defType" determins the default value for "type" in the primary query 
string.

: (and then there's 'qt', often confused with defType/type by newbies, 
: since they guess it stands for 'query type', but which should probably 
: actually have been called 'requestHandler'/'rh' instead, since that's 
: what it actually chooses, no?  It gets very confusing).
: 
: If it's generally recognized it's confusing and perhaps a somewhat 
: inconsistent mental model being implied, I wonder if there'd be any 
: interest in renaming these to be more clear, leaving the old ones as 
: aliases/synonyms for backwards compatibility (perhaps with a long 

qt is historic and already being de-emphasized in favor of using 
path based names (ie: http://solr/handlername instead of 
http://solr/select?qt=/handlername) so adding yet another alias for that 
would be moving in the wrong direction.

"type" and "defType" probably make more sense when you think of 
them in that order.  I don't see a strong need to confuse/complicate the 
issue by adding more aliases for them.



-Hoss

Reply via email to