You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Mehant Baid (JIRA)" <ji...@apache.org> on 2014/11/11 01:00:42 UTC

[jira] [Resolved] (DRILL-1613) Drill does not honor nested schema changes

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

Mehant Baid resolved DRILL-1613.
--------------------------------
    Resolution: Fixed

Fixed in 61053a8c9c22e7cce45bb74e3e1894f2cfd42041

> Drill does not honor nested schema changes
> ------------------------------------------
>
>                 Key: DRILL-1613
>                 URL: https://issues.apache.org/jira/browse/DRILL-1613
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Hanifi Gunes
>            Assignee: Mehant Baid
>             Fix For: 0.7.0
>
>
> Drill's current definition of schema change is an incremental update to the top-level schema structure. This is inappropriate for complex data types where schema change may occur at any level in the hierarchy of vectors. Current design does not fit into this requirement neatly as only top-level containers are able to mutate the schema. We need a minor to major re-design to handle this situation.
> This issue exacerbates when querying partitions or batches of files that do not necessarily conform to the exact same schema. New fields from upcoming batches will be omitted in either case. 



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