[
https://issues.apache.org/jira/browse/TAJO-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14949820#comment-14949820
]
Hudson commented on TAJO-1900:
------------------------------
SUCCESS: Integrated in Tajo-0.11.0-build #99 (See
[https://builds.apache.org/job/Tajo-0.11.0-build/99/])
TAJO-1900: When a record column and its child column are retrieved (jihoonson:
rev becab195c58b9eac6f468dbab52596d423ff53d7)
*
tajo-plan/src/main/java/org/apache/tajo/plan/rewrite/SelfDescSchemaBuildPhase.java
*
tajo-core-tests/src/test/java/org/apache/tajo/engine/query/TestQueryOnSelfDescTable.java
* CHANGES
> When a record column and its child column are retrieved together, the record
> column might not be inferred as record type properly
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAJO-1900
> URL: https://issues.apache.org/jira/browse/TAJO-1900
> Project: Tajo
> Issue Type: Bug
> Components: Planner/Optimizer
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Fix For: 0.11.0
>
> Attachments: TAJO-1900.patch
>
>
> For example, given a following query, the column 'glossary' can be inferred
> as the TEXT type rather than the RECORD type.
> {noformat}
> default> select glossary from self_desc_table2 where
> char_length(glossary."GlossDiv".title) > 0
> {noformat}
> This is because columns of the query are inferred in an arbitrary order, and
> there isn't any routine to resolve the conflict of inferred data type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
