Mailing-List: contact issues-help@impala.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@impala.incubator.apache.org
Date: Wed, 22 Mar 2017 00:44:41 +0000 (UTC)
From: "Tim Armstrong (JIRA)" <jira@apache.org>
To: issues@impala.incubator.apache.org
Message-ID: <JIRA.13056827.1489704571000.83301.1490143481550@Atlassian.JIRA>
In-Reply-To: <JIRA.13056827.1489704571000@Atlassian.JIRA>
References: <JIRA.13056827.1489704571000@Atlassian.JIRA> <JIRA.13056827.1489704571130@jira-lw-us.apache.org>
Subject: [jira] [Commented] (IMPALA-5084) Backend support for large rows in
 Sorter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 22 Mar 2017 00:44:48 -0000


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

Tim Armstrong commented on IMPALA-5084:
---------------------------------------

As a temporary solution, it may be reasonable to just increase the default buffer size in the sorter to match the maximum row size, given that the sorter's buffer requirements are more modest than the joins and aggs, and there are typically fewer sorts in a plan.

> Backend support for large rows in Sorter
> ----------------------------------------
>
>                 Key: IMPALA-5084
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5084
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Backend
>    Affects Versions: Impala 2.6.0
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Minor
>              Labels: resource-management
>
> See IMPALA-3208 for the context.
> Sorter::Run changes:
> * We can use a similar approach to that used for BufferedTupleStream as described in IMPALA-5085
> Testing:
> Needs end-to-end tests exercising all operators with large operators


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)