[ 
https://issues.apache.org/jira/browse/DRILL-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Jurcau updated DRILL-5111:
---------------------------------
    Description: 
When querying JSON documents via the ODBC driver on Windows, the contents of 
columns which contain a JSON array is always trimmed to 64K characters. 

Example entry in the JSON document:
{
"id": 1,
"items": [
   {"type": "item"},
   // thousands of similar entries
]}

On querying, the column {{items}} returns the array as a JSON string that never 
exceeds 64K characters, even if the amount should be in the range of a few 
megabytes for the data in question.

  was:
When querying JSON documents via the ODBC driver on Windows, the contents of 
columns which contain a JSON array is always trimmed to 64K characters. 

Example entry in the JSON document:
{
"id": 1,
"items": [
   {"type": "item"},
   // thousands of similar entries
]}

On query, the column {{items}} returns the array as a JSON string that never 
exceeds 64K characters, even if the amount should be in the range of a few 
megabytes for the data in question.


> Nested array column trimmed on 64k characters when queried via ODBC
> -------------------------------------------------------------------
>
>                 Key: DRILL-5111
>                 URL: https://issues.apache.org/jira/browse/DRILL-5111
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - ODBC
>    Affects Versions: 1.8.0
>            Reporter: Daniel Jurcau
>            Priority: Critical
>
> When querying JSON documents via the ODBC driver on Windows, the contents of 
> columns which contain a JSON array is always trimmed to 64K characters. 
> Example entry in the JSON document:
> {
> "id": 1,
> "items": [
>    {"type": "item"},
>    // thousands of similar entries
> ]}
> On querying, the column {{items}} returns the array as a JSON string that 
> never exceeds 64K characters, even if the amount should be in the range of a 
> few megabytes for the data in question.



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

Reply via email to