kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4849) Bug in KafkaStreams documentation
Date Mon, 26 Jun 2017 20:37:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063739#comment-16063739
] 

Guozhang Wang commented on KAFKA-4849:
--------------------------------------

We have resolved all the reported issues in this JIRA except the one in web docs, which is
covered in KAFKA-4705 already. Resolving this ticket for now.

> Bug in KafkaStreams documentation
> ---------------------------------
>
>                 Key: KAFKA-4849
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4849
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.2.0
>            Reporter: Seweryn Habdank-Wojewodzki
>            Assignee: Matthias J. Sax
>            Priority: Minor
>
> At the page: https://kafka.apache.org/documentation/streams
>  
> In the chapter titled Application Configuration and Execution, in the example there is
a line:
>  
> settings.put(StreamsConfig.ZOOKEEPER_CONNECT_CONFIG, "zookeeper1:2181");
>  
> but ZOOKEEPER_CONNECT_CONFIG is deprecated in the Kafka version 0.10.2.0.
>  
> Also the table on the page: https://kafka.apache.org/0102/documentation/#streamsconfigs
is a bit misleading.
> 1.     Again zookeeper.connect is deprecated.
> 2.     The client.id and zookeeper.connect are marked by high importance, 
> but according to http://docs.confluent.io/3.2.0/streams/developer-guide.html none of
them are important to initialize the stream.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message