logged to console/stdout before it finally turns off. This seems to defeat the purpose of silencing logging to stdout. This is important to me because the output to my program (querying Snowflake) is used as input to another process, and the downstream process is confused by seeing Snowflake logging output.
As a workaround, I've instead done
import Logger from "snowflake-sdk/lib/logger.js";
Logger.getInstance().configure({level: -1});
Please answer these questions before submitting your issue. In order to accurately debug the issue this information is required. Thanks!
What version of NodeJS driver are you using? 1.15.0
What operating system and processor architecture are you using? darwin arm64
What version of NodeJS are you using? v20.18.0
What are the component versions in the environment (
npm list
)? N/AWhat did you do?
No logging to stdout anywhere. Instead, I see the message
logged to console/stdout before it finally turns off. This seems to defeat the purpose of silencing logging to stdout. This is important to me because the output to my program (querying Snowflake) is used as input to another process, and the downstream process is confused by seeing Snowflake logging output.
As a workaround, I've instead done
but this isn't documented anywhere. Other workarounds like setting
additionalLogToConsole
to false doesn't work because a log file isn't set, and settinglogFilePath
also triggers that initial, unwanted message: https://github.com/snowflakedb/snowflake-connector-nodejs/blob/d50e1ce273ef945cd82ecd0a9480546134efe55b/lib/core.js#L189-L190