: "uncool" comment was, er, uncool, but the motivation was that AFAIK in
: no other place does SOLR make this distinction, an assumption based on
: SolrParams not having an API to test for param existence and being
: explicitly coded around nonexistence and null being equatable; meanwhile
: elsewhere in the code (e.g. parseSort) null and "" are equated.
:
: So this would constitute a policy change, and one that required a
agreed ... trying to drive behavior based on the distinction between a
param being blank an a param not being specified at all is a bad idea ...
particularly since we've observed inconsistencies in the way some servlet
containers deal with empty params...
http://issues.apache.org/jira/browse/SOLR-12
-Hoss
