[jira] [Commented] (AMBARI-20761) Update propery description for zookeeper.connect in Kafka Config

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-20761:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12863345/AMBARI-20761.PATCH
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/11395//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11395//console

This message is automatically generated.

> Update propery description for zookeeper.connect in Kafka Config
> ----------------------------------------------------------------
>
>                 Key: AMBARI-20761
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20761
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Minor
>         Attachments: AMBARI-20761.PATCH
>
>
> <property>
>     <name>zookeeper.connect</name>
>     <value>localhost:2181</value>
>     <description>
>       Zookeeper also allows you to add a "chroot" path which will make all kafka data for this cluster appear under a particular path.
>       This is a way to setup multiple Kafka clusters or other applications on the same zookeeper cluster. To do this give a connection
>      string in the form hostname1:port1,hostname2:port2,hostname3:port3/chroot/path which would put all this cluster's data under the
>       path /chroot/path. Note that you must create this path yourself prior to starting the broker and consumers must use the
>       same connection string.
>     </description>
> In the description it is said to create path before starting broker and consumer. Actually this is taken care in Kafka. So need to cleanup this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)