Upgrade 0.18.0 release plus tests #105
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
jtcohen6
approved these changes
Sep 15, 2020
gshank
approved these changes
Sep 16, 2020
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.
Updated to 0.18.0 and to support dbt-core 0.18.0.
This went through the same treatment as presto.
After doing a
docker-compose up -d,tox -e integration-spark-thriftshould work locally without any other actions.If you have databricks environment variables exported (
DBT_DATABRICKS_HOST_NAME,DBT_DATABRICKS_CLUSTER_NAME,DBT_DATABRICKS_TOKEN) you can also runtox -e integration-spark-databricks.I updated CircleCI to run the thrift tests, we could definitely also set it up with databricks credentials if we were so inclined.