Return-Path: 
 <issues-return-26602-apmail-drill-issues-archive=drill.apache.org@drill.apache.org>
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 5A92618468
	for <apmail-drill-issues-archive@minotaur.apache.org>;
 Wed, 18 Nov 2015 18:42:11 +0000 (UTC)
Received: (qmail 5663 invoked by uid 500); 18 Nov 2015 18:42:11 -0000
Delivered-To: apmail-drill-issues-archive@drill.apache.org
Received: (qmail 5607 invoked by uid 500); 18 Nov 2015 18:42:11 -0000
Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@drill.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@drill.apache.org>
List-Post: <mailto:issues@drill.apache.org>
List-Id: <issues.drill.apache.org>
Reply-To: dev@drill.apache.org
Delivered-To: mailing list issues@drill.apache.org
Received: (qmail 5586 invoked by uid 99); 18 Nov 2015 18:42:11 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Nov 2015 18:42:11 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 20A712C1F5F
	for <issues@drill.apache.org>; Wed, 18 Nov 2015 18:42:11 +0000 (UTC)
Date: Wed, 18 Nov 2015 18:42:11 +0000 (UTC)
From: "Sudheesh Katkam (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12913684.1447764225000.109687.1447872131130@Atlassian.JIRA>
In-Reply-To: <JIRA.12913684.1447764225000@Atlassian.JIRA>
References: <JIRA.12913684.1447764225000@Atlassian.JIRA>
 <JIRA.12913684.1447764225456@arcas>
Subject: [jira] [Commented] (DRILL-4102) Only one row found in a JSON
 document that contains multiple items.
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-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011627#comment-15011627 ] 

Sudheesh Katkam commented on DRILL-4102:
----------------------------------------

This is actually a duplicate of DRILL-2583, allowing `KVGEN(*)`  resolves the issue you are facing.

> Only one row found in a JSON document that contains multiple items.
> -------------------------------------------------------------------
>
>                 Key: DRILL-4102
>                 URL: https://issues.apache.org/jira/browse/DRILL-4102
>             Project: Apache Drill
>          Issue Type: Bug
>         Environment: OS X, Drill embedded, v1.1.0 installed via HomeBrew
>            Reporter: aditya menon
>
> I tried to analyse a JSON file that had the following (sample) structure:
> {code:json}
> {
>     "Key1": {
>       "htmltags": "<htmltag attr1='bravo' /><htmltag attr2='delta' /><htmltag attr3='charlie' />"
>     },
>     "Key2": {
>       "htmltags": "<htmltag attr1='kilo' /><htmltag attr2='lima' /><htmltag attr3='mike' />"
>     },
>     "Key3": {
>       "htmltags": "<htmltag attr1='november' /><htmltag attr2='foxtrot' /><htmltag attr3='sierra' />"
>     }
> }
> {code}
> (Apologies for the obfuscation, I am unable to publish the original dataset. But the structure is exactly the same. Note especially how the keys and other data points *differ* in some places, and remain identical in others.)
> When I run a {code:sql}SELECT * FROM DataFile.json{code} what I get is a single row listed under three columns: {code:html}"<htmltag attr1='bravo' /><htmltag attr2='delta' /><htmltag attr3='charlie' />"{code} [i.e., only the entry `Key1.htmltags`] .
> Ideally, I should see three rows, each with entries from Key1..Key3, listed under the correct respective column.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)