[
https://issues.apache.org/jira/browse/TAJO-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253572#comment-15253572
]
ASF GitHub Bot commented on TAJO-2127:
--------------------------------------
Github user hyunsik commented on a diff in the pull request:
https://github.com/apache/tajo/pull/1005#discussion_r60709717
--- Diff: tajo-plan/src/main/java/org/apache/tajo/plan/LogicalPlanner.java
---
@@ -577,7 +577,7 @@ public static void verifyProjectedFields(QueryBlock
block, Projectable projectab
public static void prohibitNestedRecordProjection(Projectable
projectable)
throws TajoException {
for (Target t : projectable.getTargets()) {
- if (t.getEvalTree().getValueType().getType() ==
TajoDataTypes.Type.RECORD) {
+ if (t.getEvalTree().getValueType().isStruct()) {
--- End diff --
Currently, record is right. I need to make them consistent. According to my
future plan, struct would be better. That's why they are mixed.
> Use Type instead of DataType for EvalNode
> -----------------------------------------
>
> Key: TAJO-2127
> URL: https://issues.apache.org/jira/browse/TAJO-2127
> Project: Tajo
> Issue Type: Improvement
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.12.0
>
>
> See TAJO-2042 and TAJO-2043. This issue will change the return type of
> EvalNode::getValueType() to be org.apache.tajo.type.Type and its related
> code. Also, I'll some converter to order to keep existing APIs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
