Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Sun, 1 Mar 2015 20:21:05 +0000 (UTC)
From: "Kristine Hahn (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12770154.1422298840000.47318.1425241265070@Atlassian.JIRA>
In-Reply-To: <JIRA.12770154.1422298840000@Atlassian.JIRA>
References: <JIRA.12770154.1422298840000@Atlassian.JIRA>
 <JIRA.12770154.1422298840289@arcas>
Subject: [jira] [Comment Edited] (DRILL-2071) Better documentation for JSON
 reader all_text_mode option
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristine Hahn edited comment on DRILL-2071 at 3/1/15 8:20 PM:
--------------------------------------------------------------

{quote}
This is only mentioned on the wiki in this page, but does not really describe all of the use cases of the feature.
{quote}
https://docs.google.com/a/maprtech.com/document/d/1jz5jvgFdm7jOldT_ZeY2gH389dKxMiv6fE0LNBJG8EI/ (page 2), Handling Type Differences and the preceding section are ready for review. Does this cover the documentation needs?


was (Author: krishahn):
{quote}
This is only mentioned on the wiki in this page, but does not really describe all of the use cases of the feature.
{quote}
What are all the use cases?

> Better documentation for JSON reader all_text_mode option
> ---------------------------------------------------------
>
>                 Key: DRILL-2071
>                 URL: https://issues.apache.org/jira/browse/DRILL-2071
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Jason Altekruse
>            Assignee: Kristine Hahn
>             Fix For: 0.7.0
>
>
> Currently Drill will fail by default to read JSON files with changes in schema, or with several different data types in a list. These files can however be read if the store.json.all_text_mode option is set to true. This option will read all data from the JSON files as varchar and from here the data can be casted to an appropriate type (or filtered out in the case where a cast to numeric is desired but some of the data in the column is a string or boolean type). This is only mentioned on the wiki in this page, but does not really describe all of the use cases of the feature. https://cwiki.apache.org/confluence/display/DRILL/Analyzing+Yelp+JSON+Data+with+Apache+Drill


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