🐞 Destination databricks: fix destination config #12299
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
tuliren
commented
Apr 23, 2022
tuliren
commented
- The Databricks destination config was broken 🎉 GCS destination: use serialized buffer; compress csv & jsonl #11686. The integration test fails because the S3 credentials are not correctly passed into the destination config. This PR fixes it.
- No Databricks version has been published since the bug. So this does not affect any production users.
|
/test connector=connectors/destination-databricks
|
suhomud
pushed a commit
that referenced
this pull request
May 23, 2022
* Fix databricks dest config * Add private constructor for constant class
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.