You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/18 17:07:10 UTC
[jira] [Commented] (BEAM-4378) Update javadoc for set/getRegion in
DataflowPipelineOptions.
[ https://issues.apache.org/jira/browse/BEAM-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179764#comment-17179764 ]
Beam JIRA Bot commented on BEAM-4378:
-------------------------------------
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.
> Update javadoc for set/getRegion in DataflowPipelineOptions.
> ------------------------------------------------------------
>
> Key: BEAM-4378
> URL: https://issues.apache.org/jira/browse/BEAM-4378
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: David Yan
> Priority: P2
> Labels: stale-P2
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Dataflow now supports the region flag. We should update the javadoc here:
> https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/src/main/java/org/apache/beam/runners/dataflow/options/DataflowPipelineOptions.java#L107
--
This message was sent by Atlassian Jira
(v8.3.4#803005)