You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/26 23:24:27 UTC
[jira] [Commented] (HAWQ-80) Support dynamic relation distribution
type in gpopt
[ https://issues.apache.org/jira/browse/HAWQ-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975225#comment-14975225 ]
ASF GitHub Bot commented on HAWQ-80:
------------------------------------
GitHub user entong opened a pull request:
https://github.com/apache/incubator-hawq/pull/42
HAWQ-80. Support dynamic relation distribution type in gpopt
If there are 3 hash distributed tables in a query, each has a different buckets number, say 8, 24 and 64, the resource negotiator will allocate max(8,24,64)=64 vSegs. In this case, the tables with buckets number 8 and 24 will need to be regarded as random distributed table during planning.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/entong/incubator-hawq HAWQ-80
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/42.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #42
----
commit d14101881b23564cdffcf8204706dfbbc3a94737
Author: Entong Shen <es...@pivotal.io>
Date: 2015-10-24T00:48:23Z
HAWQ-80. Support dynamic relation distribution type in gpopt
----
> Support dynamic relation distribution type in gpopt
> ----------------------------------------------------
>
> Key: HAWQ-80
> URL: https://issues.apache.org/jira/browse/HAWQ-80
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Optimizer
> Reporter: Entong Shen
> Assignee: Amr El-Helw
>
> If there are 3 hash distributed tables in a query, each has a different buckets number, say 8, 24 and 64, the resource negotiator will allocate max(8,24,64)=64 vSegs. In this case, the tables with buckets number 8 and 24 will need to be regarded as random distributed table during planning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)