drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5919) Add non-numeric support for JSON processing
Date Sat, 11 Nov 2017 01:48:00 GMT

    [ https://issues.apache.org/jira/browse/DRILL-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248269#comment-16248269

ASF GitHub Bot commented on DRILL-5919:

Github user paul-rogers commented on the issue:

    Further, is the extra option to `convertFromJSON` really needed? Can't we just accept
`NaN` and `Infinity` by default?
    Consider. If the option is off by default, users without `NaN` or `Infinity` data will
see no difference. But, users will this data will get an error and have to hunt down the option
to make their data work.
    If the option is on by default, users without `NaN` or `Infinity` data will see no difference.
But, users will this data will also have their queries work by default.
    So, seems no harm in making the `NaN` and `Infinity` support turned on by default.

> Add non-numeric support for JSON processing
> -------------------------------------------
>                 Key: DRILL-5919
>                 URL: https://issues.apache.org/jira/browse/DRILL-5919
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Storage - JSON
>    Affects Versions: 1.11.0
>            Reporter: Volodymyr Tkach
>            Assignee: Volodymyr Tkach
>              Labels: doc-impacting
>             Fix For: Future
> Add session options to allow drill working with non standard json strings number literals
like: NaN, Infinity, -Infinity. By default these options will be switched off, the user will
be able to toggle them during working session.
> *For documentation*
> 1. Added two session options {{store.json.reader.non_numeric_numbers}} and {{store.json.reader.non_numeric_numbers}}
that allow to read/write NaN and Infinity as numbers. By default these options are set to
> 2. Extended signature of {{convert_toJSON}} and {{convert_fromJSON}} functions by adding
second optional parameter that enables read/write NaN and Infinity.
> For example:
> {noformat}
> select convert_fromJSON('{"key": NaN}') from (values(1)); will result with JsonParseException,
> select convert_fromJSON('{"key": NaN}', true) from (values(1)); will parse NaN as a number.
> {noformat}

This message was sent by Atlassian JIRA

View raw message