[
https://issues.apache.org/jira/browse/TAJO-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738738#comment-14738738
]
Hudson commented on TAJO-1833:
------------------------------
SUCCESS: Integrated in Tajo-master-build #856 (See
[https://builds.apache.org/job/Tajo-master-build/856/])
TAJO-1833: Refine LogicalPlanPreprocessor to add new rules easily. (jihoonson:
rev 508d17a2d7fdb3f5ac9a9dabec46b6ec4e5fb1cb)
*
tajo-plan/src/main/java/org/apache/tajo/plan/rewrite/LogicalPlanRewriteEngine.java
* tajo-plan/src/main/java/org/apache/tajo/plan/rewrite/BaseSchemaBuildPhase.java
*
tajo-plan/src/main/java/org/apache/tajo/plan/rewrite/BaseLogicalPlanPreprocessPhaseProvider.java
* tajo-plan/src/main/java/org/apache/tajo/plan/LogicalPlanner.java
*
tajo-plan/src/main/java/org/apache/tajo/plan/rewrite/LogicalPlanPreprocessEngine.java
*
tajo-plan/src/main/java/org/apache/tajo/plan/rewrite/LogicalPlanRewriteRule.java
*
tajo-plan/src/main/java/org/apache/tajo/plan/rewrite/LogicalPlanPreprocessPhase.java
*
tajo-plan/src/main/java/org/apache/tajo/plan/rewrite/BaseLogicalPlanPreprocessEngine.java
* tajo-plan/src/main/java/org/apache/tajo/plan/LogicalPlanPreprocessor.java
*
tajo-plan/src/main/java/org/apache/tajo/plan/rewrite/LogicalPlanPreprocessPhaseProvider.java
*
tajo-plan/src/main/java/org/apache/tajo/plan/rewrite/BaseLogicalPlanRewriteEngine.java
* CHANGES
> Refine LogicalPlanPreprocessor to add new rules easily
> ------------------------------------------------------
>
> Key: TAJO-1833
> URL: https://issues.apache.org/jira/browse/TAJO-1833
> Project: Tajo
> Issue Type: Task
> Components: Planner/Optimizer
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Fix For: 0.11.0
>
>
> LogicalPlanPreprocessor is responsible for building base schema information.
> So far, it has been enough to do this.
> However, to support self-describing data formats well (TAJO-1832), the
> current architecture is difficult to fulfil the requirements.
> To make good use of self-described data format information, schema can be
> guessed at query runtime. I think that this should be done between logical
> plan preprocessing phase and logical planning phase. However, guessing schema
> is also a duty of LogicalPlanPreprocessor, that is building base schema
> information.
> For the sake of generality and extensibility, I think we need to refine
> LogicalPlanPreprocessor to add new rules easily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
