beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-59) Switch from IOChannelFactory to FileSystems
Date Sun, 30 Apr 2017 17:49:04 GMT


ASF GitHub Bot commented on BEAM-59:

GitHub user dhalperi opened a pull request:

    [BEAM-59] DataflowRunner: Sink is always a FileBasedSink now


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

    $ git pull dataflow-runner-minor

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2791
commit 84713fd62ef9935fa4cf882da0f0302f387b39b2
Author: Dan Halperin <>
Date:   2017-04-30T17:47:37Z

    [BEAM-59] DataflowRunner: Sink is always a FileBasedSink now


> Switch from IOChannelFactory to FileSystems
> -------------------------------------------
>                 Key: BEAM-59
>                 URL:
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-core, sdk-java-gcp
>            Reporter: Daniel Halperin
>            Assignee: Daniel Halperin
>             Fix For: First stable release
> Right now, FileBasedSource and FileBasedSink communication is mediated by IOChannelFactory.
There are a number of issues:
> * Global configuration -- e.g., all 'gs://' URIs use the same credentials. This should
be per-source/per-sink/etc.
> * Supported APIs -- currently IOChannelFactory is in the "non-public API" util package
and subject to change. We need users to be able to add new backends ('s3://', 'hdfs://', etc.)
directly, without fear that they will be broken.
> * Per-backend features: e.g., creating buckets in GCS/s3, setting expiration time, etc.
> Updates:
> Design docs posted on dev@ list:
> Part 1: IOChannelFactory Redesign: 
> Part 2: Configurable BeamFileSystem:

This message was sent by Atlassian JIRA

View raw message