[
https://issues.apache.org/jira/browse/BEAM-10700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528922#comment-17528922
]
Beam JIRA Bot commented on BEAM-10700:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> "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: P2
> Labels: documentation, stale-P2
>
> 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.7#820007)
