[jira] [Assigned] (NIFI-2118) Correct license/notice issues

[Joseph Percivall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Percivall reassigned NIFI-2118:
--

Assignee: Joseph Percivall

> Correct license/notice issues
> -
>
> Key: NIFI-2118
> URL: https://issues.apache.org/jira/browse/NIFI-2118
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Reporter: Joseph Witt
>Assignee: Joseph Percivall
> Fix For: 1.0.0, 0.7.0, 1.0.0-Beta
>
>
> *The LICENSE file has this entry "This product bundles 'Jolt' which is 
> available under an Apache License"
>   We should not have apache licensed items in our license file. We only need 
> to carry forward NOTICE information of such dependencies and those would go 
> in our NOTICE if applicable.
> * The nifi-assembly/NOTICE file has an "MIT License" section.  This should be 
> removed.  MIT licensed items should be reflected in the LICENSE file and Luaj 
> already appears to be there.
> * The nifi-assembly/NOTICE file references "Python Software Foundation" 
> section.  Python license is category A.  Such dependency belongs in LICENSE 
> file and not NOTICE.  Only if that dependency has a NOTICE with legally 
> required items should there be a reference to it in our NOTICE as well.



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

[jira] [Assigned] (NIFI-836) Cleanup Javadoc @link elements to point to correct package names

[Joseph Percivall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Percivall reassigned NIFI-836:
-

Assignee: Joseph Percivall

> Cleanup Javadoc @link elements to point to correct package names
> 
>
> Key: NIFI-836
> URL: https://issues.apache.org/jira/browse/NIFI-836
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Aldrin Piri
>Assignee: Joseph Percivall
>Priority: Minor
> Fix For: 0.3.0
>
> Attachments: NIFI-836.patch
>
>
> There are currently several Javadoc links throughout the codebase that point 
> to the wrong package structure, typically nifi.* instead of org.apache.nifi.*
> An exhaustive (?) listing:
> {code}
> ± % grep -nR "link nifi." nifi
> nifi/nifi-api/src/main/java/org/apache/nifi/annotation/behavior/SupportsBatching.java:30:
>  * {@link nifi.processor.ProcessSession ProcessSession}s' commits, as well as
> nifi/nifi-api/src/main/java/org/apache/nifi/annotation/behavior/SupportsBatching.java:33:
>  * {@link nifi.processor.ProcessSessionFactory ProcessSessionFactory}.
> nifi/nifi-api/src/main/java/org/apache/nifi/annotation/behavior/SupportsBatching.java:34:
>  * {@link nifi.processor.ProcessSessionFactory#createSession() 
> createSession()}.
> nifi/nifi-api/src/main/java/org/apache/nifi/annotation/behavior/SupportsBatching.java:37:
>  * {@link nifi.processor.ProcessSession#commit() ProcessSession.commit()} may
> nifi/nifi-api/src/main/java/org/apache/nifi/controller/annotation/OnConfigured.java:31:
>  * {@link nifi.controller.ConfigurationContext ConfigurationContext}.
> nifi/nifi-api/src/main/java/org/apache/nifi/controller/repository/FlowFileRecord.java:45:
>  * {@link nifi.controller.repository.ContentRepository ContentRepository}
> nifi/nifi-api/src/main/java/org/apache/nifi/processor/annotation/OnScheduled.java:32:
>  * {@link nifi.processor.SchedulingContext SchedulingContext}.
> nifi/nifi-api/src/main/java/org/apache/nifi/processor/annotation/SupportsBatching.java:30:
>  * {@link nifi.processor.ProcessSession ProcessSession}s' commits, as well as
> nifi/nifi-api/src/main/java/org/apache/nifi/processor/annotation/SupportsBatching.java:33:
>  * {@link nifi.processor.ProcessSessionFactory ProcessSessionFactory}.{@link 
> nifi.processor.ProcessSessionFactory#createSession() createSession()}.
> nifi/nifi-api/src/main/java/org/apache/nifi/processor/annotation/SupportsBatching.java:36:
>  * {@link nifi.processor.ProcessSession#commit() ProcessSession.commit()} may
> nifi/nifi-api/src/main/java/org/apache/nifi/processor/ProcessorInitializationContext.java:25:
>  * {@link nifi.processor.Processor Processor}s access to objects that may be 
> of
> nifi/nifi-api/src/main/java/org/apache/nifi/provenance/ProvenanceEventType.java:74:
>  * {@link nifi.processor.Relationship Relationship} and should provide
> nifi/nifi-api/src/main/java/org/apache/nifi/provenance/ProvenanceReporter.java:208:
>  * {@link nifi.processor.ProcessSession ProcessSession} to which this
> nifi/nifi-api/src/main/java/org/apache/nifi/provenance/ProvenanceReporter.java:230:
>  * {@link nifi.processor.ProcessSession ProcessSession} to which this
> nifi/nifi-api/src/main/java/org/apache/nifi/provenance/ProvenanceReporter.java:252:
>  * {@link nifi.processor.ProcessSession ProcessSession} to which this
> nifi/nifi-api/src/main/java/org/apache/nifi/provenance/ProvenanceReporter.java:276:
>  * {@link nifi.processor.ProcessSession ProcessSession} to which this
> nifi/nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java:144:
>  * {@link nifi.processor.Processor#onTrigger} commits or rolls back the
> nifi/nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java:153:
>  * of {@link nifi.processor.Processor#onTrigger} commits or rolls back the
> nifi/nifi-mock/src/main/java/org/apache/nifi/util/TestRunner.java:92: * 
> {@link nifi.processor.annotation.OnScheduled @OnScheduled} annotation. If
> nifi/nifi-mock/src/main/java/org/apache/nifi/util/TestRunner.java:107: * 
> {@link nifi.processor.annotation.OnUnscheduled @OnUnscheduled} annotation
> nifi/nifi-mock/src/main/java/org/apache/nifi/util/TestRunner.java:117: * 
> {@link nifi.processor.annotation.OnStopped @OnStopped} annotation.
> nifi/nifi-mock/src/main/java/org/apache/nifi/util/TestRunner.java:123: * 
> annotated with {@link nifi.processor.annotation.OnStopped @OnStopped}
> nifi/nifi-mock/src/main/java/org/apache/nifi/util/TestRunner.java:135: * 
> {@link nifi.processor.annotation.OnScheduled @OnScheduled} annotation. If
> nifi/nifi-mock/src/main/java/org/apache/nifi/util/TestRunner.java:150: * 
> {@link nifi.processor.annotation.OnUnscheduled @OnUnscheduled} 

[jira] [Assigned] (NIFI-907) The expression language guide should talk about standard flowfile attributes

[Joseph Percivall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Percivall reassigned NIFI-907:
-

Assignee: Joseph Percivall

> The expression language guide should talk about standard flowfile attributes
> 
>
> Key: NIFI-907
> URL: https://issues.apache.org/jira/browse/NIFI-907
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Joseph Witt
>Assignee: Joseph Percivall
>  Labels: beginner
> Fix For: 0.3.0
>
> Attachments: NIFI-907.patch
>
>
> The expression language should include a paragraph talking about standard 
> flowfile attributes.  There really are very few besides say filename, path, 
> uuid.  But these should be talked about.  And the fact that this is about it 
> is also good to point out.  It would also be be beneficial to describe how a 
> user can see what attributes were on a flowfile at a given point in the flow 
> to aid the user in debugging and truly understanding the flow.



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

[jira] [Assigned] (NIFI-864) Create a NAR for handling images

[Joseph Percivall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Percivall reassigned NIFI-864:
-

Assignee: Joseph Percivall  (was: Matt Gilman)

> Create a NAR for handling images
> 
>
> Key: NIFI-864
> URL: https://issues.apache.org/jira/browse/NIFI-864
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 0.3.0
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>Priority: Minor
> Fix For: 0.3.0
>
> Attachments: nifi-864.patch
>
>
> It is useful to be able to do image related manipulation in dataflows.  
> Create a new nifi-image-bundle which will start out by having two processors. 
>  One for extracting image metadata and another for altering the size of the 
> image.



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

[jira] [Assigned] (NIFI-867) @OnEnabled is not documented in the Developer Guide

[Joseph Percivall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Percivall reassigned NIFI-867:
-

Assignee: Joseph Percivall

> @OnEnabled is not documented in the Developer Guide
> ---
>
> Key: NIFI-867
> URL: https://issues.apache.org/jira/browse/NIFI-867
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Aldrin Piri
>Assignee: Joseph Percivall
> Attachments: NIFI-867.patch
>
>
> @OnEnabled is not included in the Component Lifecycle documentation and 
> should be provided with the same detail as the other annotations.



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

[jira] [Updated] (NIFI-2826) GetEventHubProcessor Support Enqueue Time

[Joseph Percivall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Percivall updated NIFI-2826:
---
Assignee: Joseph Niemiec

> GetEventHubProcessor Support Enqueue Time
> -
>
> Key: NIFI-2826
> URL: https://issues.apache.org/jira/browse/NIFI-2826
> Project: Apache NiFi
>  Issue Type: Improvement
> Environment: centos6, jdk1.8, nifi 1.0.0
>Reporter: Joseph Niemiec
>Assignee: Joseph Niemiec
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: patch.1
>
>
> The current GetEventHubProcessor should support allowing an enqueue time like 
> eventhubs to read messages from the past. This would also support reading 
> messages missed during downtime. Today the behaviour is for the processor to 
> start at the enqueue of when it was started by the user missing any past 
> messages. 



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

[jira] [Updated] (NIFI-2826) GetEventHubProcessor Support Enqueue Time

[Joseph Niemiec (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Niemiec updated NIFI-2826:
-
Attachment: patch.1

Initial Patch to support Enqueue Time

> GetEventHubProcessor Support Enqueue Time
> -
>
> Key: NIFI-2826
> URL: https://issues.apache.org/jira/browse/NIFI-2826
> Project: Apache NiFi
>  Issue Type: Improvement
> Environment: centos6, jdk1.8, nifi 1.0.0
>Reporter: Joseph Niemiec
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: patch.1
>
>
> The current GetEventHubProcessor should support allowing an enqueue time like 
> eventhubs to read messages from the past. This would also support reading 
> messages missed during downtime. Today the behaviour is for the processor to 
> start at the enqueue of when it was started by the user missing any past 
> messages. 



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

[jira] [Comment Edited] (NIFI-2826) GetEventHubProcessor Support Enqueue Time

[Joseph Niemiec (JIRA)]

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

Joseph Niemiec edited comment on NIFI-2826 at 9/27/16 2:37 AM:
---

I have an initial working version, just refining it before attaching a patch. 


was (Author: josephxsxn):
I have an initial working version, just refining it and making tests before 
attaching a patch. 

> GetEventHubProcessor Support Enqueue Time
> -
>
> Key: NIFI-2826
> URL: https://issues.apache.org/jira/browse/NIFI-2826
> Project: Apache NiFi
>  Issue Type: Improvement
> Environment: centos6, jdk1.8, nifi 1.0.0
>Reporter: Joseph Niemiec
>Priority: Minor
> Fix For: 1.1.0
>
>
> The current GetEventHubProcessor should support allowing an enqueue time like 
> eventhubs to read messages from the past. This would also support reading 
> messages missed during downtime. Today the behaviour is for the processor to 
> start at the enqueue of when it was started by the user missing any past 
> messages. 



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

[jira] [Updated] (NIFI-2826) GetEventHubProcessor Support Enqueue Time

[Joseph Niemiec (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Niemiec updated NIFI-2826:
-
Priority: Minor  (was: Major)

> GetEventHubProcessor Support Enqueue Time
> -
>
> Key: NIFI-2826
> URL: https://issues.apache.org/jira/browse/NIFI-2826
> Project: Apache NiFi
>  Issue Type: Improvement
> Environment: centos6, jdk1.8, nifi 1.0.0
>Reporter: Joseph Niemiec
>Priority: Minor
> Fix For: 1.1.0
>
>
> The current GetEventHubProcessor should support allowing an enqueue time like 
> eventhubs to read messages from the past. This would also support reading 
> messages missed during downtime. Today the behaviour is for the processor to 
> start at the enqueue of when it was started by the user missing any past 
> messages. 



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

[jira] [Updated] (NIFI-2826) GetEventHubProcessor Support Enqueue Time

[Joseph Niemiec (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Niemiec updated NIFI-2826:
-
Fix Version/s: 1.1.0
   Issue Type: Improvement  (was: Bug)

> GetEventHubProcessor Support Enqueue Time
> -
>
> Key: NIFI-2826
> URL: https://issues.apache.org/jira/browse/NIFI-2826
> Project: Apache NiFi
>  Issue Type: Improvement
> Environment: centos6, jdk1.8, nifi 1.0.0
>Reporter: Joseph Niemiec
> Fix For: 1.1.0
>
>
> The current GetEventHubProcessor should support allowing an enqueue time like 
> eventhubs to read messages from the past. This would also support reading 
> messages missed during downtime. Today the behaviour is for the processor to 
> start at the enqueue of when it was started by the user missing any past 
> messages. 



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

[jira] [Created] (NIFI-2826) GetEventHubProcessor Support Enqueue Time

[Joseph Niemiec (JIRA)]

Joseph Niemiec created NIFI-2826:


 Summary: GetEventHubProcessor Support Enqueue Time
 Key: NIFI-2826
 URL: https://issues.apache.org/jira/browse/NIFI-2826
 Project: Apache NiFi
  Issue Type: Bug
 Environment: centos6, jdk1.8, nifi 1.0.0
Reporter: Joseph Niemiec


The current GetEventHubProcessor should support allowing an enqueue time like 
eventhubs to read messages from the past. This would also support reading 
messages missed during downtime. Today the behaviour is for the processor to 
start at the enqueue of when it was started by the user missing any past 
messages. 



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

[jira] [Commented] (NIFI-1757) If Bulletin Board is opened, the requests keep occurring in the background even after the Bulletin Board is closed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1757:
--

GitHub user scottyaslan opened a pull request:

https://github.com/apache/nifi/pull/1069

[NIFI-1757] remove iframe from shell dialog to prevent reoccurring re…

…quests, update fill color and label config dialog content margins to fit 
into their respective dialogs

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

$ git pull https://github.com/scottyaslan/nifi NIFI-1757

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

https://github.com/apache/nifi/pull/1069.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 #1069


commit b432ffc83cbbfbd91fd0302a16c55e8e9d126b45
Author: Scott Aslan 
Date:   2016-09-27T01:51:29Z

[NIFI-1757] remove iframe from shell dialog to prevent reoccurring 
requests, update fill color and label config dialog content margins to fit into 
their respective dialogs




> If Bulletin Board is opened, the requests keep occurring in the background 
> even after the Bulletin Board is closed
> --
>
> Key: NIFI-1757
> URL: https://issues.apache.org/jira/browse/NIFI-1757
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Scott Aslan
>
> I clicked to open the Bulletin Board and then closed it. Opening Chrome's 
> Developer Tools, I can see that the requests are still made to retrieve 
> bulletins every few seconds.



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

[GitHub] nifi pull request #1069: [NIFI-1757] remove iframe from shell dialog to prev...

[scottyaslan]

GitHub user scottyaslan opened a pull request:

https://github.com/apache/nifi/pull/1069

[NIFI-1757] remove iframe from shell dialog to prevent reoccurring re…

…quests, update fill color and label config dialog content margins to fit 
into their respective dialogs

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

$ git pull https://github.com/scottyaslan/nifi NIFI-1757

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

https://github.com/apache/nifi/pull/1069.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 #1069


commit b432ffc83cbbfbd91fd0302a16c55e8e9d126b45
Author: Scott Aslan 
Date:   2016-09-27T01:51:29Z

[NIFI-1757] remove iframe from shell dialog to prevent reoccurring 
requests, update fill color and label config dialog content margins to fit into 
their respective dialogs




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-2825) Remote Process Group should use num of queued flow files in remote nodes to distribute load

[Koji Kawamura (JIRA)]

Koji Kawamura created NIFI-2825:
---

 Summary: Remote Process Group should use num of queued flow files 
in remote nodes to distribute load
 Key: NIFI-2825
 URL: https://issues.apache.org/jira/browse/NIFI-2825
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.0.0
 Environment: Clustered
Reporter: Koji Kawamura
Assignee: Koji Kawamura
 Fix For: 1.1.0


A RPG (Site-to-Site client) should take into account of the number of queued 
flow files in each remote cluster nodes, to calculate the load distribution 
balance among target nodes. So that it can send more data to nodes those have 
less queued files, or receive more data from nodes those have more queued files.

However, after the clustering mechanism has changed since 1.0, this load 
distribution logic is not handled appropriately. Site-to-Site remote component 
always returns flow file count as 0. So RPG distribute load evenly, even if a 
remote cluster has unbalanced load among nodes.

We need to fix the remote node API to expose queued flow file count correctly.



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

[GitHub] nifi-minifi-cpp pull request #14: MINIFI-34 Establishing CMake build system ...

[apiri]

GitHub user apiri opened a pull request:

https://github.com/apache/nifi-minifi-cpp/pull/14

MINIFI-34 Establishing CMake build system to provide build functional…

MINIFI-34 Establishing CMake build system to provide build functionality 
equivalent to pre-existing Makefile.

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

$ git pull https://github.com/apiri/nifi-minifi-cpp MINIFI-34-CMAKE

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

https://github.com/apache/nifi-minifi-cpp/pull/14.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 #14


commit a358693c23252e427031a3ef4d25281b15116cb7
Author: Aldrin Piri 
Date:   2016-05-05T21:32:57Z

MINIFI-34 Establishing CMake build system to provide build functionality 
equivalent to pre-existing Makefile.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2711) Allow extension of nifi-assembly pom to override properties

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2711:
--

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/972
  
@olegz rebased and fixed conflicts, diffed assemblies before and after


> Allow extension of nifi-assembly pom to override properties
> ---
>
> Key: NIFI-2711
> URL: https://issues.apache.org/jira/browse/NIFI-2711
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>
> As part of the tls-toolkit work, the nifi.properties filtering was moved to 
> nifi-resources.  This didn't take into account usecases where overriding the 
> nifi.properties in an assembly was desired by those extending our assembly.



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

[GitHub] nifi issue #972: NIFI-2711 - Making top-level nifi-assemblies directory with...

[brosander]

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/972
  
@olegz rebased and fixed conflicts, diffed assemblies before and after


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-2824) Errors encountered when saving from Advanced UI (UpdateAttribute, JoltTransformProcessor)

[Matt Gilman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman updated NIFI-2824:
--
Status: Patch Available  (was: Open)

> Errors encountered when saving from Advanced UI (UpdateAttribute, 
> JoltTransformProcessor)
> -
>
> Key: NIFI-2824
> URL: https://issues.apache.org/jira/browse/NIFI-2824
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Yolanda M. Davis
>Assignee: Matt Gilman
>
> When attempting to save configuration changes using the Advanced UI for 
> UpdateAttributes or JoltTransformProcessor the following example exception 
> stack trace was encountered in a secured clustered environment (e.g. 
> Transaction already in progress):
> Received a status of 409 from ydavis-ldap-nifi-demo-1.openstacklocal:9091 for 
> request PUT /nifi-api/processors/66ce1842-0157-1000--7e910d9e when 
> performing first stage of two-stage commit. The action will not occur. Node 
> explanation: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
> 2016-09-26 16:07:43,445 ERROR [NiFi Web Server-22] 
> c.s.j.spi.container.ContainerResponse The RuntimeException could not be 
> mapped to a response, re-throwing to the HTTP container
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> 2016-09-26 16:07:43,454 WARN [NiFi Web Server-22] 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.1.0-SNAPSHOT/api/standard/processor/properties
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]



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

[jira] [Commented] (NIFI-2824) Errors encountered when saving from Advanced UI (UpdateAttribute, JoltTransformProcessor)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2824:
--

GitHub user mcgilman opened a pull request:

https://github.com/apache/nifi/pull/1068

Ensuring Custom UI requests are correctly replicated when clustered

NIFI-2824:
- Updating replication logic to account for the potential replication 
target and then invoking the corresponding action.

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

$ git pull https://github.com/mcgilman/nifi NIFI-2824

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

https://github.com/apache/nifi/pull/1068.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 #1068


commit c13efe5b05096b1d7fea30eb6f2cffeb839c2555
Author: Matt Gilman 
Date:   2016-09-26T20:03:07Z

NIFI-2824:
- Updating replication logic to account for the potential replication 
target and then invoking the corresponding action.




> Errors encountered when saving from Advanced UI (UpdateAttribute, 
> JoltTransformProcessor)
> -
>
> Key: NIFI-2824
> URL: https://issues.apache.org/jira/browse/NIFI-2824
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Yolanda M. Davis
> Fix For: 1.1.0
>
>
> When attempting to save configuration changes using the Advanced UI for 
> UpdateAttributes or JoltTransformProcessor the following example exception 
> stack trace was encountered in a secured clustered environment (e.g. 
> Transaction already in progress):
> Received a status of 409 from ydavis-ldap-nifi-demo-1.openstacklocal:9091 for 
> request PUT /nifi-api/processors/66ce1842-0157-1000--7e910d9e when 
> performing first stage of two-stage commit. The action will not occur. Node 
> explanation: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
> 2016-09-26 16:07:43,445 ERROR [NiFi Web Server-22] 
> c.s.j.spi.container.ContainerResponse The RuntimeException could not be 
> mapped to a response, re-throwing to the HTTP container
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> 2016-09-26 16:07:43,454 WARN [NiFi Web Server-22] 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.1.0-SNAPSHOT/api/standard/processor/properties
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]



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

[jira] [Updated] (NIFI-2824) Errors encountered when saving from Advanced UI (UpdateAttribute, JoltTransformProcessor)

[Matt Gilman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman updated NIFI-2824:
--
Fix Version/s: 1.1.0

> Errors encountered when saving from Advanced UI (UpdateAttribute, 
> JoltTransformProcessor)
> -
>
> Key: NIFI-2824
> URL: https://issues.apache.org/jira/browse/NIFI-2824
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Yolanda M. Davis
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> When attempting to save configuration changes using the Advanced UI for 
> UpdateAttributes or JoltTransformProcessor the following example exception 
> stack trace was encountered in a secured clustered environment (e.g. 
> Transaction already in progress):
> Received a status of 409 from ydavis-ldap-nifi-demo-1.openstacklocal:9091 for 
> request PUT /nifi-api/processors/66ce1842-0157-1000--7e910d9e when 
> performing first stage of two-stage commit. The action will not occur. Node 
> explanation: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
> 2016-09-26 16:07:43,445 ERROR [NiFi Web Server-22] 
> c.s.j.spi.container.ContainerResponse The RuntimeException could not be 
> mapped to a response, re-throwing to the HTTP container
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> 2016-09-26 16:07:43,454 WARN [NiFi Web Server-22] 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.1.0-SNAPSHOT/api/standard/processor/properties
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]



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

[jira] [Assigned] (NIFI-2824) Errors encountered when saving from Advanced UI (UpdateAttribute, JoltTransformProcessor)

[Matt Gilman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman reassigned NIFI-2824:
-

Assignee: Matt Gilman

> Errors encountered when saving from Advanced UI (UpdateAttribute, 
> JoltTransformProcessor)
> -
>
> Key: NIFI-2824
> URL: https://issues.apache.org/jira/browse/NIFI-2824
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Yolanda M. Davis
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> When attempting to save configuration changes using the Advanced UI for 
> UpdateAttributes or JoltTransformProcessor the following example exception 
> stack trace was encountered in a secured clustered environment (e.g. 
> Transaction already in progress):
> Received a status of 409 from ydavis-ldap-nifi-demo-1.openstacklocal:9091 for 
> request PUT /nifi-api/processors/66ce1842-0157-1000--7e910d9e when 
> performing first stage of two-stage commit. The action will not occur. Node 
> explanation: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
> 2016-09-26 16:07:43,445 ERROR [NiFi Web Server-22] 
> c.s.j.spi.container.ContainerResponse The RuntimeException could not be 
> mapped to a response, re-throwing to the HTTP container
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> 2016-09-26 16:07:43,454 WARN [NiFi Web Server-22] 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.1.0-SNAPSHOT/api/standard/processor/properties
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]



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

[GitHub] nifi pull request #1068: Ensuring Custom UI requests are correctly replicate...

[mcgilman]

GitHub user mcgilman opened a pull request:

https://github.com/apache/nifi/pull/1068

Ensuring Custom UI requests are correctly replicated when clustered

NIFI-2824:
- Updating replication logic to account for the potential replication 
target and then invoking the corresponding action.

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

$ git pull https://github.com/mcgilman/nifi NIFI-2824

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

https://github.com/apache/nifi/pull/1068.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 #1068


commit c13efe5b05096b1d7fea30eb6f2cffeb839c2555
Author: Matt Gilman 
Date:   2016-09-26T20:03:07Z

NIFI-2824:
- Updating replication logic to account for the potential replication 
target and then invoking the corresponding action.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2795) Enhance Cluster UI with System Diagnostics

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2795:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1042
  
@jvwing I'll just squash those changes into your commit before I push. Just 
wanted to communicate before I do that. Thanks!


> Enhance Cluster UI with System Diagnostics
> --
>
> Key: NIFI-2795
> URL: https://issues.apache.org/jira/browse/NIFI-2795
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Attachments: cluster-01-nodes.png, cluster-02-system.png, 
> cluster-03-jvm.png, cluster-04-flowfile-store.png, 
> cluster-05-content-store.png
>
>
> The Cluster UI currently provides some basic information on each node in the 
> cluster and options for connecting and disconnecting nodes. I propose to add 
> system diagnostics information in tables, contained in multiple tabs.  
> Roughly, the tabs should cover the same content as the System Diagnostics 
> dialog already in the System UI, but in a tabular format for comparing across 
> nodes.



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

[GitHub] nifi issue #1042: NIFI-2795 Sys Diagnostics in Cluster UI

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1042
  
@jvwing I'll just squash those changes into your commit before I push. Just 
wanted to communicate before I do that. Thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (NIFI-2822) JoltTransformer Advanced UI doesn't load in a secured cluster

[Matt Gilman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman resolved NIFI-2822.
---
   Resolution: Fixed
Fix Version/s: 1.1.0

> JoltTransformer Advanced UI doesn't load in a secured cluster
> -
>
> Key: NIFI-2822
> URL: https://issues.apache.org/jira/browse/NIFI-2822
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: LDAP-secured 3 node NiFi cluster
>Reporter: Andrew Grande
>Assignee: Yolanda M. Davis
> Fix For: 1.1.0
>
>
> JoltTransformer -> click Advanced. The UI doesn't load - "An error has 
> occurred loading the editor."
> The error on the backend is below, doesn't seem to pass authorization tokens 
> at all, lists 'anonymous':
> {noformat}
> 2016-09-26 09:19:16,794 WARN NiFi Web Server-74433 - 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.0.0.2.0.0.0-579/api/standard/processor/details
> org.apache.nifi.authorization.AccessDeniedException: Unknown user with 
> identity 'anonymous'.
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:166)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:163)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:179)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.lambda$getComponentDetails$0(StandardNiFiWebConfigurationContext.java:342)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade.authorizeAccess(StandardNiFiServiceFacade.java:289)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke()
>  ~[na:na]
>   at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) 
> ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
>  ~[na:na]
>   at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$EnhancerBySpringCGLIB$$80c8c166.authorizeAccess()
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.getComponentDetails(StandardNiFiWebConfigurationContext.java:340)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext.getComponentDetails(StandardNiFiWebConfigurationContext.java:256)
>  ~[na:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:47)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:52)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorResource.getDetails(ProcessorResource.java:49)
>  ~[classes/:na]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_77]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_77]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_77]
>   at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_77]
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  

[jira] [Assigned] (NIFI-1757) If Bulletin Board is opened, the requests keep occurring in the background even after the Bulletin Board is closed

[Scott Aslan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Aslan reassigned NIFI-1757:
-

Assignee: Scott Aslan

> If Bulletin Board is opened, the requests keep occurring in the background 
> even after the Bulletin Board is closed
> --
>
> Key: NIFI-1757
> URL: https://issues.apache.org/jira/browse/NIFI-1757
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Scott Aslan
>
> I clicked to open the Bulletin Board and then closed it. Opening Chrome's 
> Developer Tools, I can see that the requests are still made to retrieve 
> bulletins every few seconds.



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

[jira] [Commented] (NIFI-2822) JoltTransformer Advanced UI doesn't load in a secured cluster

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2822:
--

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/1065
  
thx @mcgilman !


> JoltTransformer Advanced UI doesn't load in a secured cluster
> -
>
> Key: NIFI-2822
> URL: https://issues.apache.org/jira/browse/NIFI-2822
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: LDAP-secured 3 node NiFi cluster
>Reporter: Andrew Grande
>Assignee: Yolanda M. Davis
>
> JoltTransformer -> click Advanced. The UI doesn't load - "An error has 
> occurred loading the editor."
> The error on the backend is below, doesn't seem to pass authorization tokens 
> at all, lists 'anonymous':
> {noformat}
> 2016-09-26 09:19:16,794 WARN NiFi Web Server-74433 - 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.0.0.2.0.0.0-579/api/standard/processor/details
> org.apache.nifi.authorization.AccessDeniedException: Unknown user with 
> identity 'anonymous'.
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:166)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:163)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:179)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.lambda$getComponentDetails$0(StandardNiFiWebConfigurationContext.java:342)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade.authorizeAccess(StandardNiFiServiceFacade.java:289)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke()
>  ~[na:na]
>   at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) 
> ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
>  ~[na:na]
>   at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$EnhancerBySpringCGLIB$$80c8c166.authorizeAccess()
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.getComponentDetails(StandardNiFiWebConfigurationContext.java:340)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext.getComponentDetails(StandardNiFiWebConfigurationContext.java:256)
>  ~[na:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:47)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:52)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorResource.getDetails(ProcessorResource.java:49)
>  ~[classes/:na]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_77]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_77]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_77]
>   at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_77]
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> 

[GitHub] nifi issue #1065: NIFI-2822 - Provide the JWT Authorization token

[YolandaMDavis]

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/1065
  
thx @mcgilman !


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2822) JoltTransformer Advanced UI doesn't load in a secured cluster

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2822:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1065
  
Looks good @YolandaMDavis! This has been merged to master. Thanks!


> JoltTransformer Advanced UI doesn't load in a secured cluster
> -
>
> Key: NIFI-2822
> URL: https://issues.apache.org/jira/browse/NIFI-2822
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: LDAP-secured 3 node NiFi cluster
>Reporter: Andrew Grande
>Assignee: Yolanda M. Davis
>
> JoltTransformer -> click Advanced. The UI doesn't load - "An error has 
> occurred loading the editor."
> The error on the backend is below, doesn't seem to pass authorization tokens 
> at all, lists 'anonymous':
> {noformat}
> 2016-09-26 09:19:16,794 WARN NiFi Web Server-74433 - 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.0.0.2.0.0.0-579/api/standard/processor/details
> org.apache.nifi.authorization.AccessDeniedException: Unknown user with 
> identity 'anonymous'.
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:166)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:163)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:179)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.lambda$getComponentDetails$0(StandardNiFiWebConfigurationContext.java:342)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade.authorizeAccess(StandardNiFiServiceFacade.java:289)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke()
>  ~[na:na]
>   at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) 
> ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
>  ~[na:na]
>   at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$EnhancerBySpringCGLIB$$80c8c166.authorizeAccess()
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.getComponentDetails(StandardNiFiWebConfigurationContext.java:340)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext.getComponentDetails(StandardNiFiWebConfigurationContext.java:256)
>  ~[na:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:47)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:52)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorResource.getDetails(ProcessorResource.java:49)
>  ~[classes/:na]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_77]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_77]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_77]
>   at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_77]
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   

[jira] [Commented] (NIFI-2822) JoltTransformer Advanced UI doesn't load in a secured cluster

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2822:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1065


> JoltTransformer Advanced UI doesn't load in a secured cluster
> -
>
> Key: NIFI-2822
> URL: https://issues.apache.org/jira/browse/NIFI-2822
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: LDAP-secured 3 node NiFi cluster
>Reporter: Andrew Grande
>Assignee: Yolanda M. Davis
>
> JoltTransformer -> click Advanced. The UI doesn't load - "An error has 
> occurred loading the editor."
> The error on the backend is below, doesn't seem to pass authorization tokens 
> at all, lists 'anonymous':
> {noformat}
> 2016-09-26 09:19:16,794 WARN NiFi Web Server-74433 - 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.0.0.2.0.0.0-579/api/standard/processor/details
> org.apache.nifi.authorization.AccessDeniedException: Unknown user with 
> identity 'anonymous'.
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:166)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:163)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:179)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.lambda$getComponentDetails$0(StandardNiFiWebConfigurationContext.java:342)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade.authorizeAccess(StandardNiFiServiceFacade.java:289)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke()
>  ~[na:na]
>   at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) 
> ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
>  ~[na:na]
>   at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$EnhancerBySpringCGLIB$$80c8c166.authorizeAccess()
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.getComponentDetails(StandardNiFiWebConfigurationContext.java:340)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext.getComponentDetails(StandardNiFiWebConfigurationContext.java:256)
>  ~[na:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:47)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:52)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorResource.getDetails(ProcessorResource.java:49)
>  ~[classes/:na]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_77]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_77]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_77]
>   at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_77]
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> 

[jira] [Commented] (NIFI-2822) JoltTransformer Advanced UI doesn't load in a secured cluster

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-2822:
---

Commit 30f008d6764ac9f41c9bbdeec723ed09ac5c44a6 in nifi's branch 
refs/heads/master from [~YolandaMDavis]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=30f008d ]

NIFI-2822 - pass the JWT Authorization token i. This closes #1065


> JoltTransformer Advanced UI doesn't load in a secured cluster
> -
>
> Key: NIFI-2822
> URL: https://issues.apache.org/jira/browse/NIFI-2822
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: LDAP-secured 3 node NiFi cluster
>Reporter: Andrew Grande
>Assignee: Yolanda M. Davis
>
> JoltTransformer -> click Advanced. The UI doesn't load - "An error has 
> occurred loading the editor."
> The error on the backend is below, doesn't seem to pass authorization tokens 
> at all, lists 'anonymous':
> {noformat}
> 2016-09-26 09:19:16,794 WARN NiFi Web Server-74433 - 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.0.0.2.0.0.0-579/api/standard/processor/details
> org.apache.nifi.authorization.AccessDeniedException: Unknown user with 
> identity 'anonymous'.
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:166)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:163)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:179)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.lambda$getComponentDetails$0(StandardNiFiWebConfigurationContext.java:342)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade.authorizeAccess(StandardNiFiServiceFacade.java:289)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke()
>  ~[na:na]
>   at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) 
> ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
>  ~[na:na]
>   at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$EnhancerBySpringCGLIB$$80c8c166.authorizeAccess()
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.getComponentDetails(StandardNiFiWebConfigurationContext.java:340)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext.getComponentDetails(StandardNiFiWebConfigurationContext.java:256)
>  ~[na:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:47)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:52)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorResource.getDetails(ProcessorResource.java:49)
>  ~[classes/:na]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_77]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_77]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_77]
>   at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_77]
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.1.jar:1.19.1]
>   at 
> 

[GitHub] nifi issue #1065: NIFI-2822 - Provide the JWT Authorization token

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1065
  
Looks good @YolandaMDavis! This has been merged to master. Thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #1042: NIFI-2795 Sys Diagnostics in Cluster UI

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1042
  
@mcgilman Your changes look good to me.  I had noticed that filter 
behavior, but I wasn't sure how intentional it was.  Your fix does allow 
filtering by the full address or status text as displayed, rather than just one 
column value, and that seems more intuitive to users.  

Should I merge that commit into the PR branch?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #1065: NIFI-2822 - Provide the JWT Authorization token

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1065
  
Reviewing...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #1061: Backport NIFI-2728 to 0.x tree

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1061
  
Thanks @trixpan! This has been merged to the 0.x branch. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2728) Travis CI experiences GC overhead limit exceeded

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-2728:
---

Commit 4e6f9d39652f78db5840129ea5d49eddffb62e0e in nifi's branch refs/heads/0.x 
from Andre F de Miranda
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=4e6f9d3 ]

Backport NIFI-2728 to 0.x tree. This closes #1061


> Travis CI experiences GC overhead limit exceeded 
> -
>
> Key: NIFI-2728
> URL: https://issues.apache.org/jira/browse/NIFI-2728
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Andre
>
> travis-ci is currently broken and frequently reporting 
> {{GC overhead limit exceeded}}



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

[jira] [Commented] (NIFI-2639) Update graphics in "Apache NiFi In Depth" doc

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2639:
--

GitHub user andrewmlim opened a pull request:

https://github.com/apache/nifi/pull/1067

NIFI-2639 Update NiFi In Depth Doc: made text edits and replaced scre…

…enshots with new UI

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

$ git pull https://github.com/andrewmlim/nifi NIFI-2639

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

https://github.com/apache/nifi/pull/1067.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 #1067


commit 2c059471a30d59b022cfd787031fd196d45a6e55
Author: Andrew Lim 
Date:   2016-09-26T18:36:55Z

NIFI-2639 Update NiFi In Depth Doc: made text edits and replaced 
screenshots with new UI




> Update graphics in "Apache NiFi In Depth" doc
> -
>
> Key: NIFI-2639
> URL: https://issues.apache.org/jira/browse/NIFI-2639
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Joseph Percivall
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.1.0
>
>
> There are a number of graphics in the "Apache NiFi In Depth" that are screen 
> shots of a flow that currently are of the 0.x UI. 
> For aesthetics purposes, these should be updated using the new UI .



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

[GitHub] nifi pull request #1067: NIFI-2639 Update NiFi In Depth Doc: made text edits...

[andrewmlim]

GitHub user andrewmlim opened a pull request:

https://github.com/apache/nifi/pull/1067

NIFI-2639 Update NiFi In Depth Doc: made text edits and replaced scre…

…enshots with new UI

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

$ git pull https://github.com/andrewmlim/nifi NIFI-2639

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

https://github.com/apache/nifi/pull/1067.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 #1067


commit 2c059471a30d59b022cfd787031fd196d45a6e55
Author: Andrew Lim 
Date:   2016-09-26T18:36:55Z

NIFI-2639 Update NiFi In Depth Doc: made text edits and replaced 
screenshots with new UI




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2823) tls-toolkit standalone should allow DN specification

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2823:
--

GitHub user brosander opened a pull request:

https://github.com/apache/nifi/pull/1066

NIFI-2823 - Adding nifiDnPrefix, nifiDnSuffix options to standalone t…

…ls-toolkit

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

$ git pull https://github.com/brosander/nifi NIFI-2823

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

https://github.com/apache/nifi/pull/1066.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 #1066


commit 07f0c9242e46cd26e938b96704cc30b913152d78
Author: Bryan Rosander 
Date:   2016-09-26T18:16:19Z

NIFI-2823 - Adding nifiDnPrefix, nifiDnSuffix options to standalone 
tls-toolkit




> tls-toolkit standalone should allow DN specification
> 
>
> Key: NIFI-2823
> URL: https://issues.apache.org/jira/browse/NIFI-2823
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>
> When running the tls-toolkit in standalone mode, users should be able to 
> specify a DN for the nifi instance



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

[GitHub] nifi pull request #1066: NIFI-2823 - Adding nifiDnPrefix, nifiDnSuffix optio...

[brosander]

GitHub user brosander opened a pull request:

https://github.com/apache/nifi/pull/1066

NIFI-2823 - Adding nifiDnPrefix, nifiDnSuffix options to standalone t…

…ls-toolkit

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

$ git pull https://github.com/brosander/nifi NIFI-2823

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

https://github.com/apache/nifi/pull/1066.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 #1066


commit 07f0c9242e46cd26e938b96704cc30b913152d78
Author: Bryan Rosander 
Date:   2016-09-26T18:16:19Z

NIFI-2823 - Adding nifiDnPrefix, nifiDnSuffix options to standalone 
tls-toolkit




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2795) Enhance Cluster UI with System Diagnostics

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2795:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1042
  
@jvwing While reviewing I stumbled into an existing bug filtering the 
tables in the cluster page. I've addressed it here [1]. Hoping you could just 
review what I did so I could include it in your PR. 

Thanks!

[1] 
https://github.com/mcgilman/nifi/commit/45d9fc33054a5696b67bec7a934a4e4500a01ad5


> Enhance Cluster UI with System Diagnostics
> --
>
> Key: NIFI-2795
> URL: https://issues.apache.org/jira/browse/NIFI-2795
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Attachments: cluster-01-nodes.png, cluster-02-system.png, 
> cluster-03-jvm.png, cluster-04-flowfile-store.png, 
> cluster-05-content-store.png
>
>
> The Cluster UI currently provides some basic information on each node in the 
> cluster and options for connecting and disconnecting nodes. I propose to add 
> system diagnostics information in tables, contained in multiple tabs.  
> Roughly, the tabs should cover the same content as the System Diagnostics 
> dialog already in the System UI, but in a tabular format for comparing across 
> nodes.



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

[jira] [Updated] (NIFI-2824) Errors encountered when saving from Advanced UI (UpdateAttribute, JoltTransformProcessor)

[Yolanda M. Davis (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yolanda M. Davis updated NIFI-2824:
---
Summary: Errors encountered when saving from Advanced UI (UpdateAttribute, 
JoltTransformProcessor)  (was: Errors encountered when saving from Advanced UI 
(UpdateAttributes, JoltTransformProcessor))

> Errors encountered when saving from Advanced UI (UpdateAttribute, 
> JoltTransformProcessor)
> -
>
> Key: NIFI-2824
> URL: https://issues.apache.org/jira/browse/NIFI-2824
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Yolanda M. Davis
>
> When attempting to save configuration changes using the Advanced UI for 
> UpdateAttributes or JoltTransformProcessor the following example exception 
> stack trace was encountered in a secured clustered environment (e.g. 
> Transaction already in progress):
> Received a status of 409 from ydavis-ldap-nifi-demo-1.openstacklocal:9091 for 
> request PUT /nifi-api/processors/66ce1842-0157-1000--7e910d9e when 
> performing first stage of two-stage commit. The action will not occur. Node 
> explanation: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
> 2016-09-26 16:07:43,445 ERROR [NiFi Web Server-22] 
> c.s.j.spi.container.ContainerResponse The RuntimeException could not be 
> mapped to a response, re-throwing to the HTTP container
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> 2016-09-26 16:07:43,454 WARN [NiFi Web Server-22] 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.1.0-SNAPSHOT/api/standard/processor/properties
> org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
> ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
> due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
> progress.
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
>  ~[na:na]
>   at 
> org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
>  ~[na:na]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> ~[na:1.8.0_77]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  ~[na:1.8.0_77]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ~[na:1.8.0_77]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]



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

[jira] [Commented] (NIFI-2341) Create a processor to parse logs formated using CEF

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2341:
--

Github user mattyb149 commented on a diff in the pull request:

https://github.com/apache/nifi/pull/785#discussion_r80535518
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ParseCEF.java
 ---
@@ -0,0 +1,323 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.nifi.processors.standard;
+
+import com.fasterxml.jackson.core.JsonGenerator;
+import com.fasterxml.jackson.core.JsonProcessingException;
+import com.fasterxml.jackson.databind.JsonSerializer;
+import com.fasterxml.jackson.databind.ObjectMapper;
+import com.fasterxml.jackson.databind.SerializerProvider;
+import com.fasterxml.jackson.databind.module.SimpleModule;
+
+import com.fasterxml.jackson.databind.node.ObjectNode;
+import com.fluenda.parcefone.event.CEFHandlingException;
+import com.fluenda.parcefone.event.CommonEvent;
+import com.fluenda.parcefone.parser.CEFParser;
+
+import com.martiansoftware.macnificent.MacAddress;
+
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.behavior.SideEffectFree;
+import org.apache.nifi.annotation.behavior.SupportsBatching;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.SeeAlso;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.io.InputStreamCallback;
+import org.apache.nifi.processor.io.OutputStreamCallback;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.stream.io.BufferedOutputStream;
+import org.apache.nifi.stream.io.StreamUtils;
+
+import java.io.IOException;
+import java.io.InputStream;
+import java.io.OutputStream;
+import java.net.InetAddress;
+import java.text.SimpleDateFormat;
+import java.time.ZoneId;
+import java.time.ZonedDateTime;
+import java.time.format.DateTimeFormatter;
+import java.util.ArrayList;
+import java.util.Date;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+import java.util.TimeZone;
+
+@EventDriven
+@SideEffectFree
+@SupportsBatching
+@InputRequirement(Requirement.INPUT_REQUIRED)
+@Tags({"logs", "cef", "attributes", "system", "event", "message"})
+@CapabilityDescription("Parses the contents of a CEF formatted message and 
adds attributes to the FlowFile for " +
+"headers and extensions of the parts of the CEF message.\n" +
+"Note: This Processor expects CEF messages WITHOUT the syslog 
headers (i.e. starting at \"CEF:0\"")
+@WritesAttributes({@WritesAttribute(attribute = "cef.header.version", 
description = "The version of the CEF message."),
+@WritesAttribute(attribute = "cef.header.deviceVendor", description = 
"The Device Vendor of the CEF message."),
+@WritesAttribute(attribute = "cef.header.deviceProduct", description = 
"The Device Product of the CEF message."),
+@WritesAttribute(attribute = 

[jira] [Commented] (NIFI-2341) Create a processor to parse logs formated using CEF

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2341:
--

Github user mattyb149 commented on a diff in the pull request:

https://github.com/apache/nifi/pull/785#discussion_r80535990
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestParseCEF.java
 ---
@@ -0,0 +1,186 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.nifi.processors.standard;
+
+import com.fasterxml.jackson.databind.JsonNode;
+import com.fasterxml.jackson.databind.ObjectMapper;
+import org.apache.nifi.util.MockFlowFile;
+import org.apache.nifi.util.TestRunner;
+import org.apache.nifi.util.TestRunners;
+import org.junit.Assert;
+import org.junit.Test;
+
+import java.io.IOException;
+import java.text.SimpleDateFormat;
+import java.util.Date;
+import java.util.TimeZone;
+
+
+public class TestParseCEF {
+private SimpleDateFormat sdf = new 
SimpleDateFormat("-MM-dd'T'HH:mm:ss.SSSZ");
+
+private final static String sample1 = 
"CEF:0|TestVendor|TestProduct|TestVersion|TestEventClassID|TestName|Low|" +
+// TimeStamp, String and Long
+"rt=Feb 09 2015 00:27:43 UTC cn3Label=Test Long 
cn3=9223372036854775807 " +
+// FloatPoint and MacAddress
+"cfp1=1.234 cfp1Label=Test FP Number smac=00:00:0c:07:ac:00 " +
+// IPv6 and String
+"c6a3=2001:cdba::3257:9652 c6a3Label=Test IPv6 " +
+// IPv4
+"destinationTranslatedAddress=123.123.123.123 " +
+// Date without TZ
+"deviceCustomDate1=Feb 06 2015 13:27:43 " +
+// Integer  and IP Address (from v4)
+"dpt=1234 agt=123.123.0.124 dlat=40.366633";
+
+@Test
+public void testInvalidMessage() {
--- End diff --

Are there any other inputs or properties that could cause a different 
error? If so additional tests would be nice (for illustration and regression 
purposes).


> Create a processor to parse logs formated using CEF
> ---
>
> Key: NIFI-2341
> URL: https://issues.apache.org/jira/browse/NIFI-2341
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> As NiFi continue to increase its abilities to complement SIEM, Splunk and ELK 
> deployments, a number of users will be looking to parse CEF formatted 
> logs[1][2].
> CEF is a format specified by Arcsight (now part of HPE) and is described in 
> detail in here:
> https://www.protect724.hpe.com/docs/DOC-1072
> [1] 
> http://apache-nifi.1125220.n5.nabble.com/Suggestion-of-processors-td9795.html
> [2] 
> https://community.hortonworks.com/questions/43185/which-processor-is-used-to-parse-cef-format-logs.html



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

[jira] [Commented] (NIFI-2341) Create a processor to parse logs formated using CEF

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2341:
--

Github user mattyb149 commented on a diff in the pull request:

https://github.com/apache/nifi/pull/785#discussion_r80535718
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutSQL.java
 ---
@@ -819,7 +819,7 @@ private void setParameter(final PreparedStatement stmt, 
final String attrName, f
 bValue = 
DatatypeConverter.parseBase64Binary(parameterValue);
 break;
 default:
-throw new ParseException("Unable to parse 
binary data using the formatter `" + valueFormat + "`.",0);
+throw new ParseException("Unable to parse 
binary data using the simpleDateFormat `" + valueFormat + "`.",0);
--- End diff --

This change looks odd (no other reference to such things), perhaps a rebase 
is needed? Or maybe a search-and-replace ran rampant and this file should be 
removed from the PR?


> Create a processor to parse logs formated using CEF
> ---
>
> Key: NIFI-2341
> URL: https://issues.apache.org/jira/browse/NIFI-2341
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> As NiFi continue to increase its abilities to complement SIEM, Splunk and ELK 
> deployments, a number of users will be looking to parse CEF formatted 
> logs[1][2].
> CEF is a format specified by Arcsight (now part of HPE) and is described in 
> detail in here:
> https://www.protect724.hpe.com/docs/DOC-1072
> [1] 
> http://apache-nifi.1125220.n5.nabble.com/Suggestion-of-processors-td9795.html
> [2] 
> https://community.hortonworks.com/questions/43185/which-processor-is-used-to-parse-cef-format-logs.html



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

[GitHub] nifi pull request #785: NIFI-2341 - Introduce ParseCEF processor

[mattyb149]

Github user mattyb149 commented on a diff in the pull request:

https://github.com/apache/nifi/pull/785#discussion_r80535518
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ParseCEF.java
 ---
@@ -0,0 +1,323 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.nifi.processors.standard;
+
+import com.fasterxml.jackson.core.JsonGenerator;
+import com.fasterxml.jackson.core.JsonProcessingException;
+import com.fasterxml.jackson.databind.JsonSerializer;
+import com.fasterxml.jackson.databind.ObjectMapper;
+import com.fasterxml.jackson.databind.SerializerProvider;
+import com.fasterxml.jackson.databind.module.SimpleModule;
+
+import com.fasterxml.jackson.databind.node.ObjectNode;
+import com.fluenda.parcefone.event.CEFHandlingException;
+import com.fluenda.parcefone.event.CommonEvent;
+import com.fluenda.parcefone.parser.CEFParser;
+
+import com.martiansoftware.macnificent.MacAddress;
+
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.behavior.SideEffectFree;
+import org.apache.nifi.annotation.behavior.SupportsBatching;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.SeeAlso;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.io.InputStreamCallback;
+import org.apache.nifi.processor.io.OutputStreamCallback;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.stream.io.BufferedOutputStream;
+import org.apache.nifi.stream.io.StreamUtils;
+
+import java.io.IOException;
+import java.io.InputStream;
+import java.io.OutputStream;
+import java.net.InetAddress;
+import java.text.SimpleDateFormat;
+import java.time.ZoneId;
+import java.time.ZonedDateTime;
+import java.time.format.DateTimeFormatter;
+import java.util.ArrayList;
+import java.util.Date;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+import java.util.TimeZone;
+
+@EventDriven
+@SideEffectFree
+@SupportsBatching
+@InputRequirement(Requirement.INPUT_REQUIRED)
+@Tags({"logs", "cef", "attributes", "system", "event", "message"})
+@CapabilityDescription("Parses the contents of a CEF formatted message and 
adds attributes to the FlowFile for " +
+"headers and extensions of the parts of the CEF message.\n" +
+"Note: This Processor expects CEF messages WITHOUT the syslog 
headers (i.e. starting at \"CEF:0\"")
+@WritesAttributes({@WritesAttribute(attribute = "cef.header.version", 
description = "The version of the CEF message."),
+@WritesAttribute(attribute = "cef.header.deviceVendor", description = 
"The Device Vendor of the CEF message."),
+@WritesAttribute(attribute = "cef.header.deviceProduct", description = 
"The Device Product of the CEF message."),
+@WritesAttribute(attribute = "cef.header.deviceVersion", description = 
"The Device Version of the CEF message."),
+@WritesAttribute(attribute = "cef.header.deviceEventClassId", 
description = "The Device Event Class ID of the CEF message."),
+

[GitHub] nifi pull request #785: NIFI-2341 - Introduce ParseCEF processor

[mattyb149]

Github user mattyb149 commented on a diff in the pull request:

https://github.com/apache/nifi/pull/785#discussion_r80535718
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutSQL.java
 ---
@@ -819,7 +819,7 @@ private void setParameter(final PreparedStatement stmt, 
final String attrName, f
 bValue = 
DatatypeConverter.parseBase64Binary(parameterValue);
 break;
 default:
-throw new ParseException("Unable to parse 
binary data using the formatter `" + valueFormat + "`.",0);
+throw new ParseException("Unable to parse 
binary data using the simpleDateFormat `" + valueFormat + "`.",0);
--- End diff --

This change looks odd (no other reference to such things), perhaps a rebase 
is needed? Or maybe a search-and-replace ran rampant and this file should be 
removed from the PR?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request #785: NIFI-2341 - Introduce ParseCEF processor

[mattyb149]

Github user mattyb149 commented on a diff in the pull request:

https://github.com/apache/nifi/pull/785#discussion_r80535990
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestParseCEF.java
 ---
@@ -0,0 +1,186 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.nifi.processors.standard;
+
+import com.fasterxml.jackson.databind.JsonNode;
+import com.fasterxml.jackson.databind.ObjectMapper;
+import org.apache.nifi.util.MockFlowFile;
+import org.apache.nifi.util.TestRunner;
+import org.apache.nifi.util.TestRunners;
+import org.junit.Assert;
+import org.junit.Test;
+
+import java.io.IOException;
+import java.text.SimpleDateFormat;
+import java.util.Date;
+import java.util.TimeZone;
+
+
+public class TestParseCEF {
+private SimpleDateFormat sdf = new 
SimpleDateFormat("-MM-dd'T'HH:mm:ss.SSSZ");
+
+private final static String sample1 = 
"CEF:0|TestVendor|TestProduct|TestVersion|TestEventClassID|TestName|Low|" +
+// TimeStamp, String and Long
+"rt=Feb 09 2015 00:27:43 UTC cn3Label=Test Long 
cn3=9223372036854775807 " +
+// FloatPoint and MacAddress
+"cfp1=1.234 cfp1Label=Test FP Number smac=00:00:0c:07:ac:00 " +
+// IPv6 and String
+"c6a3=2001:cdba::3257:9652 c6a3Label=Test IPv6 " +
+// IPv4
+"destinationTranslatedAddress=123.123.123.123 " +
+// Date without TZ
+"deviceCustomDate1=Feb 06 2015 13:27:43 " +
+// Integer  and IP Address (from v4)
+"dpt=1234 agt=123.123.0.124 dlat=40.366633";
+
+@Test
+public void testInvalidMessage() {
--- End diff --

Are there any other inputs or properties that could cause a different 
error? If so additional tests would be nice (for illustration and regression 
purposes).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2822) JoltTransformer Advanced UI doesn't load in a secured cluster

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2822:
--

GitHub user YolandaMDavis opened a pull request:

https://github.com/apache/nifi/pull/1065

NIFI-2822 - Provide the JWT Authorization token 

This change ensures that the JWT token used for authorization is added to 
headers when using the $http service.  Testing requires a secured server.

The Jolt Transform Advanced UI should appear, and validate/format/transform 
operation  should work. However a separate JIRA was filed (NIFI-2824) in order 
to handle a separate problem related to saving that was found during testing:

https://issues.apache.org/jira/browse/NIFI-2824

This problem also impacts saving the UpdateAttributes processor. It does 
not appear related to the token issue.

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

$ git pull https://github.com/YolandaMDavis/nifi NIFI-2822

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

https://github.com/apache/nifi/pull/1065.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 #1065


commit 2de95b7cf853b94e6de2fdb13ed40fe9fea65593
Author: Yolanda M. Davis 
Date:   2016-09-26T16:11:28Z

NIFI-2822 - pass the JWT Authorization token i




> JoltTransformer Advanced UI doesn't load in a secured cluster
> -
>
> Key: NIFI-2822
> URL: https://issues.apache.org/jira/browse/NIFI-2822
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: LDAP-secured 3 node NiFi cluster
>Reporter: Andrew Grande
>Assignee: Yolanda M. Davis
>
> JoltTransformer -> click Advanced. The UI doesn't load - "An error has 
> occurred loading the editor."
> The error on the backend is below, doesn't seem to pass authorization tokens 
> at all, lists 'anonymous':
> {noformat}
> 2016-09-26 09:19:16,794 WARN NiFi Web Server-74433 - 
> org.eclipse.jetty.servlet.ServletHandler 
> /nifi-jolt-transform-json-ui-1.0.0.2.0.0.0-579/api/standard/processor/details
> org.apache.nifi.authorization.AccessDeniedException: Unknown user with 
> identity 'anonymous'.
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:166)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:163)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.authorization.resource.Authorizable.authorize(Authorizable.java:179)
>  ~[nifi-framework-api-1.0.0.2.0.0.0-579.jar:1.0.0.2.0.0.0-579]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.lambda$getComponentDetails$0(StandardNiFiWebConfigurationContext.java:342)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade.authorizeAccess(StandardNiFiServiceFacade.java:289)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke()
>  ~[na:na]
>   at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) 
> ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
>  ~[na:na]
>   at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>  ~[na:na]
>   at 
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiServiceFacade$$EnhancerBySpringCGLIB$$80c8c166.authorizeAccess()
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext$ProcessorFacade.getComponentDetails(StandardNiFiWebConfigurationContext.java:340)
>  ~[na:na]
>   at 
> org.apache.nifi.web.StandardNiFiWebConfigurationContext.getComponentDetails(StandardNiFiWebConfigurationContext.java:256)
>  ~[na:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:47)
>  ~[classes/:na]
>   at 
> org.apache.nifi.web.standard.api.processor.ProcessorWebUtils.getComponentDetails(ProcessorWebUtils.java:52)
>  ~[classes/:na]
>   at 
> 

[GitHub] nifi pull request #1065: NIFI-2822 - Provide the JWT Authorization token

[YolandaMDavis]

GitHub user YolandaMDavis opened a pull request:

https://github.com/apache/nifi/pull/1065

NIFI-2822 - Provide the JWT Authorization token 

This change ensures that the JWT token used for authorization is added to 
headers when using the $http service.  Testing requires a secured server.

The Jolt Transform Advanced UI should appear, and validate/format/transform 
operation  should work. However a separate JIRA was filed (NIFI-2824) in order 
to handle a separate problem related to saving that was found during testing:

https://issues.apache.org/jira/browse/NIFI-2824

This problem also impacts saving the UpdateAttributes processor. It does 
not appear related to the token issue.

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

$ git pull https://github.com/YolandaMDavis/nifi NIFI-2822

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

https://github.com/apache/nifi/pull/1065.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 #1065


commit 2de95b7cf853b94e6de2fdb13ed40fe9fea65593
Author: Yolanda M. Davis 
Date:   2016-09-26T16:11:28Z

NIFI-2822 - pass the JWT Authorization token i




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-2824) Errors encountered when saving from Advanced UI (UpdateAttributes, JoltTransformProcessor)

[Yolanda M. Davis (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yolanda M. Davis updated NIFI-2824:
---
Description: 
When attempting to save configuration changes using the Advanced UI for 
UpdateAttributes or JoltTransformProcessor the following example exception 
stack trace was encountered in a secured clustered environment (e.g. 
Transaction already in progress):

Received a status of 409 from ydavis-ldap-nifi-demo-1.openstacklocal:9091 for 
request PUT /nifi-api/processors/66ce1842-0157-1000--7e910d9e when 
performing first stage of two-stage commit. The action will not occur. Node 
explanation: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
progress.
2016-09-26 16:07:43,445 ERROR [NiFi Web Server-22] 
c.s.j.spi.container.ContainerResponse The RuntimeException could not be mapped 
to a response, re-throwing to the HTTP container
org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in progress.
  at 
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
 ~[na:na]
  at 
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
 ~[na:na]
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
~[na:1.8.0_77]
  at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
~[na:1.8.0_77]
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
~[na:1.8.0_77]
  at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
2016-09-26 16:07:43,454 WARN [NiFi Web Server-22] 
org.eclipse.jetty.servlet.ServletHandler 
/nifi-jolt-transform-json-ui-1.1.0-SNAPSHOT/api/standard/processor/properties
org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in progress.
  at 
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
 ~[na:na]
  at 
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
 ~[na:na]
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
~[na:1.8.0_77]
  at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
~[na:1.8.0_77]
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
~[na:1.8.0_77]
  at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]



  was:
When attempting to save configuration changes using the Advanced UI for 
UpdateAttributes or JoltTransformProcessor the following example exception 
stack trace was encountered (e.g. Transaction already in progress):

Received a status of 409 from ydavis-ldap-nifi-demo-1.openstacklocal:9091 for 
request PUT /nifi-api/processors/66ce1842-0157-1000--7e910d9e when 
performing first stage of two-stage commit. The action will not occur. Node 
explanation: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
progress.
2016-09-26 16:07:43,445 ERROR [NiFi Web Server-22] 
c.s.j.spi.container.ContainerResponse The RuntimeException could not be mapped 
to a response, re-throwing to the HTTP container
org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in progress.
  at 
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
 ~[na:na]
  at 
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
 ~[na:na]
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
~[na:1.8.0_77]
  at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
~[na:1.8.0_77]
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
~[na:1.8.0_77]
  at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
2016-09-26 16:07:43,454 WARN [NiFi Web Server-22] 
org.eclipse.jetty.servlet.ServletHandler 
/nifi-jolt-transform-json-ui-1.1.0-SNAPSHOT/api/standard/processor/properties

[GitHub] nifi-minifi-cpp pull request #13: MINIFI-109: Add ExecuteProcess

[benqiu2016]

GitHub user benqiu2016 opened a pull request:

https://github.com/apache/nifi-minifi-cpp/pull/13

MINIFI-109: Add ExecuteProcess



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

$ git pull https://github.com/benqiu2016/nifi-minifi-cpp 
excecute_process_merge

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

https://github.com/apache/nifi-minifi-cpp/pull/13.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 #13


commit 2e1b7599d6f59d014587c8db3890ac0843942a99
Author: Bin Qiu 
Date:   2016-09-26T17:42:54Z

MINIFI-109: Add ExecuteProcess




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2277) Policies: Get an "An unexpected type of resource in this policy /flow" error trying to access global policies

[Andrew Lim (JIRA)]

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

Andrew Lim commented on NIFI-2277:
--

[~scottyaslan] Will check it out.  Thanks!

> Policies:  Get an "An unexpected type of resource in this policy /flow" error 
> trying to access global policies
> --
>
> Key: NIFI-2277
> URL: https://issues.apache.org/jira/browse/NIFI-2277
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>  Labels: UI
> Attachments: NIFI-2277_globalError.png
>
>
> Launched secured NiFi instance.  If I immediately select "Policies" from the 
> control menu, the Access Policies window is displayed as expected.
> If I select a processor on the canvas that I do not have view policies on, I 
> get an error (https://issues.apache.org/jira/browse/NIFI-2273).  Now if I 
> select "Policies" from the control menu, I get an error:
> An unexpected type of resource in this policy /flow
> See attached screenshot.
> Here is the link to this error in my NiFi instance:
> https://localhost:8443/nifi-api/policies/read/flow/6bbc2432-9896-4bf2-ba2d-fa379d91684e



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

[jira] [Updated] (NIFI-2277) Policies: Get an "An unexpected type of resource in this policy /flow" error trying to access global policies

[Andrew Lim (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Lim updated NIFI-2277:
-
Assignee: Andrew Lim  (was: Scott Aslan)

> Policies:  Get an "An unexpected type of resource in this policy /flow" error 
> trying to access global policies
> --
>
> Key: NIFI-2277
> URL: https://issues.apache.org/jira/browse/NIFI-2277
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>  Labels: UI
> Attachments: NIFI-2277_globalError.png
>
>
> Launched secured NiFi instance.  If I immediately select "Policies" from the 
> control menu, the Access Policies window is displayed as expected.
> If I select a processor on the canvas that I do not have view policies on, I 
> get an error (https://issues.apache.org/jira/browse/NIFI-2273).  Now if I 
> select "Policies" from the control menu, I get an error:
> An unexpected type of resource in this policy /flow
> See attached screenshot.
> Here is the link to this error in my NiFi instance:
> https://localhost:8443/nifi-api/policies/read/flow/6bbc2432-9896-4bf2-ba2d-fa379d91684e



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

[jira] [Assigned] (NIFI-1758) Unable to scroll in the Comments field

[Scott Aslan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Aslan reassigned NIFI-1758:
-

Assignee: Scott Aslan

> Unable to scroll in the Comments field
> --
>
> Key: NIFI-1758
> URL: https://issues.apache.org/jira/browse/NIFI-1758
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.6.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
>
> Example:  when configuring a process group, the Comments field allows a large 
> amount of text to be entered or pasted in.  The size of the comments field 
> displays about 6-7 rows (depending on what web browser is being used).  
> However, scrolling is not allowed for that field, so the user is unable to 
> easily see or edit the values in the field.
> A workaround is to use the keyboard arrow keys.



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

[jira] [Resolved] (NIFI-1758) Unable to scroll in the Comments field

[Scott Aslan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Aslan resolved NIFI-1758.
---
Resolution: Fixed

> Unable to scroll in the Comments field
> --
>
> Key: NIFI-1758
> URL: https://issues.apache.org/jira/browse/NIFI-1758
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.6.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
>
> Example:  when configuring a process group, the Comments field allows a large 
> amount of text to be entered or pasted in.  The size of the comments field 
> displays about 6-7 rows (depending on what web browser is being used).  
> However, scrolling is not allowed for that field, so the user is unable to 
> easily see or edit the values in the field.
> A workaround is to use the keyboard arrow keys.



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

[jira] [Created] (NIFI-2824) Errors encountered when saving from Advanced UI (UpdateAttributes, JoltTransformProcessor)

[Yolanda M. Davis (JIRA)]

Yolanda M. Davis created NIFI-2824:
--

 Summary: Errors encountered when saving from Advanced UI 
(UpdateAttributes, JoltTransformProcessor)
 Key: NIFI-2824
 URL: https://issues.apache.org/jira/browse/NIFI-2824
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Yolanda M. Davis


When attempting to save configuration changes using the Advanced UI for 
UpdateAttributes or JoltTransformProcessor the following example exception 
stack trace was encountered (e.g. Transaction already in progress):

Received a status of 409 from ydavis-ldap-nifi-demo-1.openstacklocal:9091 for 
request PUT /nifi-api/processors/66ce1842-0157-1000--7e910d9e when 
performing first stage of two-stage commit. The action will not occur. Node 
explanation: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in 
progress.
2016-09-26 16:07:43,445 ERROR [NiFi Web Server-22] 
c.s.j.spi.container.ContainerResponse The RuntimeException could not be mapped 
to a response, re-throwing to the HTTP container
org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in progress.
  at 
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
 ~[na:na]
  at 
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
 ~[na:na]
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
~[na:1.8.0_77]
  at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
~[na:1.8.0_77]
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
~[na:1.8.0_77]
  at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
2016-09-26 16:07:43,454 WARN [NiFi Web Server-22] 
org.eclipse.jetty.servlet.ServletHandler 
/nifi-jolt-transform-json-ui-1.1.0-SNAPSHOT/api/standard/processor/properties
org.apache.nifi.cluster.manager.exception.IllegalClusterStateException: Node 
ydavis-ldap-nifi-demo-1.openstacklocal:9091 is unable to fulfill this request 
due to: Transaction d12cd676-5140-4f1a-95c3-5e44689f2b37 is already in progress.
  at 
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$2.onCompletion(ThreadPoolRequestReplicator.java:473)
 ~[na:na]
  at 
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:729)
 ~[na:na]
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
~[na:1.8.0_77]
  at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_77]
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
~[na:1.8.0_77]
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
~[na:1.8.0_77]
  at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]





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

[jira] [Updated] (NIFI-2803) The pagination of GenerateTableFetch has a sort bug.

[Matt Burgess (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess updated NIFI-2803:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> The pagination of GenerateTableFetch has a sort bug.
> 
>
> Key: NIFI-2803
> URL: https://issues.apache.org/jira/browse/NIFI-2803
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Byunghwa Yun
> Fix For: 1.1.0
>
>
> When data is coming to the ingested table, the pagination SQL needs the ORDER 
> BY statement with maxValueClauses.
> If maxValueClauses are not the primary keys, incoming data usually inserts  
> using primary keys. So when ExecuteSQL executes, some data may be lost.



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

[jira] [Commented] (NIFI-2803) The pagination of GenerateTableFetch has a sort bug.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2803:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1052


> The pagination of GenerateTableFetch has a sort bug.
> 
>
> Key: NIFI-2803
> URL: https://issues.apache.org/jira/browse/NIFI-2803
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Byunghwa Yun
> Fix For: 1.1.0
>
>
> When data is coming to the ingested table, the pagination SQL needs the ORDER 
> BY statement with maxValueClauses.
> If maxValueClauses are not the primary keys, incoming data usually inserts  
> using primary keys. So when ExecuteSQL executes, some data may be lost.



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

[jira] [Commented] (NIFI-2803) The pagination of GenerateTableFetch has a sort bug.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-2803:
---

Commit 88682359937afbc0e48df769c296606316c7b1d0 in nifi's branch 
refs/heads/master from [~combine]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8868235 ]

NIFI-2803 The pagination of GenerateTableFetch has a sort bug.

Signed-off-by: Matt Burgess 

NIFI-2803: Updated unit tests for GenerateTableFetch

Signed-off-by: Matt Burgess 

This closes #1052


> The pagination of GenerateTableFetch has a sort bug.
> 
>
> Key: NIFI-2803
> URL: https://issues.apache.org/jira/browse/NIFI-2803
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Byunghwa Yun
> Fix For: 1.1.0
>
>
> When data is coming to the ingested table, the pagination SQL needs the ORDER 
> BY statement with maxValueClauses.
> If maxValueClauses are not the primary keys, incoming data usually inserts  
> using primary keys. So when ExecuteSQL executes, some data may be lost.



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

[jira] [Commented] (NIFI-2803) The pagination of GenerateTableFetch has a sort bug.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-2803:
---

Commit 88682359937afbc0e48df769c296606316c7b1d0 in nifi's branch 
refs/heads/master from [~combine]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8868235 ]

NIFI-2803 The pagination of GenerateTableFetch has a sort bug.

Signed-off-by: Matt Burgess 

NIFI-2803: Updated unit tests for GenerateTableFetch

Signed-off-by: Matt Burgess 

This closes #1052


> The pagination of GenerateTableFetch has a sort bug.
> 
>
> Key: NIFI-2803
> URL: https://issues.apache.org/jira/browse/NIFI-2803
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Byunghwa Yun
> Fix For: 1.1.0
>
>
> When data is coming to the ingested table, the pagination SQL needs the ORDER 
> BY statement with maxValueClauses.
> If maxValueClauses are not the primary keys, incoming data usually inserts  
> using primary keys. So when ExecuteSQL executes, some data may be lost.



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

[GitHub] nifi pull request #1052: NIFI-2803 The pagination of GenerateTableFetch has ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1052


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #1052: NIFI-2803 The pagination of GenerateTableFetch has a sort ...

[mattyb149]

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1052
  
This commit breaks some unit tests that check the SQL statement(s) being 
generated, I will fix the tests before merging. Otherwise +1 LGTM, merging to 
master, thanks much for your contribution!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2803) The pagination of GenerateTableFetch has a sort bug.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2803:
--

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1052
  
This commit breaks some unit tests that check the SQL statement(s) being 
generated, I will fix the tests before merging. Otherwise +1 LGTM, merging to 
master, thanks much for your contribution!


> The pagination of GenerateTableFetch has a sort bug.
> 
>
> Key: NIFI-2803
> URL: https://issues.apache.org/jira/browse/NIFI-2803
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Byunghwa Yun
> Fix For: 1.1.0
>
>
> When data is coming to the ingested table, the pagination SQL needs the ORDER 
> BY statement with maxValueClauses.
> If maxValueClauses are not the primary keys, incoming data usually inserts  
> using primary keys. So when ExecuteSQL executes, some data may be lost.



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

[jira] [Commented] (NIFI-2803) The pagination of GenerateTableFetch has a sort bug.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2803:
--

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1052
  
Reviewing...


> The pagination of GenerateTableFetch has a sort bug.
> 
>
> Key: NIFI-2803
> URL: https://issues.apache.org/jira/browse/NIFI-2803
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Byunghwa Yun
> Fix For: 1.1.0
>
>
> When data is coming to the ingested table, the pagination SQL needs the ORDER 
> BY statement with maxValueClauses.
> If maxValueClauses are not the primary keys, incoming data usually inserts  
> using primary keys. So when ExecuteSQL executes, some data may be lost.



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

[jira] [Updated] (NIFI-2803) The pagination of GenerateTableFetch has a sort bug.

[Matt Burgess (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess updated NIFI-2803:
---
Fix Version/s: 1.1.0

> The pagination of GenerateTableFetch has a sort bug.
> 
>
> Key: NIFI-2803
> URL: https://issues.apache.org/jira/browse/NIFI-2803
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Byunghwa Yun
> Fix For: 1.1.0
>
>
> When data is coming to the ingested table, the pagination SQL needs the ORDER 
> BY statement with maxValueClauses.
> If maxValueClauses are not the primary keys, incoming data usually inserts  
> using primary keys. So when ExecuteSQL executes, some data may be lost.



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

[GitHub] nifi issue #1052: NIFI-2803 The pagination of GenerateTableFetch has a sort ...

[mattyb149]

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1052
  
Reviewing...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2277) Policies: Get an "An unexpected type of resource in this policy /flow" error trying to access global policies

[Scott Aslan (JIRA)]

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

Scott Aslan commented on NIFI-2277:
---

[~andrewmlim] I am unable to reproduce this. Can you please verify that this is 
no longer an issue?

> Policies:  Get an "An unexpected type of resource in this policy /flow" error 
> trying to access global policies
> --
>
> Key: NIFI-2277
> URL: https://issues.apache.org/jira/browse/NIFI-2277
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>  Labels: UI
> Attachments: NIFI-2277_globalError.png
>
>
> Launched secured NiFi instance.  If I immediately select "Policies" from the 
> control menu, the Access Policies window is displayed as expected.
> If I select a processor on the canvas that I do not have view policies on, I 
> get an error (https://issues.apache.org/jira/browse/NIFI-2273).  Now if I 
> select "Policies" from the control menu, I get an error:
> An unexpected type of resource in this policy /flow
> See attached screenshot.
> Here is the link to this error in my NiFi instance:
> https://localhost:8443/nifi-api/policies/read/flow/6bbc2432-9896-4bf2-ba2d-fa379d91684e



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

[GitHub] nifi pull request #1057: NIFI-2816 - Clean typos across the code

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1057


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Assigned] (NIFI-2277) Policies: Get an "An unexpected type of resource in this policy /flow" error trying to access global policies

[Scott Aslan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Aslan reassigned NIFI-2277:
-

Assignee: Scott Aslan

> Policies:  Get an "An unexpected type of resource in this policy /flow" error 
> trying to access global policies
> --
>
> Key: NIFI-2277
> URL: https://issues.apache.org/jira/browse/NIFI-2277
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>  Labels: UI
> Attachments: NIFI-2277_globalError.png
>
>
> Launched secured NiFi instance.  If I immediately select "Policies" from the 
> control menu, the Access Policies window is displayed as expected.
> If I select a processor on the canvas that I do not have view policies on, I 
> get an error (https://issues.apache.org/jira/browse/NIFI-2273).  Now if I 
> select "Policies" from the control menu, I get an error:
> An unexpected type of resource in this policy /flow
> See attached screenshot.
> Here is the link to this error in my NiFi instance:
> https://localhost:8443/nifi-api/policies/read/flow/6bbc2432-9896-4bf2-ba2d-fa379d91684e



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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-2816:
---

Commit 446cd4470251e6a400fde14eca69db8b10969d40 in nifi's branch 
refs/heads/master from Andre F de Miranda
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=446cd44 ]

NIFI-2816 - Clean typos across the code

This closes #1057.


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1057


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[GitHub] nifi issue #1057: NIFI-2816 - Clean typos across the code

[pvillard31]

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1057
  
Merging...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi-cpp issue #12: Minifi 109

[benqiu2016]

Github user benqiu2016 commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/12
  
@apiri, will do. Thanks.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1057
  
Merging...


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2796) Rest Api Docs - Cluster summary endpoint documentation is wrong

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-2796:
---

Commit 1b88552b4677ceb1dfef0119c9c5a0306761ec95 in nifi's branch 
refs/heads/master from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=1b88552 ]

NIFI-2796:
- Fixing incorrect documentation for the cluster summary endpoint.

This closes #1063.

Signed-off-by: Aldrin Piri 


> Rest Api Docs - Cluster summary endpoint documentation is wrong
> ---
>
> Key: NIFI-2796
> URL: https://issues.apache.org/jira/browse/NIFI-2796
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Documentation & Website
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> Documentation for the cluster summary endpoint should indicate that it 
> returns a ClusterSummaryEntity.



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

[GitHub] nifi pull request #1063: Correcting REST API documentation

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1063


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-2796) Rest Api Docs - Cluster summary endpoint documentation is wrong

[Aldrin Piri (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri updated NIFI-2796:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Rest Api Docs - Cluster summary endpoint documentation is wrong
> ---
>
> Key: NIFI-2796
> URL: https://issues.apache.org/jira/browse/NIFI-2796
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Documentation & Website
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> Documentation for the cluster summary endpoint should indicate that it 
> returns a ClusterSummaryEntity.



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

[jira] [Commented] (NIFI-2796) Rest Api Docs - Cluster summary endpoint documentation is wrong

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2796:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1063


> Rest Api Docs - Cluster summary endpoint documentation is wrong
> ---
>
> Key: NIFI-2796
> URL: https://issues.apache.org/jira/browse/NIFI-2796
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Documentation & Website
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> Documentation for the cluster summary endpoint should indicate that it 
> returns a ClusterSummaryEntity.



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

[GitHub] nifi issue #1063: Correcting REST API documentation

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi/pull/1063
  
changes look good, verified in app.  will merge. thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request #1058: NIFI-2814 - Add ASF header to AppVeyor settings fil...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1058


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2814) Add ASL 2.0 header to appveyor settings

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-2814:
---

Commit be85d9ddff1a3c39631718d936afdf5a6199c335 in nifi's branch 
refs/heads/master from Andre F de Miranda
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=be85d9d ]

NIFI-2814 - Add ASF header to AppVeyor settings file and adjust apache-rat 
accordingly

This closes #1058.

Signed-off-by: Aldrin Piri 


> Add ASL 2.0 header to appveyor settings
> ---
>
> Key: NIFI-2814
> URL: https://issues.apache.org/jira/browse/NIFI-2814
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[GitHub] nifi pull request #1062: Backport NIFI-2814 to 0.x tree

[trixpan]

Github user trixpan closed the pull request at:

https://github.com/apache/nifi/pull/1062


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #1063: Correcting REST API documentation

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi/pull/1063
  
reviewing


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (NIFI-2814) Add ASL 2.0 header to appveyor settings

[Aldrin Piri (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri resolved NIFI-2814.
---
Resolution: Fixed

> Add ASL 2.0 header to appveyor settings
> ---
>
> Key: NIFI-2814
> URL: https://issues.apache.org/jira/browse/NIFI-2814
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2814) Add ASL 2.0 header to appveyor settings

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2814:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi/pull/1062
  
@trixpan this was merged, could you please close?  I think github only does 
automatic closing for master/default branch.


> Add ASL 2.0 header to appveyor settings
> ---
>
> Key: NIFI-2814
> URL: https://issues.apache.org/jira/browse/NIFI-2814
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2814) Add ASL 2.0 header to appveyor settings

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-2814:
---

Commit 5ddf1d70b5ad245b188fb569bdd0f08afd76c23c in nifi's branch refs/heads/0.x 
from Andre F de Miranda
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5ddf1d7 ]

Backport NIFI-2814 to 0.x tree

This closes #1062.

Signed-off-by: Aldrin Piri 


> Add ASL 2.0 header to appveyor settings
> ---
>
> Key: NIFI-2814
> URL: https://issues.apache.org/jira/browse/NIFI-2814
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2814) Add ASL 2.0 header to appveyor settings

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2814:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1058


> Add ASL 2.0 header to appveyor settings
> ---
>
> Key: NIFI-2814
> URL: https://issues.apache.org/jira/browse/NIFI-2814
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2795) Enhance Cluster UI with System Diagnostics

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2795:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1042
  
Reviewing...


> Enhance Cluster UI with System Diagnostics
> --
>
> Key: NIFI-2795
> URL: https://issues.apache.org/jira/browse/NIFI-2795
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Attachments: cluster-01-nodes.png, cluster-02-system.png, 
> cluster-03-jvm.png, cluster-04-flowfile-store.png, 
> cluster-05-content-store.png
>
>
> The Cluster UI currently provides some basic information on each node in the 
> cluster and options for connecting and disconnecting nodes. I propose to add 
> system diagnostics information in tables, contained in multiple tabs.  
> Roughly, the tabs should cover the same content as the System Diagnostics 
> dialog already in the System UI, but in a tabular format for comparing across 
> nodes.



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

[GitHub] nifi issue #1042: NIFI-2795 Sys Diagnostics in Cluster UI

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1042
  
Reviewing...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi pull request #39: MINIFI-81 Adding a check for a valid command t...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi/pull/39


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi pull request #39: MINIFI-81 Adding a check for a valid command t...

[apiri]

Github user apiri commented on a diff in the pull request:

https://github.com/apache/nifi-minifi/pull/39#discussion_r80500315
  
--- Diff: 
minifi-toolkit/minifi-toolkit-configuration/src/main/java/org/apache/nifi/minifi/toolkit/configuration/ConfigMain.java
 ---
@@ -85,8 +85,6 @@ public static void main(String[] args) {
 public static void printValidateUsage() {
 System.out.println("Validate Usage:");
 System.out.println();
-System.out.print("java ");
--- End diff --

fair enough, will merge 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-2803) The pagination of GenerateTableFetch has a sort bug.

[Matt Burgess (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess updated NIFI-2803:
---
Status: Patch Available  (was: Open)

> The pagination of GenerateTableFetch has a sort bug.
> 
>
> Key: NIFI-2803
> URL: https://issues.apache.org/jira/browse/NIFI-2803
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Byunghwa Yun
>
> When data is coming to the ingested table, the pagination SQL needs the ORDER 
> BY statement with maxValueClauses.
> If maxValueClauses are not the primary keys, incoming data usually inserts  
> using primary keys. So when ExecuteSQL executes, some data may be lost.



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

[jira] [Updated] (NIFI-2758) Prevent moving Processor whose Controller Service reference to move out of scope

[Matt Gilman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman updated NIFI-2758:
--
Assignee: Matt Gilman
  Status: Patch Available  (was: Open)

> Prevent moving Processor whose Controller Service reference to move out of 
> scope
> 
>
> Key: NIFI-2758
> URL: https://issues.apache.org/jira/browse/NIFI-2758
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>
> In Apache NiFi 1.0.0, Controller Services became scoped by Process Group. We 
> need to add in a check to ensure that a Processor isn't moved out of a 
> Process Group resulting in a Controller Service that is out of scope.



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

[jira] [Commented] (NIFI-2728) Travis CI experiences GC overhead limit exceeded

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2728:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1061
  
I was just going to comment that I can't seem to get the Java 7 builds to 
pass. Still not sure if it's related to your changes or not though. I'll sit 
tight until you update.

I don't have any issue removing the multi-threaded builds here.

Thanks!


> Travis CI experiences GC overhead limit exceeded 
> -
>
> Key: NIFI-2728
> URL: https://issues.apache.org/jira/browse/NIFI-2728
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Andre
>
> travis-ci is currently broken and frequently reporting 
> {{GC overhead limit exceeded}}



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

[GitHub] nifi issue #1061: Backport NIFI-2728 to 0.x tree

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1061
  
I was just going to comment that I can't seem to get the Java 7 builds to 
pass. Still not sure if it's related to your changes or not though. I'll sit 
tight until you update.

I don't have any issue removing the multi-threaded builds here.

Thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi-cpp issue #12: Minifi 109

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/12
  
hey @benqiu2016.  It looks like there are some merge conflicts and I wasn't 
able to just apply the last commit.  Is there a way you can get this rebased on 
master?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2817) git branch cleanup

[Andre (JIRA)]

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

Andre commented on NIFI-2817:
-

After reviewing commits the second batch of branches was deemed safe to delete. 

Waiting for replication to GH 

> git branch cleanup
> --
>
> Key: NIFI-2817
> URL: https://issues.apache.org/jira/browse/NIFI-2817
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Andre
>Assignee: Andre
>
> Document the deletion of stale git branches



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

[GitHub] nifi issue #1057: NIFI-2816 - Clean typos across the code

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1057
  
@bbende there's a few hundred more  but I decided to split the task to 
avoid having to rebase non-stop! :sunglasses: 

@joewitt pleased to help, next time the kangaroo steak bill is yours. 
:smiley: 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1057
  
@bbende there's a few hundred more  but I decided to split the task to 
avoid having to rebase non-stop! :sunglasses: 

@joewitt pleased to help, next time the kangaroo steak bill is yours. 
:smiley: 


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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