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

ASF GitHub Bot commented on KAFKA-4849:
---------------------------------------

GitHub user mjsax opened a pull request:

    https://github.com/apache/kafka/pull/2648

    KAFKA-4849: Bug in KafkaStreams documentation

     - removed ZK config from Streams cods
     - removed deprecated ZK config parameter from configs table

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mjsax/kafka kafka-4849-docs-bug

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/2648.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2648
    
----

----


> 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.3.15#6346)

Reply via email to