[jira] [Created] (SOLR-4336) 4.1 no longer treats blank request params the same way as 4.0

["Hoss Man (JIRA)" <ji...@apache.org>]

Hoss Man created SOLR-4336:
------------------------------

             Summary: 4.1 no longer treats blank request params the same way as 4.0
                 Key: SOLR-4336
                 URL: https://issues.apache.org/jira/browse/SOLR-4336
             Project: Solr
          Issue Type: Bug
    Affects Versions: 4.1
            Reporter: Hoss Man


I haven't figured out where/why this changed, but IRC user trmnlr pointed out to me that a query like the following example works fine in Solr 4.0 and results in the default value for "start", but produces a 'NumberFormatException: For input string: ""' in Solr 4.1...

http://localhost:8983/solr/select?q=*:*&start=&rows=10

...the code related to parsing the "start" param hasn't changed between 4.0 and 4.1, suggesting that this is a more general regression in behavior in something more lower level, that probably affects all SolrParams -- anywhere in the past that users might have safely specify an empty string value and still get Solr's "default" value will likely now behave differently.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org