You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/18 18:11:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17478099#comment-17478099 ] 

Kenneth Knowles commented on BEAM-10700:
----------------------------------------

Can you provide some details on what you tried that didn't work? We do have a lot of usage of {{ValueProvider}} so I'm hoping we can fix the docs or help you out getting it to work.

> "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
>            Assignee: David Huntsperger
>            Priority: P1
>              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.20.1#820001)