You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by reuvenlax <gi...@git.apache.org> on 2017/07/11 16:20:36 UTC

[GitHub] beam pull request #3541: [BEAM-92] Support value-dependent files in AvroIO.

GitHub user reuvenlax opened a pull request:

    https://github.com/apache/beam/pull/3541

    [BEAM-92] Support value-dependent files in AvroIO.

    Extends the FileBasedSink dynamic filename support to AvroIO. In addition to allowing dynamic destinations, we also allow per-destination AVRO schemas, metadata, and codec. Allow the DynamicDestinations class to access side inputs if wanted.
    
    Note: Currently AvroIOTest.testDynamicDestinations fails on the direct runner. This appears to be due to bugs in the proto translation support in Beam. Working with @kennknowles to debug and fix this.
    
    R: @jkff 

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

    $ git pull https://github.com/reuvenlax/incubator-beam dynamic_avro_write

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

    https://github.com/apache/beam/pull/3541.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 #3541
    
----
commit a61076e1561ff9109f315e67c19ce7466901e3e0
Author: Reuven Lax <re...@google.com>
Date:   2017-07-07T03:22:25Z

    Support DynamicDestinations in AvroIO.

----


---
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.
---

[GitHub] beam pull request #3541: [BEAM-92] Support value-dependent files in AvroIO.

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/beam/pull/3541


---
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.
---