Closed brianzinn closed 1 year ago
hi, thank you for submitting this issue.
seems to be very likely caused by the bind uploader (introduced in 1.6.14). when the driver inserts data into snowflake with arraybinding, and the bound data exceeds a certain size/amount, it chooses a different ingest strategy. this involves putting temporal files on the filesystem, which when the default current directory is not writable for the driver, is not successful.
as mentioned in https://github.com/snowflakedb/snowflake-connector-nodejs/issues/364#issuecomment-1396820416 (raised for AWS Lambda, should be similar for Google Cloud Function), you can either tackle this by
chmod
ding the current working directory to be writable for the driver if that's allowedarrayBindingThreshold
in the connection
options.until the driver is enhanced with a capability to have configureable locations for these temp files. closing this as a duplicate of #364 but if you feel this is an entirely different error, please reopen/comment
Thank-you for explanation. I’ll bump the threshold!
Please answer these questions before submitting your issue. Thanks!
What version of NodeJS are you using (
node --version
andnpm --version
)? node 16What operating system and processor architecture are you using? linux (google cloud function)
What are the component versions in the environment (
npm list
)?What did you do? If possible, provide a recipe for reproducing the error. A complete runnable program is good.
What did you expect to see? no errors
What did you see instead?
Add this to get standard output. n/a