You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2018/02/02 00:01:00 UTC

[jira] [Updated] (KAFKA-6386) Deprecate KafkaStreams constructor taking StreamsConfig parameter

     [ https://issues.apache.org/jira/browse/KAFKA-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias J. Sax updated KAFKA-6386:
-----------------------------------
    Fix Version/s: 1.2.0

> 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
>            Assignee: Boyang Chen
>            Priority: Minor
>              Labels: beginner, kip, newbie
>             Fix For: 1.2.0
>
>
> 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.
> KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-245%3A+Use+Properties+instead+of+StreamsConfig+in+KafkaStreams+constructor



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)