Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: requester-pays flag for GCS storage #33300

Open
2 of 17 tasks
kellen opened this issue Dec 5, 2024 · 0 comments
Open
2 of 17 tasks

[Feature Request]: requester-pays flag for GCS storage #33300

kellen opened this issue Dec 5, 2024 · 0 comments

Comments

@kellen
Copy link
Contributor

kellen commented Dec 5, 2024

What would you like to happen?

Add a pipeline option that can toggle opt-in requester-pays functionality for storage requests.

At spotify we have many GCP projects and want to be able to attribute read cost to the requester rather than bucket-owner preferably without toggling requester pays option on each bucket. Beam does not currently support opting-in.

From discussions with @iht it seems like this would require a change to GcsUtil in the java API. We also (rarely) use the python API so would be nice to have symmetrical support there.

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant