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

ASF GitHub Bot commented on ORC-367:
------------------------------------

GitHub user omalley opened a pull request:

    https://github.com/apache/orc/pull/272

    ORC-367: Fix incorrect reads of boolean columns after a seek.

    Fix #272
    
    Signed-off-by: Owen O'Malley <[email protected]>

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

    $ git pull https://github.com/omalley/orc orc-367

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

    https://github.com/apache/orc/pull/272.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 #272
    
----
commit b0504f55e4a68de0c73b89ab5bccb2a673efe9b4
Author: Owen O'Malley <omalley@...>
Date:   2018-05-22T21:43:06Z

    ORC-367: Fix incorrect reads of boolean columns after a seek.
    
    Fix #272
    
    Signed-off-by: Owen O'Malley <[email protected]>

----


> Incorrect reading of boolean value with latest version
> ------------------------------------------------------
>
>                 Key: ORC-367
>                 URL: https://issues.apache.org/jira/browse/ORC-367
>             Project: ORC
>          Issue Type: Test
>            Reporter: Jesus Camacho Rodriguez
>            Priority: Major
>
> HIVE-19465 is the issue to upgrade Hive to latest 1.5.0.
> While upgrading, there are two tests that fail:
> {code}
> org.apache.hadoop.hive.ql.io.orc.TestOrcFile.testSeek
> org.apache.hadoop.hive.ql.io.orc.TestOrcFile.testZeroCopySeek
> {code}
> Problem seems to be at reading time for boolean type (value always false). 
> Reverting ORC-187 (which was pushed in 1.5.0) from release fixes those tests, 
> hence I am wondering whether this is a bug introduced by that patch or maybe 
> I need to change something in Hive side that I am missing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to