adding duckdb, metadata, and some tags #2
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
… right asset group
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.
Not sure if you wanted to merge this, but figured I'd share it bc I used it recently as a demo.
It definitely doesn't work in prod, but added DuckDB to "theoretically" show using DuckDB locally and Snowflake in prod.
Also added more metadata and tags to give it some more pop and wowzers.
It does this weird thing where are two versions of the
forecastingdirectory and__init__.pyfiles, suffixed withcomplete.Take what you want or dismiss this PR completely, but figured I'd share the change in case you were interested in them.