Return-Path: X-Original-To: apmail-tajo-issues-archive@minotaur.apache.org Delivered-To: apmail-tajo-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7A2BF188CC for ; Thu, 8 Oct 2015 08:50:29 +0000 (UTC) Received: (qmail 70425 invoked by uid 500); 8 Oct 2015 08:50:29 -0000 Delivered-To: apmail-tajo-issues-archive@tajo.apache.org Received: (qmail 70388 invoked by uid 500); 8 Oct 2015 08:50:29 -0000 Mailing-List: contact issues-help@tajo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tajo.apache.org Delivered-To: mailing list issues@tajo.apache.org Received: (qmail 70379 invoked by uid 99); 8 Oct 2015 08:50:29 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2015 08:50:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id F10C2180E21 for ; Thu, 8 Oct 2015 08:50:28 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.23 X-Spam-Level: X-Spam-Status: No, score=-3.23 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id nOdlgkWpn1SH for ; Thu, 8 Oct 2015 08:50:28 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id 5B8C1206E8 for ; Thu, 8 Oct 2015 08:50:27 +0000 (UTC) Received: (qmail 70364 invoked by uid 99); 8 Oct 2015 08:50:26 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2015 08:50:26 +0000 Date: Thu, 8 Oct 2015 08:50:26 +0000 (UTC) From: "Jihoon Son (JIRA)" To: issues@tajo.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (TAJO-1900) When a record column and its child column are retrieved together, the record column might not be inferred as record type properly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/TAJO-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jihoon Son updated TAJO-1900: ----------------------------- Attachment: TAJO-1900.patch > 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 > 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)