[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
[
https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jose Armando Garcia Sancio updated KAFKA-13913:
---
Fix Version/s: (was: 3.3.0)
> Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
> -
>
> Key: KAFKA-13913
> URL: https://issues.apache.org/jira/browse/KAFKA-13913
> Project: Kafka
> Issue Type: Improvement
> Components: clients, streams
>Affects Versions: 3.2.0
>Reporter: François Rosière
>Assignee: François Rosière
>Priority: Major
> Labels: kip
>
> To have more flexibility, builders should be provided for the following
> objects
> * KafkaProducer
> * KafkaConsumer
> * KafkaStreams
> These builders will give an easy way to construct these objects using
> different arguments/combinations without having to add a new constructor
> every time a new parameter is required.
> They will also allow using already configured dependencies coming from an
> injection framework such as Spring (see
> [https://github.com/spring-projects/spring-kafka/issues/2244]).
> From a user point of view, builders would be used as follow
> {noformat}
> KafkaProducer kafkaProducer = new KafkaProducerBuilder MyPojo()
> .withKeySerializer()
> .withValueSerializer()
> .withInterceptors()
> .withPartitioner()
> .withMetricsReporter()
> .build();
> KafkaConsumer consumer = new KafkaConsumerBuilder MyPojo()
> .withKeyDeserializer()
> .withValueDeserializer()
> .withInterceptors()
> .withMetricsReporter()
> .build();
> KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
> )
> .withProducerInterceptors()
> .withConsumerInterceptors()
> .withTime() .withKafkaClientSupplier()
> .withMetricsReporter()
> .build();{noformat}
> This KIP can be seen as the continuity of the KIP-832.
> More details can be found in the related KIP
> [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211884640]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
[
https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13913:
Labels: kip (was: )
> Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
> -
>
> Key: KAFKA-13913
> URL: https://issues.apache.org/jira/browse/KAFKA-13913
> Project: Kafka
> Issue Type: Improvement
> Components: clients, streams
>Affects Versions: 3.2.0
>Reporter: François Rosière
>Assignee: François Rosière
>Priority: Major
> Labels: kip
> Fix For: 3.3.0
>
>
> To have more flexibility, builders should be provided for the following
> objects
> * KafkaProducer
> * KafkaConsumer
> * KafkaStreams
> These builders will give an easy way to construct these objects using
> different arguments/combinations without having to add a new constructor
> every time a new parameter is required.
> They will also allow using already configured dependencies coming from an
> injection framework such as Spring (see
> [https://github.com/spring-projects/spring-kafka/issues/2244]).
> From a user point of view, builders would be used as follow
> {noformat}
> KafkaProducer kafkaProducer = new KafkaProducerBuilder MyPojo()
> .withKeySerializer()
> .withValueSerializer()
> .withInterceptors()
> .withPartitioner()
> .withMetricsReporter()
> .build();
> KafkaConsumer consumer = new KafkaConsumerBuilder MyPojo()
> .withKeyDeserializer()
> .withValueDeserializer()
> .withInterceptors()
> .withMetricsReporter()
> .build();
> KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
> )
> .withProducerInterceptors()
> .withConsumerInterceptors()
> .withTime() .withKafkaClientSupplier()
> .withMetricsReporter()
> .build();{noformat}
> This KIP can be seen as the continuity of the KIP-832.
> More details can be found in the related KIP
> [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211884640]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
[
https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13913:
Component/s: streams
> Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
> -
>
> Key: KAFKA-13913
> URL: https://issues.apache.org/jira/browse/KAFKA-13913
> Project: Kafka
> Issue Type: Improvement
> Components: clients, streams
>Affects Versions: 3.2.0
>Reporter: François Rosière
>Assignee: François Rosière
>Priority: Major
> Fix For: 3.3.0
>
>
> To have more flexibility, builders should be provided for the following
> objects
> * KafkaProducer
> * KafkaConsumer
> * KafkaStreams
> These builders will give an easy way to construct these objects using
> different arguments/combinations without having to add a new constructor
> every time a new parameter is required.
> They will also allow using already configured dependencies coming from an
> injection framework such as Spring (see
> [https://github.com/spring-projects/spring-kafka/issues/2244]).
> From a user point of view, builders would be used as follow
> {noformat}
> KafkaProducer kafkaProducer = new KafkaProducerBuilder MyPojo()
> .withKeySerializer()
> .withValueSerializer()
> .withInterceptors()
> .withPartitioner()
> .withMetricsReporter()
> .build();
> KafkaConsumer consumer = new KafkaConsumerBuilder MyPojo()
> .withKeyDeserializer()
> .withValueDeserializer()
> .withInterceptors()
> .withMetricsReporter()
> .build();
> KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
> )
> .withProducerInterceptors()
> .withConsumerInterceptors()
> .withTime() .withKafkaClientSupplier()
> .withMetricsReporter()
> .build();{noformat}
> This KIP can be seen as the continuity of the KIP-832.
> More details can be found in the related KIP
> [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211884640]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
[
https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
François Rosière updated KAFKA-13913:
-
Fix Version/s: 3.3.0
> Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
> -
>
> Key: KAFKA-13913
> URL: https://issues.apache.org/jira/browse/KAFKA-13913
> Project: Kafka
> Issue Type: Improvement
> Components: clients
>Affects Versions: 3.2.0
>Reporter: François Rosière
>Assignee: François Rosière
>Priority: Major
> Fix For: 3.3.0
>
>
> To have more flexibility, builders should be provided for the following
> objects
> * KafkaProducer
> * KafkaConsumer
> * KafkaStreams
> These builders will give an easy way to construct these objects using
> different arguments/combinations without having to add a new constructor
> every time a new parameter is required.
> They will also allow using already configured dependencies coming from an
> injection framework such as Spring (see
> [https://github.com/spring-projects/spring-kafka/issues/2244]).
> From a user point of view, builders would be used as follow
> {noformat}
> KafkaProducer kafkaProducer = new KafkaProducerBuilder MyPojo()
> .withKeySerializer()
> .withValueSerializer()
> .withInterceptors()
> .withPartitioner()
> .withMetricsReporter()
> .build();
> KafkaConsumer consumer = new KafkaConsumerBuilder MyPojo()
> .withKeyDeserializer()
> .withValueDeserializer()
> .withInterceptors()
> .withMetricsReporter()
> .build();
> KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
> )
> .withProducerInterceptors()
> .withConsumerInterceptors()
> .withTime() .withKafkaClientSupplier()
> .withMetricsReporter()
> .build();{noformat}
> This KIP can be seen as the continuity of the KIP-832.
> More details can be found in the related KIP
> [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211884640]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
[
https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
François Rosière updated KAFKA-13913:
-
Description:
To have more flexibility, builders should be provided for the following objects
* KafkaProducer
* KafkaConsumer
* KafkaStreams
These builders will give an easy way to construct these objects using different
arguments/combinations without having to add a new constructor every time a new
parameter is required.
They will also allow using already configured dependencies coming from an
injection framework such as Spring (see
[https://github.com/spring-projects/spring-kafka/issues/2244]).
>From a user point of view, builders would be used as follow
{noformat}
KafkaProducer kafkaProducer = new KafkaProducerBuilder)
.withKeySerializer()
.withValueSerializer()
.withInterceptors()
.withPartitioner()
.withMetricsReporter()
.build();
KafkaConsumer consumer = new KafkaConsumerBuilder)
.withKeyDeserializer()
.withValueDeserializer()
.withInterceptors()
.withMetricsReporter()
.build();
KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
)
.withProducerInterceptors()
.withConsumerInterceptors()
.withTime() .withKafkaClientSupplier()
.withMetricsReporter()
.build();{noformat}
This KIP can be seen as the continuity of the KIP-832.
More details can be found in the related KIP
[https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211884640]
was:
To have more flexibility, builders should be provided for the following objects
* KafkaProducer
* KafkaConsumer
* KafkaStreams
These builders will give an easy way to construct these objects using different
arguments/combinations without having to add a new constructor every time a new
parameter is required.
They will also allow using already configured dependencies coming from an
injection framework such as Spring (see
[https://github.com/spring-projects/spring-kafka/issues/2244]).
>From a user point of view, builders would be used as follow
{noformat}
KafkaProducer kafkaProducer = new KafkaProducerBuilder)
.withKeySerializer()
.withValueSerializer()
.withInterceptors()
.withPartitioner()
.withMetricsReporter()
.build();
KafkaConsumer consumer = new KafkaConsumerBuilder)
.withKeyDeserializer()
.withValueDeserializer()
.withInterceptors()
.withMetricsReporter()
.build();
KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
)
.withProducerInterceptors()
.withConsumerInterceptors()
.withTime() .withKafkaClientSupplier()
.withMetricsReporter()
.build();{noformat}
This KIP can be seen as the continuity of the KIP-832.
> Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
> -
>
> Key: KAFKA-13913
> URL: https://issues.apache.org/jira/browse/KAFKA-13913
> Project: Kafka
> Issue Type: Improvement
> Components: clients
>Affects Versions: 3.2.0
>Reporter: François Rosière
>Assignee: François Rosière
>Priority: Major
>
> To have more flexibility, builders should be provided for the following
> objects
> * KafkaProducer
> * KafkaConsumer
> * KafkaStreams
> These builders will give an easy way to construct these objects using
> different arguments/combinations without having to add a new constructor
> every time a new parameter is required.
> They will also allow using already configured dependencies coming from an
> injection framework such as Spring (see
> [https://github.com/spring-projects/spring-kafka/issues/2244]).
> From a user point of view, builders would be used as follow
> {noformat}
> KafkaProducer kafkaProducer = new KafkaProducerBuilder MyPojo()
> .withKeySerializer()
> .withValueSerializer()
> .withInterceptors()
> .withPartitioner()
> .withMetricsReporter()
> .build();
> KafkaConsumer consumer = new KafkaConsumerBuilder MyPojo()
> .withKeyDeserializer()
> .withValueDeserializer()
> .withInterceptors()
> .withMetricsReporter()
> .build();
> KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
> )
> .withProducerInterceptors()
> .withConsumerInterceptors()
> .withTime() .withKafkaClientSupplier()
> .withMetricsReporter()
> .build();{noformat}
> This KIP can be seen as the continuity of the KIP-832.
> More details can be found in the related KIP
> [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211884640]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
[
https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
François Rosière updated KAFKA-13913:
-
Affects Version/s: 3.2.0
> Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
> -
>
> Key: KAFKA-13913
> URL: https://issues.apache.org/jira/browse/KAFKA-13913
> Project: Kafka
> Issue Type: Improvement
> Components: clients
>Affects Versions: 3.2.0
>Reporter: François Rosière
>Assignee: François Rosière
>Priority: Major
>
> To have more flexibility, builders should be provided for the following
> objects
> * KafkaProducer
> * KafkaConsumer
> * KafkaStreams
> These builders will give an easy way to construct these objects using
> different arguments/combinations without having to add a new constructor
> every time a new parameter is required.
> They will also allow using already configured dependencies coming from an
> injection framework such as Spring (see
> [https://github.com/spring-projects/spring-kafka/issues/2244]).
> From a user point of view, builders would be used as follow
> {noformat}
> KafkaProducer kafkaProducer = new KafkaProducerBuilder MyPojo()
> .withKeySerializer()
> .withValueSerializer()
> .withInterceptors()
> .withPartitioner()
> .withMetricsReporter()
> .build();
> KafkaConsumer consumer = new KafkaConsumerBuilder MyPojo()
> .withKeyDeserializer()
> .withValueDeserializer()
> .withInterceptors()
> .withMetricsReporter()
> .build();
> KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
> )
> .withProducerInterceptors()
> .withConsumerInterceptors()
> .withTime() .withKafkaClientSupplier()
> .withMetricsReporter()
> .build();{noformat}
> This KIP can be seen as the continuity of the KIP-832.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
[
https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
François Rosière updated KAFKA-13913:
-
Description:
To have more flexibility, builders should be provided for the following objects
* KafkaProducer
* KafkaConsumer
* KafkaStreams
These builders will give an easy way to construct these objects using different
arguments/combinations without having to add a new constructor every time a new
parameter is required.
They will also allow using already configured dependencies coming from an
injection framework such as Spring (see
[https://github.com/spring-projects/spring-kafka/issues/2244]).
>From a user point of view, builders would be used as follow
{noformat}
KafkaProducer kafkaProducer = new KafkaProducerBuilder)
.withKeySerializer()
.withValueSerializer()
.withInterceptors()
.withPartitioner()
.withMetricsReporter()
.build();
KafkaConsumer consumer = new KafkaConsumerBuilder)
.withKeyDeserializer()
.withValueDeserializer()
.withInterceptors()
.withMetricsReporter()
.build();
KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
)
.withProducerInterceptors()
.withConsumerInterceptors()
.withTime() .withKafkaClientSupplier()
.withMetricsReporter()
.build();{noformat}
This KIP can be seen as the continuity of the KIP-832.
was:
To have more flexibility, builders should be provided for the following objects
* KafkaProducer
* KafkaConsumer
* KafkaStreams
These builders will give an easy way to construct these objects using different
arguments/combinations without having to add a new constructor every time a new
parameter is required.
They will also allow using already configured dependencies coming from an
injection framework such as Spring (see
[https://github.com/spring-projects/spring-kafka/issues/2244]).
>From a user point of view, builders would be used as follow
{noformat}
KafkaProducer kafkaProducer = new KafkaProducerBuilder()
.withKeySerializer()
.withValueSerializer()
.withInterceptors()
.withPartitioner()
.withMetricsReporter()
.build();
KafkaConsumer consumer = new KafkaConsumerBuilder()
.withKeyDeserializer()
.withValueDeserializer()
.withInterceptors()
.withMetricsReporter()
.build();
KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
)
.withProducerInterceptors()
.withConsumerInterceptors()
.withTime() .withKafkaClientSupplier()
.withMetricsReporter()
.build();{noformat}
This KIP can be seen as the continuity of the KIP-832.
> Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
> -
>
> Key: KAFKA-13913
> URL: https://issues.apache.org/jira/browse/KAFKA-13913
> Project: Kafka
> Issue Type: Improvement
> Components: clients
>Reporter: François Rosière
>Assignee: François Rosière
>Priority: Major
>
> To have more flexibility, builders should be provided for the following
> objects
> * KafkaProducer
> * KafkaConsumer
> * KafkaStreams
> These builders will give an easy way to construct these objects using
> different arguments/combinations without having to add a new constructor
> every time a new parameter is required.
> They will also allow using already configured dependencies coming from an
> injection framework such as Spring (see
> [https://github.com/spring-projects/spring-kafka/issues/2244]).
> From a user point of view, builders would be used as follow
> {noformat}
> KafkaProducer kafkaProducer = new KafkaProducerBuilder MyPojo()
> .withKeySerializer()
> .withValueSerializer()
> .withInterceptors()
> .withPartitioner()
> .withMetricsReporter()
> .build();
> KafkaConsumer consumer = new KafkaConsumerBuilder MyPojo()
> .withKeyDeserializer()
> .withValueDeserializer()
> .withInterceptors()
> .withMetricsReporter()
> .build();
> KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
> )
> .withProducerInterceptors()
> .withConsumerInterceptors()
> .withTime() .withKafkaClientSupplier()
> .withMetricsReporter()
> .build();{noformat}
> This KIP can be seen as the continuity of the KIP-832.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (KAFKA-13913) Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
[
https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
François Rosière updated KAFKA-13913:
-
Description:
To have more flexibility, builders should be provided for the following objects
* KafkaProducer
* KafkaConsumer
* KafkaStreams
These builders will give an easy way to construct these objects using different
arguments/combinations without having to add a new constructor every time a new
parameter is required.
They will also allow using already configured dependencies coming from an
injection framework such as Spring (see
[https://github.com/spring-projects/spring-kafka/issues/2244]).
>From a user point of view, builders would be used as follow
{noformat}
KafkaProducer kafkaProducer = new KafkaProducerBuilder()
.withKeySerializer()
.withValueSerializer()
.withInterceptors()
.withPartitioner()
.withMetricsReporter()
.build();
KafkaConsumer consumer = new KafkaConsumerBuilder()
.withKeyDeserializer()
.withValueDeserializer()
.withInterceptors()
.withMetricsReporter()
.build();
KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
)
.withProducerInterceptors()
.withConsumerInterceptors()
.withTime() .withKafkaClientSupplier()
.withMetricsReporter()
.build();{noformat}
This KIP can be seen as the continuity of the KIP-832.
was:
To have more flexibility, builders should be provided for the following objects
* KafkaProducer
* KafkaConsumer
* KafkaStreams
These builders will give an easy way to construct these objects using different
arguments/combinations without having to add a new constructor every time a new
parameter is required.
They will also allow using already configured dependencies coming from an
injection framework such as Spring (see
[https://github.com/spring-projects/spring-kafka/issues/2244]).
>From a user point of view, builders would be used as follow
{noformat}
KafkaProducer kafkaProducer = new KafkaProducerBuilder() .withKeySerializer()
.withValueSerializer()
.withInterceptors() .withPartitioner()
.withMetricsReporter() .build(); KafkaConsumer consumer =
new KafkaConsumerBuilder()
.withKeyDeserializer()
.withValueDeserializer()
.withInterceptors()
.withMetricsReporter() .build(); KafkaStreams kafkaStreams =
new KafkaStreamsBuilder(, )
.withProducerInterceptors()
.withConsumerInterceptors() .withTime()
.withKafkaClientSupplier()
.withMetricsReporter() .build();{noformat}
This KIP can be seen as the continuity of the KIP-832.
> Provide builders for KafkaProducer/KafkaConsumer and KafkaStreams
> -
>
> Key: KAFKA-13913
> URL: https://issues.apache.org/jira/browse/KAFKA-13913
> Project: Kafka
> Issue Type: Improvement
> Components: clients
>Reporter: François Rosière
>Assignee: François Rosière
>Priority: Major
>
> To have more flexibility, builders should be provided for the following
> objects
> * KafkaProducer
> * KafkaConsumer
> * KafkaStreams
> These builders will give an easy way to construct these objects using
> different arguments/combinations without having to add a new constructor
> every time a new parameter is required.
> They will also allow using already configured dependencies coming from an
> injection framework such as Spring (see
> [https://github.com/spring-projects/spring-kafka/issues/2244]).
> From a user point of view, builders would be used as follow
> {noformat}
> KafkaProducer kafkaProducer = new KafkaProducerBuilder MyPojo>()
> .withKeySerializer()
> .withValueSerializer()
> .withInterceptors()
> .withPartitioner()
> .withMetricsReporter()
> .build();
> KafkaConsumer consumer = new KafkaConsumerBuilder MyPojo>()
> .withKeyDeserializer()
> .withValueDeserializer()
> .withInterceptors()
> .withMetricsReporter()
> .build();
> KafkaStreams kafkaStreams = new KafkaStreamsBuilder(,
> )
> .withProducerInterceptors()
> .withConsumerInterceptors()
> .withTime() .withKafkaClientSupplier()
> .withMetricsReporter()
> .build();{noformat}
> This KIP can be seen as the continuity of the KIP-832.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
