You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the thread #953 and the noises INFO from logging, I tried to use the snowflake.jdbc.map parameters to set the tracing for the jdbc to SEVERE or WARNING to avoid having to explicitly use the workaround of setting -Dnet.snowflake.jdbc.loggerImpl=net.snowflake.client.log.SLF4JLogger".
Based on the documentation I have set "snowflake.jdbc.map": "networkTimeout:20,tracing:WARNING" but failed with "message":"Connector configuration is invalid.
However when I exclude tracing parameter from the snowflake.jdbc.map the config can be added successfully.
Following the thread #953 and the noises INFO from logging, I tried to use the
snowflake.jdbc.map
parameters to set the tracing for the jdbc toSEVERE
orWARNING
to avoid having to explicitly use the workaround of setting-Dnet.snowflake.jdbc.loggerImpl=net.snowflake.client.log.SLF4JLogger"
.Based on the documentation I have set
"snowflake.jdbc.map": "networkTimeout:20,tracing:WARNING"
but failed with"message":"Connector configuration is invalid
.However when I exclude
tracing
parameter from thesnowflake.jdbc.map
the config can be added successfully.Snowflake kafka connector version: 2.5.0
Confluent platform: 7.6.1
I am assuming I have to set the KAFKA_OPTS asking snowflake.jdbc to explicitly to use SLF4JLogger.
The text was updated successfully, but these errors were encountered: