[
https://issues.apache.org/jira/browse/DRILL-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972238#comment-14972238
]
Parth Chandra commented on DRILL-3229:
--------------------------------------
I think we do need to do the same thing as with complex types, see if the
client supports complex types or not, and if not, then convert to JSON.
Otherwise we will break the C++ client (fixing the C++ client for this would be
painful, and useless since no consumer of the API can currently handle the
Union type).
Untyped nulls will also break he C++ client, though it is easier to fix that,
so we probably should. IF you include a quick proposal on that, I an get a
headstart on the
> Create a new EmbeddedVector
> ---------------------------
>
> Key: DRILL-3229
> URL: https://issues.apache.org/jira/browse/DRILL-3229
> Project: Apache Drill
> Issue Type: Sub-task
> Components: Execution - Codegen, Execution - Data Types, Execution -
> Relational Operators, Functions - Drill
> Reporter: Jacques Nadeau
> Assignee: Hanifi Gunes
> Fix For: Future
>
>
> Embedded Vector will leverage a binary encoding for holding information about
> type for each individual field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
