-
Notifications
You must be signed in to change notification settings - Fork 133
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
SNOW-502598 Unable to execute statements in async mode (add async query execution capabilities) #208
Comments
I see that async queries are available for the Python driver, but not Nodejs |
will there be any support for NodeJS driver in the future for this? |
hi, we do have plans to support it in the future. unfortunately at this moment, i do not have any information on the timeline. |
reopened to be able to properly track the request |
I'd really like to see this feature added. I'm importing about 1.3 million records as a stream, batching the records in an array and then processing the. Since this is not async, each invocation of the Ideally I'd like the callback to be async and the SDK pause streaming in data from Snowflake until the promise has resolved. I think this would prevent the constant stream of data that's causing a memory issue. |
Thank you all so much for bearing with us ! Got some good news: work is ongoing on this one, will update this comment once it gets into review. |
PR: #672 |
PR #672 is merged and will be part of the upcoming October's release (hoping to release very soon) |
node.js driver version 1.9.1 released with the fix and is available on npm. thank you all for bearing with us ! |
Please answer these questions before submitting your issue. Thanks!
What version of NodeJS are you using (
node --version
andnpm --version
)?node:
v14.18.0
yarn:
1.22.10
What operating system and processor architecture are you using?
For Prod env: AWS Lambda
For local testing:
npm list
)?Hey, is there a way to execute statements in async manner so that after starting a heavy procedure I would be able to monitor its status using snowflake's
query_history()
calls?Looks like
snowflake-connector-nodejs
doesn't allow to setasync
execution parameter to the inner SnowFlake API call on statement execution…In general Snowflake REST API allows to execute sql statement in async mode
async:true
(see here) - this is an url parameter but it’s not allowed in NodeJs snowflake driver. I believe this is the place where we should be able to set async param:source code is here: https://github.com/snowflakedb/snowflake-connector-nodejs/blob/master/lib/connection/statement.js#L1134
Is there a plan to introduce this async flag support in
snowflake-connector-nodejs
? Or maybe someone could recommend other approach to achieve this asynchronous behavior?The text was updated successfully, but these errors were encountered: