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

ASF GitHub Bot commented on ARROW-1817:
---------------------------------------

BryanCutler opened a new pull request #1375: ARROW-1817: [Java] Configure 
JsonReader to read floating point NaN values
URL: https://github.com/apache/arrow/pull/1375
 
 
   The last upgrade of the Jackson JSON library changed behavior to no longer 
allow reading of "NaN" values  by default.  This change configures the JSON 
generator and parser to allow for NaN values (unquoted) alongside standard 
floating point numbers.  A test was added for JSON writing/reading and modified 
the test for Arrow file and stream .

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Configure JsonFileReader to read NaN for floats
> -----------------------------------------------
>
>                 Key: ARROW-1817
>                 URL: https://issues.apache.org/jira/browse/ARROW-1817
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Java - Vectors
>            Reporter: Bryan Cutler
>            Assignee: Bryan Cutler
>              Labels: pull-request-available
>             Fix For: 0.8.0
>
>
> There is a Spark unit test that includes reading JSON floating point values 
> that are NaN's (validity bit is set).  The Jackson parser in Arrow version 
> 0.4 allowed for these by default, but looks like the updated version requires 
> the conf {{ALLOW_NON_NUMERIC_NUMBERS}} to allow this. 
> https://fasterxml.github.io/jackson-core/javadoc/2.2.0/com/fasterxml/jackson/core/JsonParser.Feature.html#ALLOW_NON_NUMERIC_NUMBERS



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to