Change duckdb version to fix backward compatibility issue in Superset #106
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
|
yes, the fix is to update the pin to 0.8.1. Not sure why so many lines are changing though? |
|
Probably a yml linting issue with whatever you are using to format. Ok as long as the test passes, should merge w/o issue. |
matsonj
added a commit
that referenced
this pull request
Apr 6, 2024
Change duckdb version to fix backward compatibility issue in Superset
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.
Issue
DuckDBhas backward compatibility issue. The version inmeltano.ymlforSupersetanddbt-duckdbdon't match.Change
duckdbversion inSupersetfromduckdb==0.7.1toduckdb==0.8.1