Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-4336

4.1 no longer treats blank request params the same way as 4.0

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 4.1
    • Fix Version/s: None
    • Component/s: search
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                hossman Chris M. Hostetter
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: