Selman

I'm having the same issue with `landoop/schema-registry:{0.9.5, latest}`. Apparently it's fixed in master and `latest` image built from c99eb61be6a57260fed67392efadee3b76d65677. Since in Dockerfile it's downloading a specific version (which 15 commits...

@sfc-gh-zli besides `SecurityManager`, if multiple connectors are running on the same Kafka Connect cluster, there's no way to distinguish their logs. ``` 2020-06-16 17:49:51,416 INFO || [SF_KAFKA_CONNECTOR] SnowflakeSinkTask[ID:0]:put 220 records...

Seems like it prepends new line to each log here; https://github.com/snowflakedb/snowflake-kafka-connector/blob/1cab4698ff6784db096d49627f077d9f61d80b72/src/main/java/com/snowflake/kafka/connector/internal/Logging.java#L137-L140 But like you said reason might be Snowflake Ingest SDK

It stays in that state. Previous logs I've shared only had a single poll before shutting the exporter down. It still reports old state even after multiple intervals; * [Logs](https://gist.github.com/seruman/e0859481db02e50a114a06e65fcadf84)...

Hi @seglo, Since there were new releases, I tried to re-produce the issue with the 0.7.1 and I can confirm it is still re-producable even after multiple poll intervals.

Observed the same exact behaviour, here's what I could find; Seems like the closure here (`p == pipelineProcessCmds | txPipelineProcessCmds`) is never called if the client is closed; AFAIU it...