Return-Path: X-Original-To: apmail-drill-dev-archive@www.apache.org Delivered-To: apmail-drill-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DE64D17D6D for ; Fri, 10 Apr 2015 20:21:13 +0000 (UTC) Received: (qmail 93142 invoked by uid 500); 10 Apr 2015 20:21:13 -0000 Delivered-To: apmail-drill-dev-archive@drill.apache.org Received: (qmail 93091 invoked by uid 500); 10 Apr 2015 20:21:13 -0000 Mailing-List: contact dev-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 dev@drill.apache.org Received: (qmail 93042 invoked by uid 99); 10 Apr 2015 20:21:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Apr 2015 20:21:13 +0000 Date: Fri, 10 Apr 2015 20:21:13 +0000 (UTC) From: "Jason Altekruse (JIRA)" To: dev@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DRILL-2754) Allocation bug in splitAndTransfer method causing some flatten queries to fail MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jason Altekruse created DRILL-2754: -------------------------------------- Summary: Allocation bug in splitAndTransfer method causing some flatten queries to fail Key: DRILL-2754 URL: https://issues.apache.org/jira/browse/DRILL-2754 Project: Apache Drill Issue Type: Bug Components: Execution - Data Types, Execution - Relational Operators Reporter: Jason Altekruse Assignee: Jason Altekruse Priority: Critical Data for reproduction: {code} { "config": [ [], [ "a string" ] ] } {code} {code} select flatten(config) as flat from cp.`/store/json/null_list.json` {code} This was carved out of a larger use case that was failing, so in the course of coming up with a minimal reproduction I fixed the bug. I will be posting a patch shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)