Github user hyunsik commented on a diff in the pull request:
https://github.com/apache/tajo/pull/71#discussion_r15042347
--- Diff:
tajo-core/src/main/java/org/apache/tajo/engine/planner/LogicalPlanner.java ---
@@ -383,7 +386,7 @@ private EvalExprNode
buildPlanForNoneFromStatement(PlanContext context, Stack<Ex
for (int i = 0; i < targets.length; i++) {
NamedExpr namedExpr = projection.getNamedExprs()[i];
- EvalNode evalNode = exprAnnotator.createEvalNode(plan, block,
namedExpr.getExpr());
+ EvalNode evalNode = exprAnnotator.createEvalNode(plan, block,
namedExpr.getExpr(), NameResolvingMode.RELS_ONLY);
--- End diff --
As you know, non-from statement does not need to resolve any column because
non-from statement means no table and no column reference.
The main difference among the resolving modes is the priority and scope. It
is enough to use the mode which has the correct priority and the scope. If
possible, it would be nice if we use the mode the minimum scope. RELS_ONLY is
the minimum scope one.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
