beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dhalperi <...@git.apache.org>
Subject [GitHub] incubator-beam pull request #583: [BEAM-422] AvroSource: use a 64K buffer si...
Date Sat, 02 Jul 2016 09:23:01 GMT
GitHub user dhalperi opened a pull request:

    https://github.com/apache/incubator-beam/pull/583

    [BEAM-422] AvroSource: use a 64K buffer size for Snappy codec

    commons-compress defaults to a 32K buffer size for Snappy.
    
    However, Avro uses xerial.snappy to write, which has a 64K buffer size.
    When the buffer size is too small, decoding data from Snappy can cause
    an EOF exception rather than finishing data.
    
    This fixes BEAM-422.

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

    $ git pull https://github.com/dhalperi/incubator-beam avro-source-fix

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

    https://github.com/apache/incubator-beam/pull/583.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 #583
    
----
commit 7bbec5108aa64e97a4e7a2cda54882a369f94ebd
Author: Dan Halperin <dhalperi@google.com>
Date:   2016-07-02T09:18:07Z

    AvroSource: use a 64K buffer size for Snappy codec
    
    commons-compress defaults to a 32K buffer size for Snappy.
    
    However, Avro uses xerial.snappy to write, which has a 64K buffer size.
    When the buffer size is too small, decoding data from Snappy can cause
    an EOF exception rather than finishing data.
    
    This fixes BEAM-422.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message