[
https://issues.apache.org/jira/browse/TAJO-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368483#comment-14368483
]
Hyunsik Choi edited comment on TAJO-1355 at 3/19/15 4:23 AM:
-------------------------------------------------------------
That may be one solution for this issue. Actually, LogicalPlanPreProcessor
partially replaces names with fully qualified names. But, in order to replace
fully them into fully qualified names, it still requires much effort.
was (Author: hyunsik):
That may be one solution for this issue. Actually, LogicalPlanPreProcessor
partially replaces names with fully qualified names. But, it requires more
effort to replace fully them into fully qualified names.
> All column resolving should be as fully qualified names.
> --------------------------------------------------------
>
> Key: TAJO-1355
> URL: https://issues.apache.org/jira/browse/TAJO-1355
> Project: Tajo
> Issue Type: Improvement
> Components: planner/optimizer
> Reporter: Hyunsik Choi
>
> Currently, schemas used in a logical plan includes fully qualified names and
> simple name without qualified names. It makes many parts complicated
> unnecessarily.
> For example, Schema class can be simplified if it maintains only qualified
> names. Binding correct columns in FieldEval can be simplified if we do it.
> Also, many query optimization code would be simple.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
