[ 
https://issues.apache.org/jira/browse/SOLR-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043448#comment-16043448
 ] 

Tomás Fernández Löbbe commented on SOLR-10833:
----------------------------------------------

Thanks for the review Hoss
bq. perhaps we should add some replacement/wrapper methods
Yes, that's good. I'll change that. One thing I want to be careful is not to 
throw SolrException(4XX) in all cases, since in some a SolrException(5XX) makes 
more sense (and for those, we may want to keep the NFE as it would today). I'll 
work on a patch. 

Any thoughts on tests I may be missing?

> Numeric FooPointField classes inconsistent with TrieFooFields on malformed 
> input: throw NumberFormatException
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-10833
>                 URL: https://issues.apache.org/jira/browse/SOLR-10833
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Hoss Man
>            Assignee: Tomás Fernández Löbbe
>         Attachments: SOLR-10833.patch, SOLR-10833.patch, SOLR-10833.patch
>
>
> Trie based Numeic fields deal with bad input by wrapping 
> NumberFormatExceptions in w/BAD_REQUEST SolrExceptions -- PointFields are 
> just allowing the NumberFormatExceptions to be thrown as is, which means they 
> propagate up and are eventually treated as a SERVER_ERROR when responding to 
> clients.
> This is not only inconsistent from an end user perspective -- but also breaks 
> how these errors are handled in SolrCloud when the requests have been 
> forwarded/proxied.
> We should ensure that the FooPointField classes behave consistently with the 
> TrieFooField classes on bad input (both when adding a document, or query 
> creating a field query)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to