[
https://issues.apache.org/jira/browse/DRILL-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176852#comment-15176852
]
Aman Sinha commented on DRILL-3806:
-----------------------------------
[~julienledem] or [~jnadeau], for handling the untyped null in a JSON file that
begins with 4096 (or more) NULLs followed by string values, should we use the
union vector type ? It works for a simplified example but I am not sure about
general cases (the option for union type is off by default).
Any thoughts on what we want to do going forward with this scenario since it is
fairly common. If no one is working on this, I will look into it.
> add metadata for untyped null and simple type promotion
> -------------------------------------------------------
>
> Key: DRILL-3806
> URL: https://issues.apache.org/jira/browse/DRILL-3806
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Data Types
> Reporter: Julien Le Dem
> Fix For: Future
>
>
> Currently when a field has literal null values in JSON the type will be
> assigned as BIGINT by default for lack of better type.
> ```
> {
> "a": null
> }
> ```
> if later on a is assigned with a string value the query will fail with a
> schema change error,
> The idea is to capture the notion of "untyped null" and implement simple type
> promotion from untyped null to the actual type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
