[
https://issues.apache.org/jira/browse/BEAM-10700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494734#comment-17494734
]
Beam JIRA Bot commented on BEAM-10700:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> "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: P2
> Labels: documentation, stale-assigned
>
> 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)
