Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Current stateUnder Discussion

Discussion thread: tbaTBD

JIRA:  KAFKA-6037

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

...

  1. The main motivation of this KIP is stated in the related jira: "Today the downstream sub-topology's parallelism (aka the number of tasks) are purely dependent on the upstream sub-topology's parallelism, which ultimately depends on the source topic's num.partitions. However this does not work perfectly with dynamic scaling scenarios". 
  2. Depending on use-case, we might not need to use repartitioning topic, as keys might not change.
  3. The KStream application has no control over the sink topic creation, which means user has to create their own connecting Kafka topics with desired partitions which is cumbersome.

Proposed Changes

 

Code Block
languagejava
public class Produced<K, V> {
	protected String topicName;
	protected Boolean topicCreated = false;
	protected Boolean repartitionNeeded = true;
	protected Boolean useAsInternalTopicOnly = true;
 	protected Integer partitions; 
	protected Produced(String topicName, Boolean alreadyCreated) {
    	this.topicName = topicName;
   	    this.alreadyCreated = alreadyCreated;
	}
 
	protected Produced(String topicName, Integer partitions) {
    	this.topicName = topicName;
   	    this.partitions = partitions;
	}

 
	public static <K, V> Produced<K, V> withTopic(String topicName, Boolean alreadyCreated) {
    	return new Produced<>(topicName, alreadyCreated);
	}
 
	public static <K, V> Produced<K, V> withTopic(String topicName, Integer partitions) {
    	return new Produced<>(topicName, partitions);
	}

	public Produced<K, V> repartitionNeeded(Boolean repartitionNeeded) {
		this.repartitionNeeded = repartitionNeeded;
		return this;
	}
 
	public Produced<K, V> useAsInternalTopicOnly(Boolean useAsInternalTopicOnly) {
		this.useAsInternalTopicOnly = useAsInternalTopicOnly;
		return this;
	}
}

...