[
https://issues.apache.org/jira/browse/BEAM-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552303#comment-15552303
]
Daniel Halperin commented on BEAM-59:
-------------------------------------
I think there are two separable tasks.
1. Completely rethink the IOChannelFactory-type code. This is a large task and
requires community discussion. [This JIRA]
2. Implement an HDFS-compatible IOChannelFactory using the existing APIs,
without changing the design. I think that is shovel-ready and also does not
require a proposal. It's like adding ZIP to TextIO.Read -- just filling in
features without new design.
> 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
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
