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

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

GitHub user lindong28 opened a pull request:

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

    KAFKA-2278; JmxTool should support querying all objects when object-n…

    …ame is omitted

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

    $ git pull https://github.com/lindong28/kafka KAFKA-2278

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

    https://github.com/apache/kafka/pull/181.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 #181
    
----
commit 82cd911cc832a91ecae5bca2a9e2ca8bc7ff69e4
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-08-31T22:53:22Z

    KAFKA-2278; JmxTool should support querying all objects when object-name is 
omitted

----


> JmxTool should support querying all objects when object-name is omitted
> -----------------------------------------------------------------------
>
>                 Key: KAFKA-2278
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2278
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Dong Lin
>            Assignee: Dong Lin
>         Attachments: KAFKA-2278.patch
>
>
> One usecase of JmxTool is to allow user to query all existing objects and 
> attributes, such that the developer can quickly lookup the right object name 
> and attribute name in the output. Indeed, existing API of JmxTool allows user 
> to do this when object-name is not specified in argument.
> However, current implementation of JmxTool doesn't support this operation due 
> to the way it is implemented. This is partly due to the fact that some JMX 
> object, such as java.lang:type=MemoryPool, doesn't have value for all its 
> attributes.
> The patch submitted here will fix the problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to