[
https://issues.apache.org/jira/browse/BEAM-14403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531986#comment-17531986
]
Ahmet Altay commented on BEAM-14403:
------------------------------------
[~kenn][~robertwb]
Is there something we could do to prevent an issue like this in the future? In
an ideal world SDK could leave these types of choices to the service. And if
SDK has to make a choice it could distinguish between options SDK set vs the
options a user explicitly set. We could check for such things in code review,
but beyond that is there a way for us to check if SDK is setting options that
is more than necessary in a more automated way. (I might be overthinking this
and this might be a single example.)
> Allow Prime to be used with Legacy workers
> ------------------------------------------
>
> Key: BEAM-14403
> URL: https://issues.apache.org/jira/browse/BEAM-14403
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Affects Versions: 2.35.0, 2.36.0, 2.37.0, 2.38.0
> Reporter: Robert Bradshaw
> Assignee: Robert Bradshaw
> Priority: P1
> Fix For: 2.39.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> [https://github.com/apache/beam/blob/v2.37.0/runners/google-cloud-dataflow-java/src/main/java/org/apache/beam/runners/dataflow/DataflowRunner.java#L2315]
> assumes that enable_prime forces UW. This decision should be left up to the
> service.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
