-
Notifications
You must be signed in to change notification settings - Fork 12
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
Feature: Convert RunQuery
to use duckdb
#1801
Comments
@jonthegeek- I pushed up a start to this on
feel free to take a look! |
Let's go ahead and implement. I think it might be of use in gsm.template. |
collaborate with @dpastoor and team to get this implemented. moving towards having only |
RunQuery
to use duckdb
In the poc I tried, I was passing the lazy table through, and if the step was not RunQuery, it would collect it into memory. Some of the discussions with devin revolved around what is the best to pass along as the argument for duckdb RunWorkflow:
LoadData:
ProcessSteps:
RunQuery:
|
df2 in RunQuery was due to converting DATACHG, DATAENT, and QUERY workflows to use sql instead: from:
to:
|
Feature Details
Add an
engine
argument toRunQuery()
. Default to an option, then "sqldf" if the option isn't set. Other option is "duckdb" right now. Check that the engine-package is installed for that option (and move sqldf to Suggests, along with duckdb).Example Code
Possible Implementation
Additional Comments
Be sure to test that both outputs are the same.
The text was updated successfully, but these errors were encountered: