[
https://issues.apache.org/jira/browse/TAJO-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137404#comment-14137404
]
ASF GitHub Bot commented on TAJO-1049:
--------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/147
TAJO-1049: Remove the parallel degree limit up to the maximum cluster ca...
...pacity.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-1049
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/147.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 #147
----
commit bdeedac47697b072f8d32e5673a4651e611bf6c7
Author: Hyunsik Choi <[email protected]>
Date: 2014-09-17T15:37:01Z
TAJO-1049: Remove the parallel degree limit up to the maximum cluster
capacity.
----
> Remove the parallel degree limit up to the maximum cluster capacity
> -------------------------------------------------------------------
>
> Key: TAJO-1049
> URL: https://issues.apache.org/jira/browse/TAJO-1049
> Project: Tajo
> Issue Type: Improvement
> Components: data shuffle, distributed query plan
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Priority: Trivial
> Fix For: 0.9.0
>
> Attachments: TAJO-1049.patch
>
>
> The maximum parallel degree had been limited by the number of cluster node
> capacity. This was because the old hash shuffle approach created too many
> small files depending on the number of parallel degree of a stage.
> But, TAJO-992 solved this problem. We don't need to use this limit anymore.
> This patch removes the limit.
> I think that this patch requires cluster test and it is hard to verify this
> patch in unit tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
