You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Marcus Truscello (Jira)" <ji...@apache.org> on 2020/08/13 00:51:00 UTC
[jira] [Updated] (BEAM-10700) "Retroactively logging runtime
parameters" guide simply doesn't work.
[ https://issues.apache.org/jira/browse/BEAM-10700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Truscello updated BEAM-10700:
------------------------------------
Description:
The Java version of the "[Pipeline option patterns|https://beam.apache.org/documentation/patterns/pipeline-options/]" article simply does not work.
When creating a PipelineOptions inside of a DoFn, all get methods that return ValueProvider<T> will return null instead. The closest working example I could find was from Google's guide on [ValueProviders in Dataflow templates|#using-valueprovider-in-your-functions]]. The pattern involves passing the ValueProvider into a DoFn class's constructor, storing it, then later accessing it at runtime.
was:
The Java version of the "[Pipeline option patterns|[https://beam.apache.org/documentation/patterns/pipeline-options/]]" article simply does not work.
When creating a PipelineOptions inside of a DoFn, all get methods that return ValueProvider<T> will return null instead. The closest working example I could find was from Google's guide on [ValueProviders in Dataflow templates|[https://cloud.google.com/dataflow/docs/guides/templates/creating-templates#using-valueprovider-in-your-functions]]. The pattern involves passing the ValueProvider into a DoFn class's constructor, storing it, then later accessing it at runtime.
> "Retroactively logging runtime parameters" guide simply doesn't work.
> ---------------------------------------------------------------------
>
> Key: BEAM-10700
> URL: https://issues.apache.org/jira/browse/BEAM-10700
> Project: Beam
> Issue Type: Bug
> Components: website
> Reporter: Marcus Truscello
> Priority: P3
> Labels: documentation
>
> The Java version of the "[Pipeline option patterns|https://beam.apache.org/documentation/patterns/pipeline-options/]" article simply does not work.
> When creating a PipelineOptions inside of a DoFn, all get methods that return ValueProvider<T> will return null instead. The closest working example I could find was from Google's guide on [ValueProviders in Dataflow templates|#using-valueprovider-in-your-functions]]. The pattern involves passing the ValueProvider into a DoFn class's constructor, storing it, then later accessing it at runtime.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)