Colin McCabe created KAFKA-10703: ------------------------------------ Summary: Document that default configs are not supported for TOPIC entities Key: KAFKA-10703 URL: https://issues.apache.org/jira/browse/KAFKA-10703 Project: Kafka Issue Type: Improvement Reporter: Colin McCabe
We should better document that default configs are not supported for TOPIC entities. Currently an attempt to set them gets confusing error messages. Using admin client's incrementalAlterConfigs with {type=TOPIC, name=""} gives a cryptic error stack trace: Exception in thread "main" java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidRequestException: Invalid config value for resource ConfigResource(type=TOPIC, name=''): Path must not end with / character at org.apache.kafka.common.internals.KafkaFutureImpl.wrapAndThrow(KafkaFutureImpl.java:45) at org.apache.kafka.common.internals.KafkaFutureImpl.access$000(KafkaFutureImpl.java:32) at org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:89) at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:260) at kafka.admin.ConfigCommand$.main(ConfigCommand.scala:91) at kafka.admin.ConfigCommand.main(ConfigCommand.scala) Caused by: org.apache.kafka.common.errors.InvalidRequestException: Invalid config value for resource ConfigResource(type=TOPIC, name=''): Path must not end with / character Similarly, kafka-configs.sh is not very clear about this issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)