Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BD62B18666 for ; Fri, 26 Jun 2015 17:56:11 +0000 (UTC) Received: (qmail 91286 invoked by uid 500); 26 Jun 2015 17:56:06 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 91248 invoked by uid 500); 26 Jun 2015 17:56:06 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 91192 invoked by uid 99); 26 Jun 2015 17:56:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Jun 2015 17:56:06 +0000 Date: Fri, 26 Jun 2015 17:56:06 +0000 (UTC) From: "Jason Altekruse (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DRILL-3323) Flatten planning rule creates unneeded copy of the list being flattened, causes executuion/allocation issues with large lists MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DRILL-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Altekruse updated DRILL-3323: ----------------------------------- Fix Version/s: (was: 1.1.0) 1.2.0 > Flatten planning rule creates unneeded copy of the list being flattened, causes executuion/allocation issues with large lists > ----------------------------------------------------------------------------------------------------------------------------- > > Key: DRILL-3323 > URL: https://issues.apache.org/jira/browse/DRILL-3323 > Project: Apache Drill > Issue Type: Bug > Components: Execution - Flow > Reporter: Jason Altekruse > Assignee: Jason Altekruse > Fix For: 1.2.0 > > > The planning rule for flatten was written to not only handle the flatten operator, but it also was designed to address some shortcomings in expression evaluation involving complex types. The rule currently plans inefficiently to try to cover some of these more advanced cases, but there is not thorough test coverage to even demonstrate the benefits of it. We should disable a particular behavior of copying complex data and extra time when it is not needed, because it is causing flatten queries to fail with allocation issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)