Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-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 EBB6118F88 for ; Fri, 23 Oct 2015 00:13:27 +0000 (UTC) Received: (qmail 10072 invoked by uid 500); 23 Oct 2015 00:13:27 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 10027 invoked by uid 500); 23 Oct 2015 00:13:27 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 10012 invoked by uid 99); 23 Oct 2015 00:13:27 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Oct 2015 00:13:27 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B1FFF2C033A for ; Fri, 23 Oct 2015 00:13:27 +0000 (UTC) Date: Fri, 23 Oct 2015 00:13:27 +0000 (UTC) From: "Parth Chandra (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DRILL-2868) Drill returning incorrect data when we have fields missing in some of the files 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/DRILL-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Chandra updated DRILL-2868: --------------------------------- Assignee: (was: Chris Westin) > Drill returning incorrect data when we have fields missing in some of the files > ------------------------------------------------------------------------------- > > Key: DRILL-2868 > URL: https://issues.apache.org/jira/browse/DRILL-2868 > Project: Apache Drill > Issue Type: Bug > Components: Execution - Relational Operators, Storage - JSON, Storage - Parquet > Reporter: Rahul Challapalli > Priority: Critical > Fix For: Future > > > git.commit.id.abbrev=5cd36c5 > Data File1 : a.json > {code} > { "c1" : 1, "m1" : {"m2" : {"m3" : {"c2" : 5} } } } > { "c1" : 2, "m1" : {"m2" : {"m3" : {"c2" : 6} } } } > { "c1" : 3, "m1" : {"m2" : {"c2" : 5} } } > {code} > Data File2 : b.json > {code} > { "c1" : 3, "m1" : {"m2" : {"c2" : 5} } } > { "c1" : 3, "m1" : {"m2" : {"c2" : 5} } } > { "c1" : 3, "m1" : {"m2" : {"c2" : 5} } } > {code} > Data File3 : c.json > {code} > { "c1" : 3, "m1" : {"m2" : {"c2" : 5} } } > { "c1" : 3, "m1" : {"m2" : {"c2" : 5} } } > { "c1" : 3, "m1" : {"m2" : {"c2" : 5} } } > {code} > The below query reports incorrect data : > {code} > select t.m1.m2.m3 from `delme_repro` as `t`; > +------------+ > | EXPR$0 | > +------------+ > | null | > | null | > | null | > | null | > | null | > | null | > | null | > | null | > | null | > +------------+ > 9 rows selected (0.139 seconds) > {code} > However if I run the same query on the specific file, I get the correct output > {code} > select t.m1.m2.m3 from `delme_repro/a.json` as `t`; > +------------+ > | EXPR$0 | > +------------+ > | {"c2":5} | > | {"c2":6} | > | {} | > +------------+ > 3 rows selected (0.113 seconds) > {code} > It looks like the file size plays a part in deciding the order in which Drill reads the files. But there could be more to this than just the order because when I made sure that 'b.json' and 'c.json' only had one records, drill correctly reported the data. > Let me know if you have any questions -- This message was sent by Atlassian JIRA (v6.3.4#6332)