[
https://issues.apache.org/jira/browse/BEAM-7531?focusedWorklogId=260612&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-260612
]
ASF GitHub Bot logged work on BEAM-7531:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jun/19 18:18
Start Date: 14/Jun/19 18:18
Worklog Time Spent: 10m
Work Description: udim commented on issue #8830: [BEAM-7531] Remove and
disallow KMS key setting
URL: https://github.com/apache/beam/pull/8830#issuecomment-502212676
Thanks @lukecwik !
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 260612)
Time Spent: 0.5h (was: 20m)
> 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-python-gcp
> Reporter: Udi Meiri
> Assignee: Udi Meiri
> Priority: Major
> 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
(v7.6.3#76005)
