[
https://issues.apache.org/jira/browse/TAJO-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369292#comment-14369292
]
ASF GitHub Bot commented on TAJO-1130:
--------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/423#issuecomment-83553971
Sorry. There are some misunderstandings. I mean that unit tests should be
added for this issue because it is difficult to expect what kinds of errors we
will meet.
However, I think it will be also difficult to write some new test functions
to test only concurrent execution of multiple stages. So, I suggest adding a
parameter to existing tests to test this feature. If so, we can test Tajo's
query processing with and without concurrent execution.
I think you already know the parameterized test, but you can find an
example at TestJoinQuery.
What do you think?
> 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)
