[
https://issues.apache.org/jira/browse/TAJO-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368480#comment-14368480
]
Dongjoon Hyun commented on TAJO-1355:
-------------------------------------
Thank you for your detail and helpful description. Overall problem is really
hard. What about doing full-qualification pre-processing first in order to
reduce a possibility of occurence of this problem?
> 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)
