[
https://issues.apache.org/jira/browse/BEAM-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169784#comment-16169784
]
Reza ardeshir rokni commented on BEAM-2771:
-------------------------------------------
it would be useful to be able to set a Configuration object for a value
provider . For example in this fork:
https://github.com/rezarokni/beam/blob/beam-2871/examples/java8/src/main/java/org/apache/beam/examples/advanced/subprocess/ExampleEchoPipeline.java
There are a set of configurations that need to be passed to the DoFn, currently
these are 'copied' from the options into a configuration object which is
serlizable and sent to the DoFn classes in the constructor. Ideally would like
to be able to just have a multi property object be able to be directly accessed
directly from the DoFn and avoid the need to create a new configuration object..
> Allow using side inputs as ValueProviders
> -----------------------------------------
>
> Key: BEAM-2771
> URL: https://issues.apache.org/jira/browse/BEAM-2771
> Project: Beam
> Issue Type: New Feature
> Components: sdk-java-core, sdk-py
> Reporter: Luke Cwik
> Priority: Minor
>
> Allow dynamically computed information in a pipeline which is materialized as
> a side input to be used in the same places as ValueProviders.
> This could solve the problem mentioned in
> [https://stackoverflow.com/questions/45649244/google-cloud-dataflow-apache-beam-can-i-use-sideinputs-with-textio-write]
> if TextSink supported ValueProviders for headers/footers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
