You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Vova Vysotskyi (Jira)" <ji...@apache.org> on 2020/02/27 13:34:00 UTC

[jira] [Assigned] (DRILL-7610) Allow user to specify table schema in Metastore

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

Vova Vysotskyi reassigned DRILL-7610:
-------------------------------------

    Assignee: Vova Vysotskyi

> Allow user to specify table schema in Metastore
> -----------------------------------------------
>
>                 Key: DRILL-7610
>                 URL: https://issues.apache.org/jira/browse/DRILL-7610
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.17.0
>            Reporter: Paul Rogers
>            Assignee: Vova Vysotskyi
>            Priority: Major
>
> The Drill Metastore will infer the schema of a table while gathering stats. Unfortunately, this creates a chicken-and-egg problem. Some files need the Metastore because the schema is ambiguous. Such data won't even scan correctly without such information. Classic JSON example:
> {code:json}
> {a: 10} {a: 10.1}
> {code}
> In these cases, the user should first define the table schema, then run the {{ANALYZE TABLE}} commands. In such cases, Drill should not attempt to change the type information (since the actual data is ambiguous.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)