Simone P. M.

I also receive a strange offset WARN recently: com.snowflake.kafka.connector.internal.streaming.BufferedTopicPartitionChannel "skipping current record - expected offset 0 but received 0. The current offset stored in Snowflake: 0" IMHO does not make...

Thanks @sfc-gh-achyzy , to add context to this I still need to understand how SYSTEM$SNOWPIPE_STREAMING_UPDATE_CHANNEL_OFFSET_TOKEN works 100%, as it also happens that I set it to '0' for all the...

Thanks for confirming that!

@sfc-gh-jcieslak I noticed an unexpected behavior with 0.96.0 and user_type. snowflake_user gets created by default as NULL (PERSON), if we set it afterward to SERVICE, on next deploy the user...

Thanks, I tested and 0.97.0 new users resources suffers of this bug as well the old snowflake_user resource: https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/3125

Hello, even if the endpoint is reachable (see curl) and the configured endpoint matches, I still receive: "Connection to the Registry server failed (could not reach the server). Please check...

Kudos to this, a way to set session parameters via snow cli arguments would be greatly appreciated and in line with existing snowsql capabilities. With snowflake-cli you have to prepend...

Kudos to this, at the moment the Connector v2.3.0 supports Kafka 3.7 and Confluent 7.6. Do not know if it is an overkill, but in order to make this version...

com.snowflake:snowflake-kafka-connector:2.4.1 uses org.apache.avro:1.11.3 with CRITICAL CVE-2024-47561, having a slim version would surely help into not having to rebuild the whole fat jar to fix the issue.