[
https://issues.apache.org/jira/browse/TAJO-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183728#comment-14183728
]
ASF GitHub Bot commented on TAJO-1125:
--------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/210
TAJO-1125: Separate logical plan and optimizer into a maven module.
I moved the followings to org.apache.tajo.plan in tajo-plan maven module.
* tajo.engine.planner.logical
* tajo.engine.planner.eval
* tajo.engine.planner.LogicalPlan
* tajo.engine.planner.LogicalPlanner
* tajo.engine.planner.LogicalOptimizer
...
Also, I moved Tuple, VTuple, and StorageConstants to tajo-common. Because
the right module of StorageConstatns is tajo-storage, it's a temporary
solution. I'll improve it more later.
In addition, I changed LogicalPlanner and LogicalOptimizer to take
OverridenConf instead of QueryContext due to dependency problem,
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-1125
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/210.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #210
----
commit efdfdfc31ed2a97a0885e2185d8fa5b1975d1fcd
Author: HyoungJun Kim <[email protected]>
Date: 2014-10-19T01:56:10Z
TAJO-1121: Remove the 'v2' storage package.
commit d34218722e22ce6fec6a5deaf399a16b5cfa2edd
Author: Hyunsik Choi <[email protected]>
Date: 2014-10-21T22:15:05Z
Merge branch 'TAJO-1121' of https://github.com/babokim/tajo
commit 11ec5fdc8a0c90e4c017614c9aab04fe60e71f4a
Author: Hyunsik Choi <[email protected]>
Date: 2014-10-24T23:22:53Z
TAJO-1125: Separate logical plan and optimizer into a maven module.
commit 80969fb4230afc588ff08052ad0eb13364e97826
Author: Hyunsik Choi <[email protected]>
Date: 2014-10-24T23:29:09Z
Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/tajo into
TAJO-1125
Conflicts:
tajo-core/src/main/java/org/apache/tajo/engine/planner/PhysicalPlannerImpl.java
tajo-core/src/main/java/org/apache/tajo/engine/planner/physical/HashShuffleFileWriteExec.java
tajo-core/src/main/java/org/apache/tajo/engine/planner/physical/PartitionMergeScanExec.java
tajo-core/src/main/java/org/apache/tajo/master/querymaster/Repartitioner.java
tajo-core/src/main/java/org/apache/tajo/master/querymaster/SubQuery.java
----
> 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)
