-
Notifications
You must be signed in to change notification settings - Fork 60
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
Issue running getDbCovariateData on snowflake #236
Comments
@mdlavallee92 - I don't have access to Snowflake so this will be hard to troubleshoot. That said, we can add a proper tempEmulationSchema parameter and deprecate the oracleTempSchema so that this is handled consistently in the package. Note of how that might look from DatabaseConnector docs: https://ohdsi.github.io/DatabaseConnector/reference/renderTranslateExecuteSql.html |
Linking to #159 since we may want to do this as a major, breaking change. |
@mdlavallee92 since version 3.7.0 you can pass the tempEmulationSchema in the getDbCovariateData function. Can you try if this works for you on Snowflake? |
There is still an issue in 3.7.0. While
And here is the error report - it got quite far along, so I think that the table was successfully created in the tempEmulationSchema, but then a later query is looking for it in the public schema.
|
Hey @ginberg and @katy-sadowski I believe the bug is on a line in the When running FE v3.7.1 on snowflake it works with the tempEmulationSchema setting if my covSettings are binary. Believe Katy has a continuous setting for covariates leading to the error. |
hi @mdlavallee92 you are right we should use tempEmulationSchema here, thanks for the catch! |
Trying to run FeatureExtraction on snowflake which requires a temp emulation schema. Currently the function only allows for oracleTempSchema, which should be updated to tempEmulationSchema so it is not db exclusive. This is what I used below
for which I get this error:
Not sure if others have got this issue or if I am setting this up wrong.
The text was updated successfully, but these errors were encountered: