You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2014/06/24 16:02:24 UTC

[jira] [Updated] (TAJO-888) (Unbrella) Refactor DAG framework

     [ https://issues.apache.org/jira/browse/TAJO-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyunsik Choi updated TAJO-888:
------------------------------

    Description: 
We designed the ealier DAG framework in 2011. Since then, I have faced  new requirements for more efficient distributed query execution and more optimization opportunities. Because the additional requirements require lots of work, I have delayed the works.

The main purpose of this issue is to record and track the additional requirements and new features. This is an umbrella issue. Later, we would make an overall refactoring plan by using these well-defined requirements.

  was:
We designed the ealier DAG framework in 2011. Since then, I have faced  new requirements for more efficient distributed query execution and more optimization opportunities. Since the requirements require lots of work, I have delayed them.

The main purpose of this issue is to record and track the additional requirements and new features. This is an umbrella issue. Later, we would make an overall refactoring plan by using these well-defined requirements.


> (Unbrella) Refactor DAG framework
> ---------------------------------
>
>                 Key: TAJO-888
>                 URL: https://issues.apache.org/jira/browse/TAJO-888
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: Hyunsik Choi
>
> We designed the ealier DAG framework in 2011. Since then, I have faced  new requirements for more efficient distributed query execution and more optimization opportunities. Because the additional requirements require lots of work, I have delayed the works.
> The main purpose of this issue is to record and track the additional requirements and new features. This is an umbrella issue. Later, we would make an overall refactoring plan by using these well-defined requirements.



--
This message was sent by Atlassian JIRA
(v6.2#6252)