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

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.1
• Component/s: search
• Assignee: Unassigned
• Reporter: Chris M. Hostetter
• Created: 23/Jan/13 03:02
• Updated: 09/Jan/18 21:54

Description

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.

Issue Links

• is related to: SOLR-4371 Admin UI - Analysis Screen shows empty result
• relates to: SOLR-4265 Fix decoding of GET/POST parameters for servlet containers with non-UTF-8 URL parsing (Tomcat)
• relates to: SOLR-4283 Improve URL decoding (followup of SOLR-4265)