Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Thu, 1 Oct 2015 13:45:26 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12901730.1443652582000.1839.1443707126507@Atlassian.JIRA>
In-Reply-To: <JIRA.12901730.1443652582000@Atlassian.JIRA>
References: <JIRA.12901730.1443652582000@Atlassian.JIRA>
 <JIRA.12901730.1443652582185@arcas>
Subject: [jira] [Commented] (DRILL-3874) flattening large JSON objects
 consumes too much direct memory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF GitHub Bot commented on DRILL-3874:
---------------------------------------

Github user cwestin commented on the pull request:

    https://github.com/apache/drill/pull/181#issuecomment-144729913
  
    Passes the unit tests, and the regression suite, except for one query in the functional suite that Rahul claimed (in email) is a known problem and that he has a fix for.


> flattening large JSON objects consumes too much direct memory
> -------------------------------------------------------------
>
>                 Key: DRILL-3874
>                 URL: https://issues.apache.org/jira/browse/DRILL-3874
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow
>    Affects Versions: 1.1.0
>            Reporter: Chris Westin
>            Assignee: Chris Westin
>
> A JSON record has a field whose value is an array with 20,000 elements; the record's size is 4MB. A select is used to flatten this. The query profile reports that the peak memory utilization was 8GB, most of it used by the flatten. 


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