You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Boyang Chen (JIRA)" <ji...@apache.org> on 2017/12/22 15:25:00 UTC
[jira] [Commented] (KAFKA-6386) Deprecate KafkaStreams constructor
taking StreamsConfig parameter
[ https://issues.apache.org/jira/browse/KAFKA-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301556#comment-16301556 ]
Boyang Chen commented on KAFKA-6386:
------------------------------------
Hi I'm new to Kafka repo and would like to contribute. Is there a way I could assign this ticket to myself?
> Deprecate KafkaStreams constructor taking StreamsConfig parameter
> -----------------------------------------------------------------
>
> Key: KAFKA-6386
> URL: https://issues.apache.org/jira/browse/KAFKA-6386
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 1.0.0
> Reporter: Matthias J. Sax
> Priority: Minor
> Labels: beginner, needs-kip, newbie
>
> Currently, {{KafkaStreams}} constructor has overloads that take either {{Properties}} or {{StreamsConfig}} a parameters.
> Because {{StreamsConfig}} is immutable and is created from a {{Properties}} object itself, the constructors accepting {{StreamsConfig}} are not useful and adds only boiler plate code. Thus, we should deprecate those constructors in order to remove them eventually.
> This JIRA includes a public API changes and thus requires a KIP: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)