[
https://issues.apache.org/jira/browse/DRILL-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neeraja updated DRILL-2033:
---------------------------
Description:
A scalar/simple field turning to complex field is a very common scenario in
many JSON documents.
For ex: An integer turning into an array of integers , a string turning into a
map of multiple strings .
Drill currently already provides ability to query the scalar data with datatype
changes by turning all text mode to true.
This should be expanded it to support querying the scalar-complex type changes
as well. This gives power for the users to look at the data without
fixing/modifying JSON upfront.
Here is a quick example from a public dataset.
{
"data": {
"games": {
"game": [
{
"home_runs": {
"player": {
"first": "Jason"
}
}
},
{
"home_runs": {
"player": [
{
"first": "Kosuke"
},
{
"first": "Alfonso"
},
{
"first": "Jeff"
},
{
"first": "Brandon"
}
]
}
}
]
}
}
}
was:
A scalar/simple field turning to complex field is a very common scenario in
many JSON documents.
For ex: An integer turning into an array of integers , a string turning into a
map of multiple strings .
Drill currently already provides ability to query the scalar data with datatype
changes by turning all text mode to true.
This should be expanded it to support querying the scalar-complex type changes
as well. This gives power for the users to look at the data without
fixing/modifying JSON upfront.
> JSON 'All Text mode' should support schema change from scalar to complex types
> ------------------------------------------------------------------------------
>
> Key: DRILL-2033
> URL: https://issues.apache.org/jira/browse/DRILL-2033
> Project: Apache Drill
> Issue Type: Improvement
> Reporter: Neeraja
>
> A scalar/simple field turning to complex field is a very common scenario in
> many JSON documents.
> For ex: An integer turning into an array of integers , a string turning into
> a map of multiple strings .
> Drill currently already provides ability to query the scalar data with
> datatype changes by turning all text mode to true.
> This should be expanded it to support querying the scalar-complex type
> changes as well. This gives power for the users to look at the data without
> fixing/modifying JSON upfront.
> Here is a quick example from a public dataset.
> {
> "data": {
> "games": {
> "game": [
> {
> "home_runs": {
> "player": {
> "first": "Jason"
> }
> }
> },
> {
> "home_runs": {
> "player": [
> {
> "first": "Kosuke"
> },
> {
> "first": "Alfonso"
> },
> {
> "first": "Jeff"
> },
> {
> "first": "Brandon"
> }
> ]
> }
> }
> ]
> }
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
