[
https://issues.apache.org/jira/browse/TAJO-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903052#comment-13903052
]
Hyunsik Choi commented on TAJO-595:
-----------------------------------
Removed ExprVerifierContext and changed ExprsVerifier to use VerificationState
like before.
Updated the review request against branch master in reviewboard
https://reviews.apache.org/r/18075/
> The same expressions without different alias are not allowed.
> -------------------------------------------------------------
>
> Key: TAJO-595
> URL: https://issues.apache.org/jira/browse/TAJO-595
> Project: Tajo
> Issue Type: Bug
> Components: planner/optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.8-incubating
>
> Attachments: TAJO-595.patch, TAJO-595_140217_172537.patch,
> TAJO-595_20140217_14:04:25.patch, TAJO-595_20140217_14:33:31.patch,
> TAJO-595_20140217_14:56:20.patch
>
>
> Currently, LogicalPlanner and ProjectionPushDownRule do not allow the same
> expressions with different alias names. The following query is an example of
> this restriction.
> {code}
> select l_orderkey + 1 as total1, orderkey + 1 as total2 from ..
> {code}
> The main cause of this bug is that NamedExprManager and TargetListManager
> only keep 1:1 mapping relationship between alias and expression. This patch
> changes them to keep 1:N mapping relationship.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
