You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2016/05/03 22:09:12 UTC
[jira] [Updated] (BEAM-255) Understand and improve performance of
Write/FileBasedSink
[ https://issues.apache.org/jira/browse/BEAM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Halperin updated BEAM-255:
---------------------------------
Description:
The work by [~lcwik] to move TextIO from a Dataflow-specific implementation to a FileBasedSink-based implementation may have caused performance regressions for Dataflow -- which really means it has exposed an opportunity for improvement in the Beam combination of Write/FileBasedSink.
This is a general tracking bug for SDK-side improvements (likely GCP-related).
was:
The work by [~lcwik] to move TextIO from a Dataflow-specific implementation to a FileBasedSink-based implementation may have caused performance regressions -- which really means it has exposed opportunity for improvement in the Beam combination of Write/FileBasedSink.
This is a general tracking bug for SDK-side improvements (likely GCP-related).
> Understand and improve performance of Write/FileBasedSink
> ---------------------------------------------------------
>
> Key: BEAM-255
> URL: https://issues.apache.org/jira/browse/BEAM-255
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-gcp
> Reporter: Daniel Halperin
> Assignee: Daniel Halperin
>
> The work by [~lcwik] to move TextIO from a Dataflow-specific implementation to a FileBasedSink-based implementation may have caused performance regressions for Dataflow -- which really means it has exposed an opportunity for improvement in the Beam combination of Write/FileBasedSink.
> This is a general tracking bug for SDK-side improvements (likely GCP-related).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)