[
https://issues.apache.org/jira/browse/TAJO-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183904#comment-14183904
]
ASF GitHub Bot commented on TAJO-1125:
--------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/210#issuecomment-60470554
Actually, this patch includes the module separation and package move. I
rearrange the packages of plan, optimizer, and expressions. In some viewpoint,
it may be not unnecessary.
But, the module separation inevitably causes conflicts against the patches
for plan, optimizer, and expression part. The package rename is very trivial
than the module separation. It just requires to rearrange package imports.
The reason why this patch includes the package rename is to cleanup the
package. The current package hierarchy of plan, optimizer, and expressions is
too ugly and inconsistent.
> Separate logical plan and optimizer into a maven module
> -------------------------------------------------------
>
> Key: TAJO-1125
> URL: https://issues.apache.org/jira/browse/TAJO-1125
> Project: Tajo
> Issue Type: Improvement
> Components: planner/optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.9.1
>
>
> We already have a bunch of codes for logical planner, its optimizer,
> expressions, and expression optimizer. They have played a key role in Tajo
> project.
> As Tajo is being evolved, many parts started to require planner and
> optimization code. It's because we are trying to make good use of planning
> information in more parts.
> But, since the planner and optimization parts are included in tajo-core,
> other maven modules should depend on {{tajo-core}} which is the biggest maven
> module in Tajo.
> So, I propose to separate logical planner, logical optimizer, expression and
> expression optimizer from tajo-core into a separate maven module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
