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

Ability to implement on GCP with cloud storage interoperability #41

Open
rajatha-ravish opened this issue Jul 18, 2021 · 5 comments
Open
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@rajatha-ravish
Copy link

No description provided.

@darrenhaken
Copy link

Any ETA on this? we're databricks customers who'd love to use this on GCS/GCP

@rtyler rtyler added the enhancement New feature or request label Apr 4, 2023
@rtyler
Copy link
Member

rtyler commented Apr 4, 2023

@darrenhaken this will unfortunately sit in the issues list until somebody steps up to add GCP support similar to #136 which was recently contributed for Azure support

@mightyshazam
Copy link
Collaborator

@rtyler @darrenhaken With #136 merged, it may be as simple as adding gcs to the features. Then, according to the object store code, users just need to change there uri to gs:// instead of an s3 or azure prefix. It will require testing, but it may be an easy lift.

@rtyler rtyler added the good first issue Good for newcomers label May 19, 2023
@rtyler
Copy link
Member

rtyler commented Jan 9, 2024

One of the things that I recently learned is that GCS supports S3 compatibility through their "Interoperability" feature, so it would technically be possible to just configure kafka-delta-ingest using the S3-compatible APIs for GCS.

@geoHeil
Copy link

geoHeil commented Jan 15, 2024

Is a simple repoint of the S3 URI using AWS_ENDPOINT_URL enough for this change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

5 participants