lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Commented] (SOLR-4336) 4.1 no longer treats blank request params the same way as 4.0
Date Wed, 23 Jan 2013 03:22:12 GMT


Mark Miller commented on SOLR-4336:

This is probably my fault - I think I made some changes for solr.xml that may have affected
this. Just did not notice because it did not trip any tests most likely. This was so that
you could set properties like ${property:} and get the default value by not not setting that

This is just a guess at the moment - the memory is still loose - but a direction to look.
> 4.1 no longer treats blank request params the same way as 4.0
> -------------------------------------------------------------
>                 Key: SOLR-4336
>                 URL:
>             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

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message