-
Notifications
You must be signed in to change notification settings - Fork 15
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
Update sling assets #92
Conversation
Your pull request at commit
|
Your pull request at commit
|
e01c16d
to
50569fd
Compare
Your pull request at commit
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm! Love keeping our demo up to date with the latest and greatest Dagster APIs. That duckdb issue with sling is driving me nuts, I'll try to take a crack at it at some point
type="duckdb", | ||
instance=f"{DUCKDB_PATH}", | ||
schema="RAW_DATA", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commenting out the schema will allow this to run locally—this is the bug I mentioned in the PR description.
Adding database param to be consistent with other environments—bug still exists though. Co-authored-by: Christian Minich <[email protected]>
Your pull request at commit
|
Updating the Sling demo to the new APIs.
Summary of updates:
There seems to be a bug with local dev when including a target schema with duckdb — "Catalog Error: Schema with name "raw_data" already exists!"