[
https://issues.apache.org/jira/browse/TAJO-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370447#comment-14370447
]
ASF GitHub Bot commented on TAJO-1130:
--------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/423#issuecomment-83826070
Hi guys,
I agree with all you guys. This feature still requires unit tests, yet I
also don't want to double test time. We can compromise it.
First of all, this feature will completely work after we have a better
scheduler. So, we need to mark this feature as experimental for a while. As
navis said, we need to keep it disabled by default, and if necessary, users can
enable this feature with session variables.
With this approach, we may not need to verify all unit tests with this
feature right now. We won't double the unit test time. Nevertheless, since this
feature will require unit tests, it would be great if we test this this feature
in only some unit tests like TestJoinQuery and TestUnionQuery, which mostly
have independent execution blocks.
After we have a better scheduler, Tajo will use this feature by default. At
that time, all unit tests verify this feature.
> Concurrent execution of independent execution blocks
> -----------------------------------------------------
>
> Key: TAJO-1130
> URL: https://issues.apache.org/jira/browse/TAJO-1130
> Project: Tajo
> Issue Type: Improvement
> Components: query master
> Reporter: Jihoon Son
> Assignee: Navis
>
> Currently, Tajo can execute ExecutionBlocks one by one even though there
> remain enough resources to execute two or more ExecutionBlocks.
> We can improve the query processing performance by executing two or more
> independent ExecutionBlocks if possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
