THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Public Interfaces
The producer will have a few new configurations added. Default values of -1 will use broker defaults or raise an exceptionconfiguration added.
| Name | Description | Type | Default | Valid Values | Importance | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| producer.auto.create.topics.enable | Enable Configures how topic auto-creation of topics on the producer. Even if the broker config `auto.create.topics.enable` does not will occur. 'False' does allow auto-topic creation server-side, topics can still be created automatically client-side. | boolean | false | medium | auto.create.num.partitions | The default number of log partitions per topic for auto-created topics. This value is only used . 'Server-side' allows the server to create the topic if the broker's auto-creation configuration has been disabled and the producer 's config has been enabled. | int | -1 | medium | auto.create.replication.factorThe default replication factors for automatically created topics. This value is only used if the broker's auto-creation configuration has been disabled and the producer's config has been enabled. | int | enable' is true. 'Client-side' creates the topic client-side. Client-side auto-creation is only supported by brokers with version greater than 0.10.1.1. | String | allow-server-side | [false, allow-server-side, client-side]-1 | medium |
The goal is to deprecate automatic topic creation on the broker. At some point in the future, it may be useful to set the broker's auto.create.topics.enable default to false. However, for compatibility reasons, doing so is not possible at this time. Likewise, it would make sense to eventually change the default of the consumer's allow.auto.create.topics to false since it has no effect if the broker configuration is false.
...
The idea is to move the configuration and ability to automatically create topics client-side on the producer. Broker auto-topic creation will be deprecated. This includes deprecating the configuration 'auto.create.topics.enable' on the broker and 'allow.auto.create.topics' on the consumer. In the producer, auto-creation of a topic will occur through a specific request rather than through a side effect of requesting metadata. Unlike the configuration in the consumer, the ability to automatically create topics client-side will be independent of the server-side automatic topic creation controlled by the broker configuration.
If the broker config, 'auto.create.topics.enable' is set to true, a warning will be given that states the config is deprecated.
If server-side auto-creation is enabled with the broker's auto.create.topics.enable, the broker's defaults for partitions and replication factor will be used. When serverclient-side auto-creation is disabled, client-side auto-creation will try to use client-side configurations if set. However, if none exist, as represented by -1, enabled, broker-side defaults can will be used if the broker supports KIP 464. Client-side auto-creation is not supported for older brokers if no client configurations are given.
Compatibility, Deprecation, and Migration Plan
...
In order to automatically create topics with the producer, the producer's .auto.create.topics.enable config topics config must be set to true'client-side.' If the broker does not support KIP 464, auto.create.num.partitions and auto.create.replication.factor must be specified.
...
This KIP does not plan on changing the broker default. However, it is useful to understand compatibility issues if this were to happen.
- By default, 'allow-server-side' auto-creation is used. The broker's 'auto.create.topics.enable' must be configured as true.
- Although the broker config and server-side auto-creation is deprecated, this is the default to ensure compatibility.
- If the broker config is set to false, the topic will not be created automatically.
- Systems that rely on auto-creation would be encouraged to set the producer config producer.auto.create.topics .enable to true, but could also rely on to 'client-side.'
- This will effectively override the deprecated broker config, so even if it is
- configured to true, the server will not auto-create topics.
- Systems with older broker versions would need to set auto.create.num.partitions and auto.create.replication.factor upon allowing producer auto-creation.Enabling the configuration on the broker and the producer should not have any negative consequences, but there is no benefit in enabling both either. Broker-side defaults for partitions, replication factor will be usedthat do not support KIP-464 would not be compatible with this option.
- Systems that want to turn off auto-creation completely should set the producer config to false. This will override the broker config for this producer.
- This will fulfill the same role as 'allow.auto.create.topics' on the consumer, but for the producer.
- Systems that utilize auto-creation on the consumer will no longer be able to do so with only the producer config enabled.
- Enabling the broker config or making further changes to the code is required.
- By default, 'allow-server-side' auto-creation is used. The broker's 'auto.create.topics.enable' must be configured as true.
...
- Enabling true by default on the producer config:
- Topic auto-creation is a feature that is not supported as it once was, so defaulting to false supports this trend towards using admin client to create topics. Auto-creation does not work on older brokers without configuration client-side anyway, so it might be more clear that configuration must be done in order to keep using this feature.
- Add configurations producer-side for replication factor, partitions of new topics
- The idea is to keep this simple; configuring these values is not simple and could add to more issues for users.