Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Thu, 1 Oct 2015 19:14:27 +0000 (UTC)
From: "Chun Chang (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12833605.1432853376000.4739.1443726867216@Atlassian.JIRA>
In-Reply-To: <JIRA.12833605.1432853376000@Atlassian.JIRA>
References: <JIRA.12833605.1432853376000@Atlassian.JIRA>
 <JIRA.12833605.1432853376165@arcas>
Subject: [jira] [Updated] (DRILL-3209) [Umbrella] Plan reads of Hive tables
 as native Drill reads when a native reader for the underlying table format
 exists
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chun Chang updated DRILL-3209:
------------------------------
    Attachment: tpch13-native-scan-on.sys.drill
                tpch13-native-scan-off.sys.drill

> [Umbrella] Plan reads of Hive tables as native Drill reads when a native reader for the underlying table format exists
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-3209
>                 URL: https://issues.apache.org/jira/browse/DRILL-3209
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Query Planning & Optimization, Storage - Hive
>            Reporter: Jason Altekruse
>            Assignee: Venki Korukanti
>             Fix For: 1.2.0
>
>         Attachments: tpch13-native-scan-off.sys.drill, tpch13-native-scan-on.sys.drill
>
>
> All reads against Hive are currently done through the Hive Serde interface. While this provides the most flexibility, the API is not optimized for maximum performance while reading the data into Drill's native data structures. For Parquet and Text file backed tables, we can plan these reads as Drill native reads. Currently reads of these file types provide untyped data. While parquet has metadata in the file we currently do not make use of the type information while planning. For text files we read all of the files as lists of varchars. In both of these cases, casts will need to be injected to provide the same datatypes provided by the reads through the SerDe interface.


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