drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-4503) Schema change exception even with all_text_mode enabled
Date Sun, 13 Mar 2016 23:27:33 GMT

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

ASF GitHub Bot commented on DRILL-4503:
---------------------------------------

GitHub user amansinha100 opened a pull request:

    https://github.com/apache/drill/pull/428

    DRILL-4503: Write nulls as varchar when all_text_mode is enabled.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/amansinha100/incubator-drill DRILL-4503

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/428.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #428
    
----
commit 882dc2dc66383d41867f18626443b6e2e81c8ea3
Author: Aman Sinha <asinha@maprtech.com>
Date:   2016-03-13T22:42:57Z

    DRILL-4503: Write nulls as varchar when all_text_mode is enabled.

----


> Schema change exception even with all_text_mode enabled
> -------------------------------------------------------
>
>                 Key: DRILL-4503
>                 URL: https://issues.apache.org/jira/browse/DRILL-4503
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - JSON
>    Affects Versions: 1.6.0
>            Reporter: Aman Sinha
>            Assignee: Aman Sinha
>              Labels: 1.7.0
>         Attachments: mostlynulls_1.json
>
>
> Both HashAggregate and StreamingAggregate encounter schema change error whey querying
a JSON file with non-null values for column 'a' and many null values for column 'c'.
> This occurs even when all_text_mode is enabled, which seems counterintuitive since once
all_text_mode is enabled, everything (including nulls) should be treated as varchar and one
would expect no schema change errors.  
> Here are some example queries that encounter this error: 
> {noformat}
> 0: jdbc:drill:zk=local> select a, c from dfs.`mostlynulls_1.json` group by a, c;
> Error: UNSUPPORTED_OPERATION ERROR: Hash aggregate does not support schema changes
> 0: jdbc:drill:zk=local> alter session set `store.json.all_text_mode` = true;
> +-------+------------------------------------+
> |  ok   |              summary               |
> +-------+------------------------------------+
> | true  | store.json.all_text_mode updated.  |
> +-------+------------------------------------+
> 1 row selected (0.15 seconds)
> 0: jdbc:drill:zk=local> select a, c from dfs.`mostlynulls_1.json` group by a, c;
> Error: UNSUPPORTED_OPERATION ERROR: Hash aggregate does not support schema changes
> 0: jdbc:drill:zk=local> select min(a), min(c) from dfs.`mostlynulls_1.json`;
> Error: UNSUPPORTED_OPERATION ERROR: Streaming aggregate does not support schema changes
> {noformat}



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

Mime
View raw message