[
https://issues.apache.org/jira/browse/DRILL-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers updated DRILL-6035:
-------------------------------
Description:
Drill supports JSON as its native data format. However, experience suggests
that Drill may have limitations in the JSON that Drill supports. This ticket
asks to clarify Drill's expected behavior on various kinds of JSON.
Topics to be addressed:
* Relational vs. non-relational structures
* JSON structures used in practice and how they map to Drill
* Support for varying data types
* Support for missing values, especially across files
These topics are complex, hence the request to provide a detailed
specifications that clarifies what Drill does and does not support (or what is
should and should not support.)
As noted below, the "net-net" conclusion for users is to use an ETL tool to
convert JSON to Parquet, then allow Drill to query the Parquet.
was:
Drill supports JSON as its native data format. However, experience suggests
that Drill may have limitations in the JSON that Drill supports. This ticket
asks to clarify Drill's expected behavior on various kinds of JSON.
Topics to be addressed:
* Relational vs. non-relational structures
* JSON structures used in practice and how they map to Drill
* Support for varying data types
* Support for missing values, especially across files
These topics are complex, hence the request to provide a detailed
specifications that clarifies what Drill does and does not support (or what is
should and should not support.)
> Specify Drill's JSON behavior
> -----------------------------
>
> Key: DRILL-6035
> URL: https://issues.apache.org/jira/browse/DRILL-6035
> Project: Apache Drill
> Issue Type: Improvement
> Affects Versions: 1.13.0
> Reporter: Paul Rogers
> Assignee: Pritesh Maker
>
> Drill supports JSON as its native data format. However, experience suggests
> that Drill may have limitations in the JSON that Drill supports. This ticket
> asks to clarify Drill's expected behavior on various kinds of JSON.
> Topics to be addressed:
> * Relational vs. non-relational structures
> * JSON structures used in practice and how they map to Drill
> * Support for varying data types
> * Support for missing values, especially across files
> These topics are complex, hence the request to provide a detailed
> specifications that clarifies what Drill does and does not support (or what
> is should and should not support.)
> As noted below, the "net-net" conclusion for users is to use an ETL tool to
> convert JSON to Parquet, then allow Drill to query the Parquet.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
