Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Mon, 5 Oct 2015 23:58:32 +0000 (UTC)
From: "Jacques Nadeau (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12901733.1443653352000.31913.1444089512095@Atlassian.JIRA>
In-Reply-To: <JIRA.12901733.1443653352000@Atlassian.JIRA>
References: <JIRA.12901733.1443653352000@Atlassian.JIRA>
 <JIRA.12901733.1443653352751@arcas>
Subject: [jira] [Commented] (DRILL-3876) flatten() should not require a
 subsequent project to strip columns that aren't required
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jacques Nadeau commented on DRILL-3876:
---------------------------------------

As Jason mentions, the multi-flatten case makes planning a pain since we have to actually break these into sub-operators. If you're only looking to solve the single flatten case, that should be easier. You would simply need to have flatten's config also include a "pass-through fields" attribute.

I recommend implementing this as a task after implementing UDTFs. Multiflatten could then become a special UDTF and the logic would become much simpler to write. This would also vastly simplify the flatten rule. I'll put together a proposal on UDTFs.

> flatten() should not require a subsequent project to strip columns that aren't required
> ---------------------------------------------------------------------------------------
>
>                 Key: DRILL-3876
>                 URL: https://issues.apache.org/jira/browse/DRILL-3876
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow
>    Affects Versions: 1.2.0
>            Reporter: Chris Westin
>            Assignee: Chris Westin
>


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