[
https://issues.apache.org/jira/browse/BEAM-7531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udi Meiri resolved BEAM-7531.
-----------------------------
Fix Version/s: Not applicable
Resolution: Fixed
> Don't auto-create GCS buckets with KMS settings
> -----------------------------------------------
>
> Key: BEAM-7531
> URL: https://issues.apache.org/jira/browse/BEAM-7531
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp, io-py-gcp
> Reporter: Udi Meiri
> Assignee: Udi Meiri
> Priority: Major
> Fix For: Not applicable
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> For Dataflow jobs, if a staging/temp path is not provided, a default bucket
> name is generated using the GCP project and job region.
> https://github.com/apache/beam/blob/39dab79b7bd56a47c0f2a02033ab4ca3bd4a67e2/sdks/java/extensions/google-cloud-platform-core/src/main/java/org/apache/beam/sdk/extensions/gcp/options/GcpOptions.java#L319
> We recently added the KMS setting to this bucket creation, but since
> different jobs might use different KMS keys this is unexpected behavior.
> This bug is to remove this KMS setting from default bucket creation, and
> possibly error out when a default bucket is used and KMS settings are
> provided.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
