[jira] [Commented] (KAFKA-5087) Kafka Connect's configuration topics should always be compacted
[ https://issues.apache.org/jira/browse/KAFKA-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975066#comment-15975066 ] Ewen Cheslack-Postava commented on KAFKA-5087: -- I think this is really part of the general "create internal topics automatically" issue that is already filed in KAFKA-4667. Going to close this as duplicate, but copy over some of the notes since compaction wasn't mentioned in that JIRA yet. > Kafka Connect's configuration topics should always be compacted > --- > > Key: KAFKA-5087 > URL: https://issues.apache.org/jira/browse/KAFKA-5087 > Project: Kafka > Issue Type: Improvement > Components: KafkaConnect >Reporter: Gwen Shapira >Priority: Critical > > New users frequently lose their connector configuration because they did not > manually set the topic deletion policy to "compact". Not a good first > experience with our system. > 1. If the topics do not exist, Kafka Connect should create them with the > correct configuration. > 2. If the topics do exist, Kafka Connect should check their deletion policy > and refuse to start if it isn't "compact" > I'd love to do it (or have someone else do it) the moment the AdminClient is > merged and to have it in 0.11.0.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KAFKA-5087) Kafka Connect's configuration topics should always be compacted
[ https://issues.apache.org/jira/browse/KAFKA-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974949#comment-15974949 ] Gwen Shapira commented on KAFKA-5087: - The AdminClient pull request, if someone wants an early start :) https://github.com/apache/kafka/pull/2472 > Kafka Connect's configuration topics should always be compacted > --- > > Key: KAFKA-5087 > URL: https://issues.apache.org/jira/browse/KAFKA-5087 > Project: Kafka > Issue Type: Improvement > Components: KafkaConnect >Reporter: Gwen Shapira >Priority: Critical > > New users frequently lose their connector configuration because they did not > manually set the topic deletion policy to "compact". Not a good first > experience with our system. > 1. If the topics do not exist, Kafka Connect should create them with the > correct configuration. > 2. If the topics do exist, Kafka Connect should check their deletion policy > and refuse to start if it isn't "compact" > I'd love to do it (or have someone else do it) the moment the AdminClient is > merged and to have it in 0.11.0.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
