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

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

GitHub user omalley opened a pull request:

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

    ORC-24. C++ reader for direct string encodings occasionally skips bytes.

    ORC-24. C++ reader for direct string encodings occasionally skips bytes.

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

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

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

    https://github.com/apache/orc/pull/6.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 #6
    
----
commit 4ccf6573a1d9af502c103821ca3df384c3964dd8
Author: Owen O'Malley <[email protected]>
Date:   2015-08-05T04:58:28Z

    ORC-24. C++ reader for direct string encodings occasionally skips bytes.

----


> C++ reader for direct string encodings occasionally skips bytes 
> ----------------------------------------------------------------
>
>                 Key: ORC-24
>                 URL: https://issues.apache.org/jira/browse/ORC-24
>             Project: Orc
>          Issue Type: Bug
>          Components: C++
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 1.0.0
>
>         Attachments: ORC-24.patch
>
>
> The ORC C++ direct string column reader can occasionally skip bytes in the 
> blob stream.
> The necessary conditions are:
> * The column is a string column and is directly encoded.
> * The blob stream for the row batch crosses a compression block boundary.
> * There is a null value toward the end of the block boundary.
> * The value in the length value of the null value crosses the block boundary, 
> but the length value of the following value does not.



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

Reply via email to