GitHub user jaltekruse opened a pull request:

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

    DRILL-4048: Fix reading required dictionary encoded varbinary data in…

    … parquet files after recent update
    
    Fix was small, this update is a little larger than necessary because I was 
hoping to create
    a unit test by modifying the one I had added in the earlier patch with the 
version upgrade.
    Unfortunately we don't have a good way to generate Parquet files with 
required columns from
    unit tests right now. So I just added a smaller subset of the binary file 
that was posted on
    the JIRA issue. The refactoring of the earlier test was still useful for 
readability,
    so I kept it in.

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

    $ git pull https://github.com/jaltekruse/incubator-drill DRILL-4048

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

    https://github.com/apache/drill/pull/247.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 #247
    
----
commit e344a1fdf08192d6f3d18b09c1e7c3bcc478f518
Author: Jason Altekruse <[email protected]>
Date:   2015-11-07T03:24:28Z

    DRILL-4048: Fix reading required dictionary encoded varbinary data in 
parquet files after recent update
    
    Fix was small, this update is a little larger than necessary because I was 
hoping to create
    a unit test by modifying the one I had added in the earlier patch with the 
version upgrade.
    Unfortunately we don't have a good way to generate Parquet files with 
required columns from
    unit tests right now. So I just added a smaller subset of the binary file 
that was posted on
    the JIRA issue. The refactoring of the earlier test was still useful for 
readability,
    so I kept it in.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to