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

Apply buffering changes to Databricks Destination #11424

Open
ChristopheDuong opened this issue Mar 25, 2022 · 2 comments
Open

Apply buffering changes to Databricks Destination #11424

ChristopheDuong opened this issue Mar 25, 2022 · 2 comments
Labels
area/connectors Connector related issues area/reliability autoteam frozen Not being actively worked on team/destinations Destinations team's backlog type/enhancement New feature or request

Comments

@ChristopheDuong
Copy link
Contributor

ChristopheDuong commented Mar 25, 2022

Tell us about the problem you're trying to solve

As part of #10260, refactor destination-databricks to use serialized buffering strategy.

@tuliren
Copy link
Contributor

tuliren commented May 3, 2022

Databricks is going to roll out their internal staging solution within the month. Ideally, we should wait until their solution is ready, and do the two changes together:

  • Migrate our S3 staging loading method to use the serialized buffer.
  • Add a new loading method to use Databricks' internal staging.

If we are going to do them together, please do not assign this to GL. We should work on this, because there will be some exploratory work with adopting Databricks' solution.

@grishick grishick added the team/destinations Destinations team's backlog label Sep 27, 2022
@martindlarsson
Copy link

Any news on the Databricks solution? Is there a ticket for this I can follow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues area/reliability autoteam frozen Not being actively worked on team/destinations Destinations team's backlog type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants