[jira] [Commented] (TAJO-1900) When a record column and its child column are retrieved together, the record column might not be inferred as record type properly

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAJO-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935135#comment-14935135 ] 

ASF GitHub Bot commented on TAJO-1900:
--------------------------------------

GitHub user jihoonson opened a pull request:

    https://github.com/apache/tajo/pull/792

    TAJO-1900: When a record column and its child column are retrieved together, the record column might not be inferred as record type properly

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jihoonson/tajo-2 TAJO-1900

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tajo/pull/792.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #792
    
----
commit 5217e827ce45ac7b68c3f851835d45e865d20d2d
Author: Jihoon Son <ji...@apache.org>
Date:   2015-09-29T13:08:45Z

    TAJO-1900

----


> 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
>
> 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)