lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cassandra Targett (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-4336) 4.1 no longer treats blank request params the same way as 4.0
Date Tue, 09 Jan 2018 21:55:00 GMT

     [ https://issues.apache.org/jira/browse/SOLR-4336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Cassandra Targett updated SOLR-4336:
------------------------------------
    Component/s: search

> 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
>          Components: search
>    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 was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message