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 Wed, 26 Apr 2017 04:51:04 GMT


ASF GitHub Bot commented on BEAM-59:

GitHub user dhalperi opened a pull request:

    [BEAM-59] Some low hanging fruit in FileSystems/LocalFileSystem/LocalResource

    Pulling out from ongoing work to convert `FileBasedSink`.
    R: @ssisk or @peihe or @reuvenlax as available

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

    $ git pull low-hanging-fruit

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 #2697
commit b7b38379f34b50496d962b8ef6badb4181073a53
Author: Dan Halperin <>
Date:   2017-04-26T03:48:52Z

    LocalResourceId: make toString end in '/' for directories

commit aea01295a5b71b159870126c17d0a8878d8d16bc
Author: Dan Halperin <>
Date:   2017-04-26T03:48:23Z

    FileSystems: make tolerant of and more efficient for empty lists

commit 4e6c31d99ba87682431e6ab658aae8a85e968877
Author: Dan Halperin <>
Date:   2017-04-26T03:48:02Z

    LocalFileSystem: create parent directories if needed
    And improve testing to confirm.


> 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