[
https://issues.apache.org/jira/browse/TAJO-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738358#comment-14738358
]
ASF GitHub Bot commented on TAJO-1833:
--------------------------------------
GitHub user jihoonson opened a pull request:
https://github.com/apache/tajo/pull/752
TAJO-1833: Refine LogicalPlanPreprocessor to add new rules easily
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jihoonson/tajo-2 TAJO-1833
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/752.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 #752
----
commit 2445c7d6c4d5b6cead7db09936d08945da043acf
Author: Jihoon Son <[email protected]>
Date: 2015-09-10T07:54:07Z
TAJO-1833
----
> 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
>
> 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)
