You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Jacques Nadeau (JIRA)" <ji...@apache.org> on 2015/05/05 15:36:34 UTC

[jira] [Updated] (DRILL-1961) Field definition should match the structure of ValueVector

     [ https://issues.apache.org/jira/browse/DRILL-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques Nadeau updated DRILL-1961:
----------------------------------
    Fix Version/s:     (was: 1.0.0)
                   1.2.0

> Field definition should match the structure of ValueVector
> ----------------------------------------------------------
>
>                 Key: DRILL-1961
>                 URL: https://issues.apache.org/jira/browse/DRILL-1961
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Execution - Data Types
>            Reporter: Hanifi Gunes
>            Assignee: Hanifi Gunes
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> Drill relies on container vectors to represent nested data types. In this case, materialized field def'n should capture the state of the container vector. Drill should either enforce synchrony between a MaterializedField and its owning ValueVector or avoid using MaterializedField as ValueVectors already represent a hierarchy of vectors which makes use of MaterializedField redundant.
> An instance for this case would be TestFastComplexSchema#test3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)