[ https://issues.apache.org/jira/browse/SOLR-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039919#comment-16039919 ]
Hoss Man commented on SOLR-10833: --------------------------------- discovered while working on SOLR-10807 > 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 > Attachments: 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org