[
https://issues.apache.org/jira/browse/TAJO-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829638#comment-13829638
]
Hyunsik Choi edited comment on TAJO-266 at 11/22/13 4:23 AM:
-------------------------------------------------------------
The purpose is very great and definitely necessary for us. But, I'm not sure
that this concept would be work well. To ensure that, we need a prototype. So,
I would like to suggest you to make a branch and test some example queries. For
example, the current Tajo does not support self-join. If multiple output is
supported, self joins will be easily implemented without duplicate scans. If
you agree, I would like to participate in that work.
was (Author: hyunsik):
The purpose is very great and definitely necessary for us. But, I'm not sure
that this concept would be work well. To ensure that, we need a prototype. So,
I would like to suggest you to make a branch and test some example queries. For
example, the current Tajo does not support self-join. If multiple output is
supported, self joins will be easily implemented without duplicate scans. If
you agree, I would like to participated in that work.
> Extend ExecutionBlock and Task to support multiple outputs
> ----------------------------------------------------------
>
> Key: TAJO-266
> URL: https://issues.apache.org/jira/browse/TAJO-266
> Project: Tajo
> Issue Type: Task
> Components: distributed query plan, worker
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Attachments: convert execution plan.jpg, current master plan.jpg,
> optimized master plan.jpg
>
>
> In the current Tajo, every task has the only one output.
> However, supporting multiple outputs per task very useful for the distributed
> plan optimization.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
