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

ASF GitHub Bot commented on NIFI-2724:
--------------------------------------

Github user trixpan commented on the issue:

    https://github.com/apache/nifi/pull/1016
  
    @brianburnett 
    
    I suspect the reason for that is because you are trying to cherry-pick from 
the branch you already have a commit.
    
    Note how I suggested you to circle around...
    
    First step is to create a new branch from master. If you master already has 
the commit then you can use the upstream/master as a base (assuming you gave 
the github.com/apache/nifi remote the name of upstream)
    
    `git checkout origin master -b nifi-2724v2`
    
    If you do `git log` you should see the last commit as being whatever has 
been just published to the NiFi master git and also be told by `git status` 
that you are using nifi-2724v2`
    
    Now you perform a cherry pick that will copy your changes from the old 
nifi-2742 branch into to the branch (i.e. nifi-2724v2) you just created.


> JMX Processor
> -------------
>
>                 Key: NIFI-2724
>                 URL: https://issues.apache.org/jira/browse/NIFI-2724
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>    Affects Versions: 1.0.0
>         Environment: All platforms with Java RMI support for JMX
>            Reporter: Brian Burnett
>            Assignee: Andre
>            Priority: Minor
>              Labels: processor
>         Attachments: 0001-NIFI-2724-New-JMX-Processor.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The JMX Processor feature addition includes only GetJMX without 
> SecurityManager capabilities at this time.  The processor in its current 
> state is capable of pulling MBean Property and Attribute values from a remote 
> RMI Server.  Each set of Mbean data is wrapped in a JSON formatted FlowFile 
> for downstream processing.  It has the ability to control content with 
> whitelist and blacklist properties.
> Possible use for this processor and the reason it was created is to help make 
> sense of Kafka server metrics.
> Will followup with a SecurityManager Context Service and PutJMX Processor.



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

Reply via email to