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

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

GitHub user hsuanyi opened a pull request:

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

    DRILL-4180: When clear() is called on BitVector, ensure valueCount is…

    … set to zero

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

    $ git pull https://github.com/hsuanyi/incubator-drill DRILL-4180

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

    https://github.com/apache/drill/pull/296.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 #296
    
----
commit 539cbba564db8542f72eb353f139c4d3d134b7cc
Author: Hsuan-Yi Chu <[email protected]>
Date:   2015-12-08T23:57:39Z

    DRILL-4180: When clear() is called on BitVector, ensure valueCount is set 
to zero

----


> IllegalArgumentException while reading JSON files
> -------------------------------------------------
>
>                 Key: DRILL-4180
>                 URL: https://issues.apache.org/jira/browse/DRILL-4180
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - JSON
>            Reporter: Sean Hsuan-Yi Chu
>            Assignee: Sean Hsuan-Yi Chu
>             Fix For: 1.5.0
>
>         Attachments: a.json, b.json
>
>
> First of all, this issue can be reproduced when drill runs on distributed 
> mode.
> We have two json files in distributed file system. The type for the column is 
> MAP and there is not schema change on the top level. However, in the one 
> layer deeper in this column, the first file has one NullableBit column, which 
> does not appear in the second file. 
> The issue can be reproduced by the files in the attachment and this query :
> {code}
> select jsonFieldMapLevel1_aaa from directory
> {code}



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

Reply via email to