[
https://issues.apache.org/jira/browse/DRILL-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908182#comment-14908182
]
Aman Sinha commented on DRILL-3831:
-----------------------------------
[~jaltekruse] will this address DRILL-2796 and its duplicate DRILL-3286 ? If
so, could you add a link in those JIRAs to this one ? thanks.
> Allow null values in lists
> --------------------------
>
> Key: DRILL-3831
> URL: https://issues.apache.org/jira/browse/DRILL-3831
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Data Types
> Reporter: Jason Altekruse
> Assignee: Jason Altekruse
> Fix For: 1.3.0
>
>
> Drill currently fails to read a json file where a list has a value of null in
> it. We have a workaround with all_text_mode for this case, but we need to
> enhance Drill to support this concept in the core ValueVector data structure
> used to represent records.
> As part of this change, I am considering removing the concept of a list that
> requires all of its members to be non-null, effectively the only type of list
> we have today. The data that can be read today would simply be read into a
> list where the members could be nullable, but they all happen to be non-null.
> This would simplify the code to prevent the need to cover the null and
> non-null cases explicitly.
> Initially this could pose a risk with a minor performance hit, but overall
> our approach with complex data is not been heavily performance tested.
> Keeping the code simple for now will at least allow for more thorough testing
> of the smaller number of cases, and hopefully make it easier to reason about
> and improve as we evaluate the performance of Drill with complex data more
> thoroughly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
