You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Jihoon Son (JIRA)" <ji...@apache.org> on 2015/09/29 15:08:04 UTC
[jira] [Created] (TAJO-1900) When a record column and its child
column are retrieved together, the record column might not be inferred as
record type properly
Jihoon Son created TAJO-1900:
--------------------------------
Summary: 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)