drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Nadeau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-47) Generate Logical Plans for TPC-H Queries
Date Fri, 16 May 2014 10:47:02 GMT

    [ https://issues.apache.org/jira/browse/DRILL-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998966#comment-13998966

Jacques Nadeau commented on DRILL-47:

We've now gotten to the point of using SQL queries so this is no longer necessary.

> Generate Logical Plans for TPC-H Queries
> ----------------------------------------
>                 Key: DRILL-47
>                 URL: https://issues.apache.org/jira/browse/DRILL-47
>             Project: Apache Drill
>          Issue Type: New Feature
>            Reporter: Jacques Nadeau
>            Assignee: Sree Vaddi
> Creating example logical plans should help in many ways.  Among those are validation
cases for the sql parser, logical plan completeness, execution engine performance, etc.  It
would be great if someone could generate logical plans for each of the TPC-H queries.
> TPC-H Queries are in SQL. (not sure, if they use any ANSI SQL 2003 features ?)
> Use 'sqlparser' project to convert them in to respective logical plan in json format
(json for now. any other formats we support now or in future ?)
> Use 'plan-parser' project to convert them into respective physical plan. (what is the
output format(s) here for now and in future ?)
> Use 'ref' project to execute those physical plans. (how ?)
> The data is in PSV (pipe separated value) files.
> Converting these to JSON files.
> There are 20 sql files and 5 variant sql files.
> Creating one sub-task jira for each of the sql files.  Everything related to that sql
will be in it, i.e. sql parser, logical plan, execution stats ...

This message was sent by Atlassian JIRA

View raw message