You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2017/10/03 18:48:00 UTC
[jira] [Updated] (BEAM-2958) Expose a top level user agent
PipelineOption which can be communicated to external services
[ https://issues.apache.org/jira/browse/BEAM-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luke Cwik updated BEAM-2958:
----------------------------
Component/s: sdk-py-core
> Expose a top level user agent PipelineOption which can be communicated to external services
> -------------------------------------------------------------------------------------------
>
> Key: BEAM-2958
> URL: https://issues.apache.org/jira/browse/BEAM-2958
> Project: Beam
> Issue Type: Improvement
> Components: runner-apex, runner-dataflow, runner-direct, runner-flink, runner-gearpump, runner-jstorm, runner-mapreduce, runner-spark, runner-tez, sdk-java-core, sdk-java-gcp, sdk-py-core
> Reporter: Luke Cwik
> Assignee: Daniel Oliveira
> Priority: Minor
>
> This concept is used by Bigtable and Dataflow service to specify what version of the SDK is being used and is currently available through ReleaseInfo as a static property.
> The Dataflow distribution attempts to override this but is unable to propagate this user agent to dependent modules cleanly. Having dependent modules get the user agent from a PipelineOption would make it possible for a runner to modify the user agent during execution to be able to identify its flavor.
> It seems likely that Flink/Spark/... would like to modify the user agent as well for the same purpose.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)