Hi, In the Debezium community, we ran into an interesting corner case of connector config validation [1].
The Debezium Postgres connector requires a database resource called a "replication slot", which identifies this connector to the database and tracks progress it has made reading the TX log. This replication slot must not be shared between multiple clients (Debezium connectors, or others), so we added a validation to make sure that the slot configured by the user isn't active, i.e. no client is connected to it already. This works as expected when setting up, or restarting a connector, but when trying to update the connector configuration, the connector still is running when the configuration is validated, so the slot is active and validation hence fails. Is there a way we can distinguish during config validation whether the connector is (re-)started or whether it's a validation upon re-configuration (allowing us to skip this particular validation in the re-configuration case)? If that's not the case, would there be interest for a KIP for adding such capability to the Kafka Connect API? Thanks for any feedback, --Gunnar [1] https://issues.redhat.com/browse/DBZ-2952
