[
https://issues.apache.org/jira/browse/BEAM-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pei He updated BEAM-59:
-----------------------
Description:
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:
https://docs.google.com/document/d/11TdPyZ9_zmjokhNWM3Id-XJsVG3qel2lhdKTknmZ_7M/edit#
Part 2: Configurable BeamFileSystem:
https://docs.google.com/document/d/1-7vo9nLRsEEzDGnb562PuL4q9mUiq_ZVpCAiyyJw8p8/edit#heading=h.p3gc3colc2cs
was:
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.
> IOChannelFactory rethinking/redesign
> ------------------------------------
>
> Key: BEAM-59
> URL: https://issues.apache.org/jira/browse/BEAM-59
> Project: Beam
> Issue Type: New Feature
> Components: sdk-java-core, sdk-java-gcp
> Reporter: Daniel Halperin
> Assignee: Pei He
>
> 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:
> https://docs.google.com/document/d/11TdPyZ9_zmjokhNWM3Id-XJsVG3qel2lhdKTknmZ_7M/edit#
> Part 2: Configurable BeamFileSystem:
> https://docs.google.com/document/d/1-7vo9nLRsEEzDGnb562PuL4q9mUiq_ZVpCAiyyJw8p8/edit#heading=h.p3gc3colc2cs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
