[jira] [Updated] (NIFI-2310) Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping Special Characters

[Koji Kawamura (JIRA)]

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

Koji Kawamura updated NIFI-2310:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Merged this to master and 0.x branch.

> Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping 
> Special Characters
> 
>
> Key: NIFI-2310
> URL: https://issues.apache.org/jira/browse/NIFI-2310
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 1.0.0, 0.8.0
>
>
> The following jolt spec failed to pass the validation check in 
> JoltTransformJSON:
> {
>   "\\@context": {
> "name": "&1.Name",
> "ingredient": "&1.Inputs",
> "yield": "\\@context.Makes",
> "*": "&1.&"
>   },
>   "name": "Name",
>   "ingredient": "Inputs",
>   "yield": "Makes",
>   "*": "&"
> }
> The reason is the double backslash to escape '@' which should be supported to 
> identify literal characters.
> Upgrading to Jolt version 0.0.21 should resolve this problem since it was 
> fixed in that release.



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

[jira] [Updated] (NIFI-2310) Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping Special Characters

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2310:
--
Fix Version/s: 0.8.0

> Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping 
> Special Characters
> 
>
> Key: NIFI-2310
> URL: https://issues.apache.org/jira/browse/NIFI-2310
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 1.0.0, 0.8.0
>
>
> The following jolt spec failed to pass the validation check in 
> JoltTransformJSON:
> {
>   "\\@context": {
> "name": "&1.Name",
> "ingredient": "&1.Inputs",
> "yield": "\\@context.Makes",
> "*": "&1.&"
>   },
>   "name": "Name",
>   "ingredient": "Inputs",
>   "yield": "Makes",
>   "*": "&"
> }
> The reason is the double backslash to escape '@' which should be supported to 
> identify literal characters.
> Upgrading to Jolt version 0.0.21 should resolve this problem since it was 
> fixed in that release.



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

[jira] [Commented] (NIFI-2310) Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping Special Characters

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2310:
--

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/674
  
Merged this commit to branch 0.x, too. Confirmed the sample Jolt spec with 
escape characters is validated and transformed successfully.


> Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping 
> Special Characters
> 
>
> Key: NIFI-2310
> URL: https://issues.apache.org/jira/browse/NIFI-2310
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 1.0.0
>
>
> The following jolt spec failed to pass the validation check in 
> JoltTransformJSON:
> {
>   "\\@context": {
> "name": "&1.Name",
> "ingredient": "&1.Inputs",
> "yield": "\\@context.Makes",
> "*": "&1.&"
>   },
>   "name": "Name",
>   "ingredient": "Inputs",
>   "yield": "Makes",
>   "*": "&"
> }
> The reason is the double backslash to escape '@' which should be supported to 
> identify literal characters.
> Upgrading to Jolt version 0.0.21 should resolve this problem since it was 
> fixed in that release.



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

[GitHub] nifi issue #674: NIFI-2310 - Shiftr Transform in JoltTransformJSON Processor...

[ijokarumawak]

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/674
  
Merged this commit to branch 0.x, too. Confirmed the sample Jolt spec with 
escape characters is validated and transformed successfully.


---
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-2298) Add missing futures for ConsumeKafka

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2298:
--

Github user xmlking commented on the issue:

https://github.com/apache/nifi/pull/687
  
@olegz does consumeKafka support back pressure ?
I would like to add ControlRate processor after consumeKafka to reduce the 
speed of messages pumped into nifi flow.



> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Oleg Zhurakousky
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[jira] [Commented] (NIFI-2310) Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping Special Characters

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2310:
---

[~ijokarumawak]can you please also add 0.8.0 as  fix version since it was 
merged to 0.x as well.

thanks

> Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping 
> Special Characters
> 
>
> Key: NIFI-2310
> URL: https://issues.apache.org/jira/browse/NIFI-2310
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 1.0.0
>
>
> The following jolt spec failed to pass the validation check in 
> JoltTransformJSON:
> {
>   "\\@context": {
> "name": "&1.Name",
> "ingredient": "&1.Inputs",
> "yield": "\\@context.Makes",
> "*": "&1.&"
>   },
>   "name": "Name",
>   "ingredient": "Inputs",
>   "yield": "Makes",
>   "*": "&"
> }
> The reason is the double backslash to escape '@' which should be supported to 
> identify literal characters.
> Upgrading to Jolt version 0.0.21 should resolve this problem since it was 
> fixed in that release.



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

[jira] [Commented] (NIFI-2310) Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping Special Characters

[ASF subversion and git services (JIRA)]

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

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

Commit 4ea512a9193f287ea003f46c39c791eaf510b749 in nifi's branch refs/heads/0.x 
from [~YolandaMDavis]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=4ea512a ]

NIFI-2310 - upgraded jolt to 0.0.21 to resolve special character issue

This closes #674

Signed-off-by: Koji Kawamura 


> Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping 
> Special Characters
> 
>
> Key: NIFI-2310
> URL: https://issues.apache.org/jira/browse/NIFI-2310
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 1.0.0
>
>
> The following jolt spec failed to pass the validation check in 
> JoltTransformJSON:
> {
>   "\\@context": {
> "name": "&1.Name",
> "ingredient": "&1.Inputs",
> "yield": "\\@context.Makes",
> "*": "&1.&"
>   },
>   "name": "Name",
>   "ingredient": "Inputs",
>   "yield": "Makes",
>   "*": "&"
> }
> The reason is the double backslash to escape '@' which should be supported to 
> identify literal characters.
> Upgrading to Jolt version 0.0.21 should resolve this problem since it was 
> fixed in that release.



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

[jira] [Commented] (NIFI-1733) Create Authorizer implementation that uses Apache Ranger

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1733:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/574
  
@bbende really nice job on the licensing stuff and thanks for 
finding/fixing the lgpl findbugs annotations issue!


> Create Authorizer implementation that uses Apache Ranger
> 
>
> Key: NIFI-1733
> URL: https://issues.apache.org/jira/browse/NIFI-1733
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.0.0
>
>
> In NIFI-1552 we defined a new Authorizer API for 1.0.0. 
> In addition to the standard file-based Authorizer, we should provide an 
> Authorizer implementation that uses Apache Ranger.



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

[GitHub] nifi issue #574: NIFI-1733 Adding a Ranger implementation of NiFi's Authoriz...

[joewitt]

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/574
  
@bbende really nice job on the licensing stuff and thanks for 
finding/fixing the lgpl findbugs annotations issue!


---
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-2316) After restarting cluster, all nodes sometimes come up with all components stopped

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2316:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/678
  
I have two processors (generate -> logAttribute) in a 3 node secure cluster 
and when I restart occasionally I'll get repeating messages of "Failed to 
retrieve any new heartbeat information for nodes. Will not make any decisions 
based on heartbeats." originating from different nodes.

I think this is caused by nodes not having a consistent view of the cluster.


> After restarting cluster, all nodes sometimes come up with all components 
> stopped
> -
>
> Key: NIFI-2316
> URL: https://issues.apache.org/jira/browse/NIFI-2316
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> When I restart an entire cluster, I see sometimes that all processors, etc. 
> are stopped. Sometimes this can also result in some nodes not being able to 
> join the cluster if they have a root group port, as the run status is not the 
> same across the cluster, so the new node cannot inherit the flow.



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

[jira] [Created] (NIFI-2340) Incremental database processors should support incoming flow files

[Matt Burgess (JIRA)]

Matt Burgess created NIFI-2340:
--

 Summary: Incremental database processors should support incoming 
flow files
 Key: NIFI-2340
 URL: https://issues.apache.org/jira/browse/NIFI-2340
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Extensions
Affects Versions: 0.7.0, 1.0.0
Reporter: Matt Burgess


QueryDatabaseTable and GenerateTableFetch do not support incoming connections, 
which makes them less flexible for accepting table names, such as using 
Expression Language (EL) for names located in flow file attributes, e.g.) The 
use of EL (to include custom properties and the Variable Registry) will enable 
these processors to fetch arbitrary tables based on the provided values.



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

[jira] [Updated] (NIFI-2307) Ensure the Connection Configuration and Details Dialog Open

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-2307:
--
Description: When appropriate we need to ensure the connection 
configuration and details dialog open. We were not taking into account the 
access policies of the source and destination components. Consider using the 
permissions of the source and destination to drive the permissions of the 
connection.  (was: The connection dialogs show details about the source and 
destination components. These need to be loaded/scrubbed according to the 
permissions of those components.)

> Ensure the Connection Configuration and Details Dialog Open
> ---
>
> Key: NIFI-2307
> URL: https://issues.apache.org/jira/browse/NIFI-2307
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> When appropriate we need to ensure the connection configuration and details 
> dialog open. We were not taking into account the access policies of the 
> source and destination components. Consider using the permissions of the 
> source and destination to drive the permissions of the connection.



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

[jira] [Updated] (NIFI-2334) When looking at Cluster page, some nodes do not show any stats while others do

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2334:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> When looking at Cluster page, some nodes do not show any stats while others do
> --
>
> Key: NIFI-2334
> URL: https://issues.apache.org/jira/browse/NIFI-2334
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> When I open the cluster page on a 3 node cluster, I see different results 
> depending on which node I'm on. The first node (which is the cluster 
> coordinator) shows the correct stats for Active Threads, Queue/Size, Uptime, 
> Last Heartbeat.
> Node 2 shows stale values. Node 2 used to be the cluster coordinator.
> Node 3 shows no values at all. Node 3 has never been the cluster coordinator.



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

[jira] [Commented] (NIFI-2334) When looking at Cluster page, some nodes do not show any stats while others do

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2334:
--

Github user asfgit closed the pull request at:

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


> When looking at Cluster page, some nodes do not show any stats while others do
> --
>
> Key: NIFI-2334
> URL: https://issues.apache.org/jira/browse/NIFI-2334
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> When I open the cluster page on a 3 node cluster, I see different results 
> depending on which node I'm on. The first node (which is the cluster 
> coordinator) shows the correct stats for Active Threads, Queue/Size, Uptime, 
> Last Heartbeat.
> Node 2 shows stale values. Node 2 used to be the cluster coordinator.
> Node 3 shows no values at all. Node 3 has never been the cluster coordinator.



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

[GitHub] nifi pull request #697: NIFI-2334: Delegate requests for cluster info to the...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2334) When looking at Cluster page, some nodes do not show any stats while others do

[ASF subversion and git services (JIRA)]

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

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

Commit 5eba2b763edaac6889b4389c4b9fb03768091a75 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5eba2b7 ]

NIFI-2334: Delegate requests for cluster info to the cluster coordinator

This closes #697

Signed-off-by: jpercivall 


> When looking at Cluster page, some nodes do not show any stats while others do
> --
>
> Key: NIFI-2334
> URL: https://issues.apache.org/jira/browse/NIFI-2334
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> When I open the cluster page on a 3 node cluster, I see different results 
> depending on which node I'm on. The first node (which is the cluster 
> coordinator) shows the correct stats for Active Threads, Queue/Size, Uptime, 
> Last Heartbeat.
> Node 2 shows stale values. Node 2 used to be the cluster coordinator.
> Node 3 shows no values at all. Node 3 has never been the cluster coordinator.



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

[jira] [Commented] (NIFI-1899) Create ListenSMTP & ExtractEmailAttachment processors

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-1899:
---

[~JPercivall] looks good to go to me.  I didn't do a separate functional test 
but in walking through the code the only thing that jumps out to me as 
important to flag right now is that the extract attachments processor and 
possibly the SMTP listener read the full message into memory.  That doesn't 
have to be fixed today and i did note a property to limit max message size so 
that seems fair for now.

Cool contrib /effort for sure.
+1

> Create ListenSMTP & ExtractEmailAttachment processors
> -
>
> Key: NIFI-1899
> URL: https://issues.apache.org/jira/browse/NIFI-1899
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Andre
> Fix For: 1.0.0
>
>




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

[jira] [Commented] (NIFI-2244) Cannot modify connection if user does not have permissions to modify source or destination

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2244:
--

GitHub user mcgilman opened a pull request:

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

Updating the UI to reflect the access policies being enforced

NIFI-2244:
- Separating the access control check and the supports modification check 
for the selected component.
- Using separated access control check to support editing when possible 
without write permission.

NIFI-2307:
- Adding support for opening Connection configuration and Connection 
details dialog when source/destination permissions are not allowed.
- Enforcing connection permissions based on the source and destination 
comonent.
- Removing connection specific access policies.

NIFI-2265:
- Filtering out sensitive details in component status and status history 
when appropriate.

NIFI-1800:
- Adding parent process group id to the Controller Services table.

NIFI-2077:
- Removing some old un-used icons following the UI refresh.

NIFI-2242:
- Requiring write permissions for all components in a selection.

NIFI-2080:
- Updating style of the name in the selection context to handle scroll bars 
and use available width.

NIFI-2331:
- Addressing issue when removing a user/group which was causing the tenant 
policy to be removed.

NIFI-2335:
- Ensuring the flow is saved after starting/stopping a process group.

NIFI-2235:
- Ensuring we use consistent conditions between the context menu and the 
operate palette.

- Allowing users with read only access to the tenants page.
- Fixing current user integration test.
- Ensuring schedule methods are locked appropriately.

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

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

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

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


commit f62f48efe5f0e68f6c6f439565a31c9ae4e708b7
Author: Matt Gilman 
Date:   2016-07-21T01:41:06Z

NIFI-2244:
- Separating the access control check and the supports modification check 
for the selected component.
- Using separated access control check to support editing when possible 
without write permission.
NIFI-2307:
- Adding support for opening Connection configuration and Connection 
details dialog when source/destination permissions are not allowed.
- Enforcing connection permissions based on the source and destination 
comonent.
- Removing connection specific access policies.
NIFI-2265:
- Filtering out sensitive details in component status and status history 
when appropriate.
NIFI-1800:
- Adding parent process group id to the Controller Services table.
NIFI-2077:
- Removing some old un-used icons following the UI refresh.
NIFI-2242:
- Requiring write permissions for all components in a selection.
NIFI-2080:
- Updating style of the name in the selection context to handle scroll bars 
and use available width.
NIFI-2331:
- Addressing issue when removing a user/group which was causing the tenant 
policy to be removed.
NIFI-2335:
- Ensuring the flow is saved after starting/stopping a process group.
NIFI-2235:
- Ensuring we use consistent conditions between the context menu and the 
operate palette.

- Allowing users with read only access to the tenants page.
- Fixing current user integration test.
- Ensuring schedule methods are locked appropriately.




> Cannot modify connection if user does not have permissions to modify source 
> or destination
> --
>
> Key: NIFI-2244
> URL: https://issues.apache.org/jira/browse/NIFI-2244
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> A user is unable to modify a connection if its source or destination is a 
> processor that is running. However, it appears that this logic is also 
> applied when considering permissions. If I have permissions to modify a 
> connection but the not permissions to modify the source or the destination, 
> the UI does not allow me to Configure the connection with a right-click menu. 
> Instead, the context menu shows "View Configuration" but the Operation 
> palette menu allows me to configure the Connection (the palette vs. context 
> menu issue 

[GitHub] nifi pull request #698: Updating the UI to reflect the access policies being...

[mcgilman]

GitHub user mcgilman opened a pull request:

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

Updating the UI to reflect the access policies being enforced

NIFI-2244:
- Separating the access control check and the supports modification check 
for the selected component.
- Using separated access control check to support editing when possible 
without write permission.

NIFI-2307:
- Adding support for opening Connection configuration and Connection 
details dialog when source/destination permissions are not allowed.
- Enforcing connection permissions based on the source and destination 
comonent.
- Removing connection specific access policies.

NIFI-2265:
- Filtering out sensitive details in component status and status history 
when appropriate.

NIFI-1800:
- Adding parent process group id to the Controller Services table.

NIFI-2077:
- Removing some old un-used icons following the UI refresh.

NIFI-2242:
- Requiring write permissions for all components in a selection.

NIFI-2080:
- Updating style of the name in the selection context to handle scroll bars 
and use available width.

NIFI-2331:
- Addressing issue when removing a user/group which was causing the tenant 
policy to be removed.

NIFI-2335:
- Ensuring the flow is saved after starting/stopping a process group.

NIFI-2235:
- Ensuring we use consistent conditions between the context menu and the 
operate palette.

- Allowing users with read only access to the tenants page.
- Fixing current user integration test.
- Ensuring schedule methods are locked appropriately.

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

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

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

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


commit f62f48efe5f0e68f6c6f439565a31c9ae4e708b7
Author: Matt Gilman 
Date:   2016-07-21T01:41:06Z

NIFI-2244:
- Separating the access control check and the supports modification check 
for the selected component.
- Using separated access control check to support editing when possible 
without write permission.
NIFI-2307:
- Adding support for opening Connection configuration and Connection 
details dialog when source/destination permissions are not allowed.
- Enforcing connection permissions based on the source and destination 
comonent.
- Removing connection specific access policies.
NIFI-2265:
- Filtering out sensitive details in component status and status history 
when appropriate.
NIFI-1800:
- Adding parent process group id to the Controller Services table.
NIFI-2077:
- Removing some old un-used icons following the UI refresh.
NIFI-2242:
- Requiring write permissions for all components in a selection.
NIFI-2080:
- Updating style of the name in the selection context to handle scroll bars 
and use available width.
NIFI-2331:
- Addressing issue when removing a user/group which was causing the tenant 
policy to be removed.
NIFI-2335:
- Ensuring the flow is saved after starting/stopping a process group.
NIFI-2235:
- Ensuring we use consistent conditions between the context menu and the 
operate palette.

- Allowing users with read only access to the tenants page.
- Fixing current user integration test.
- Ensuring schedule methods are locked appropriately.




---
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 #674: NIFI-2310 - Shiftr Transform in JoltTransformJSON Pr...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2310) Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping Special Characters

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2310:
--

Github user asfgit closed the pull request at:

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


> Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping 
> Special Characters
> 
>
> Key: NIFI-2310
> URL: https://issues.apache.org/jira/browse/NIFI-2310
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 1.0.0
>
>
> The following jolt spec failed to pass the validation check in 
> JoltTransformJSON:
> {
>   "\\@context": {
> "name": "&1.Name",
> "ingredient": "&1.Inputs",
> "yield": "\\@context.Makes",
> "*": "&1.&"
>   },
>   "name": "Name",
>   "ingredient": "Inputs",
>   "yield": "Makes",
>   "*": "&"
> }
> The reason is the double backslash to escape '@' which should be supported to 
> identify literal characters.
> Upgrading to Jolt version 0.0.21 should resolve this problem since it was 
> fixed in that release.



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

[jira] [Created] (NIFI-2338) Replay Authorization Check happening twice

[Matt Gilman (JIRA)]

Matt Gilman created NIFI-2338:
-

 Summary: Replay Authorization Check happening twice
 Key: NIFI-2338
 URL: https://issues.apache.org/jira/browse/NIFI-2338
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Matt Gilman
Priority: Blocker
 Fix For: 1.0.0


Verified replay authorization and ensure it's only executed when appropriately. 
Currently, its happening in the framework and in the provenance repository.



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

[jira] [Commented] (NIFI-2310) Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping Special Characters

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2310:
--

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/674
  
+1

I reproduced the validation error before applying this fix using the sample 
input and spec you shared, and confirmed that it's valid with this fix. Run a 
NiFi data-flow to transform Json using Jolt processor. It worked without 
problem.
Passed local contrib check successfully.

I will merge it in master branch.
Also I am going to test this with 0.x branch.

Thanks @YolandaMDavis !


> Shiftr Transform in JoltTransformJSON Processor Does Not Support Escaping 
> Special Characters
> 
>
> Key: NIFI-2310
> URL: https://issues.apache.org/jira/browse/NIFI-2310
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 1.0.0
>
>
> The following jolt spec failed to pass the validation check in 
> JoltTransformJSON:
> {
>   "\\@context": {
> "name": "&1.Name",
> "ingredient": "&1.Inputs",
> "yield": "\\@context.Makes",
> "*": "&1.&"
>   },
>   "name": "Name",
>   "ingredient": "Inputs",
>   "yield": "Makes",
>   "*": "&"
> }
> The reason is the double backslash to escape '@' which should be supported to 
> identify literal characters.
> Upgrading to Jolt version 0.0.21 should resolve this problem since it was 
> fixed in that release.



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

[GitHub] nifi issue #674: NIFI-2310 - Shiftr Transform in JoltTransformJSON Processor...

[ijokarumawak]

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/674
  
+1

I reproduced the validation error before applying this fix using the sample 
input and spec you shared, and confirmed that it's valid with this fix. Run a 
NiFi data-flow to transform Json using Jolt processor. It worked without 
problem.
Passed local contrib check successfully.

I will merge it in master branch.
Also I am going to test this with 0.x branch.

Thanks @YolandaMDavis !


---
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-2333) When a flow consists only of controller-level reporting tasks/controller services, nodes cannot rejoin cluster once they have disconnected

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2333:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> When a flow consists only of controller-level reporting tasks/controller 
> services, nodes cannot rejoin cluster once they have disconnected
> --
>
> Key: NIFI-2333
> URL: https://issues.apache.org/jira/browse/NIFI-2333
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> I have a cluster with 3 nodes. If I disconnect and reconnect a node with 
> nothing in the flow, all works okay. If I add processors to the graph, all 
> works okay. But if I have no components on the graph but define 
> controller-level controller services or reporting tasks, then when I 
> disconnect the node it fails to reconnect when I click 'reconnect'. I end up 
> with the following stack trace:
> 2016-07-20 15:19:28,259 ERROR [Reconnect to Cluster] 
> o.a.nifi.controller.StandardFlowService Handling reconnection request failed 
> due to: 
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed 
> to connect node to cluster because local flow controller partially updated. 
> Administrator should disconnect node and review flow for corruption.
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed 
> to connect node to cluster because local flow controller partially updated. 
> Administrator should disconnect node and review flow for corruption.
> at 
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:869)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:591)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.access$300(StandardFlowService.java:97)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService$2.run(StandardFlowService.java:403)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> Caused by: 
> org.apache.nifi.controller.serialization.FlowSynchronizationException: 
> java.lang.IllegalStateException: The specified observer identifier already 
> exists.
> at 
> org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:358)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1375)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:81)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:670)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:841)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> ... 4 common frames omitted
> Caused by: java.lang.IllegalStateException: The specified observer identifier 
> already exists.
> at 
> org.apache.nifi.logging.repository.StandardLogRepository.addObserver(StandardLogRepository.java:134)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.FlowController.createReportingTask(FlowController.java:2734)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowSynchronizer.addReportingTask(StandardFlowSynchronizer.java:467)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:326)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> ... 8 common frames omitted



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

[GitHub] nifi pull request #693: NIFI-2333: Consider reporting tasks and controller s...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2333) When a flow consists only of controller-level reporting tasks/controller services, nodes cannot rejoin cluster once they have disconnected

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2333:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/693
  
+1

Visually verified code and did a contrib check build. On secure 3 node 
cluster, I reproduced the problem without the fix applied and then verified 
that the PR fixed the problem. Thanks @markap14, I will merge it in. #


> When a flow consists only of controller-level reporting tasks/controller 
> services, nodes cannot rejoin cluster once they have disconnected
> --
>
> Key: NIFI-2333
> URL: https://issues.apache.org/jira/browse/NIFI-2333
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> I have a cluster with 3 nodes. If I disconnect and reconnect a node with 
> nothing in the flow, all works okay. If I add processors to the graph, all 
> works okay. But if I have no components on the graph but define 
> controller-level controller services or reporting tasks, then when I 
> disconnect the node it fails to reconnect when I click 'reconnect'. I end up 
> with the following stack trace:
> 2016-07-20 15:19:28,259 ERROR [Reconnect to Cluster] 
> o.a.nifi.controller.StandardFlowService Handling reconnection request failed 
> due to: 
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed 
> to connect node to cluster because local flow controller partially updated. 
> Administrator should disconnect node and review flow for corruption.
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed 
> to connect node to cluster because local flow controller partially updated. 
> Administrator should disconnect node and review flow for corruption.
> at 
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:869)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:591)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.access$300(StandardFlowService.java:97)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService$2.run(StandardFlowService.java:403)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> Caused by: 
> org.apache.nifi.controller.serialization.FlowSynchronizationException: 
> java.lang.IllegalStateException: The specified observer identifier already 
> exists.
> at 
> org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:358)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1375)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:81)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:670)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:841)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> ... 4 common frames omitted
> Caused by: java.lang.IllegalStateException: The specified observer identifier 
> already exists.
> at 
> org.apache.nifi.logging.repository.StandardLogRepository.addObserver(StandardLogRepository.java:134)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.FlowController.createReportingTask(FlowController.java:2734)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowSynchronizer.addReportingTask(StandardFlowSynchronizer.java:467)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:326)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> ... 8 common frames omitted



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

[GitHub] nifi issue #693: NIFI-2333: Consider reporting tasks and controller services...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/693
  
+1

Visually verified code and did a contrib check build. On secure 3 node 
cluster, I reproduced the problem without the fix applied and then verified 
that the PR fixed the problem. Thanks @markap14, I will merge it in. #


---
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-2337) IllegalMonitorStateException when disconnecting node

[Mark Payne (JIRA)]

Mark Payne created NIFI-2337:


 Summary: IllegalMonitorStateException when disconnecting node
 Key: NIFI-2337
 URL: https://issues.apache.org/jira/browse/NIFI-2337
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.0.0
Reporter: Mark Payne
Assignee: Mark Payne
 Fix For: 1.0.0


When a node is disconnected from the cluster, it often logs a stacktrace 
similar to:

2016-07-20 20:20:47,814 ERROR [Leader Election Notification Thread-1] 
o.a.c.f.recipes.leader.LeaderSelector The leader threw an exception
java.lang.IllegalMonitorStateException: You do not own the lock: 
/leaders/Cluster Coordinator
at 
org.apache.curator.framework.recipes.locks.InterProcessMutex.release(InterProcessMutex.java:140)
 ~[curator-recipes-2.10.0.jar:na]
at 
org.apache.curator.framework.recipes.leader.LeaderSelector.doWork(LeaderSelector.java:425)
 [curator-recipes-2.10.0.jar:na]
at 
org.apache.curator.framework.recipes.leader.LeaderSelector.doWorkLoop(LeaderSelector.java:441)
 [curator-recipes-2.10.0.jar:na]
at 
org.apache.curator.framework.recipes.leader.LeaderSelector.access$100(LeaderSelector.java:64)
 [curator-recipes-2.10.0.jar:na]
at 
org.apache.curator.framework.recipes.leader.LeaderSelector$2.call(LeaderSelector.java:245)
 [curator-recipes-2.10.0.jar:na]
at 
org.apache.curator.framework.recipes.leader.LeaderSelector$2.call(LeaderSelector.java:239)
 [curator-recipes-2.10.0.jar:na]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_74]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_74]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_74]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_74]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_74]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_74]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 [na:1.8.0_74]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_74]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_74]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_74]

This error, I believe, is harmless but is alarming and should be addressed.



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

[jira] [Updated] (NIFI-2334) When looking at Cluster page, some nodes do not show any stats while others do

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2334:
-
Status: Patch Available  (was: Open)

> When looking at Cluster page, some nodes do not show any stats while others do
> --
>
> Key: NIFI-2334
> URL: https://issues.apache.org/jira/browse/NIFI-2334
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> When I open the cluster page on a 3 node cluster, I see different results 
> depending on which node I'm on. The first node (which is the cluster 
> coordinator) shows the correct stats for Active Threads, Queue/Size, Uptime, 
> Last Heartbeat.
> Node 2 shows stale values. Node 2 used to be the cluster coordinator.
> Node 3 shows no values at all. Node 3 has never been the cluster coordinator.



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

[GitHub] nifi pull request #697: NIFI-2334: Delegate requests for cluster info to the...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-2334: Delegate requests for cluster info to the cluster coordinator



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

$ git pull https://github.com/markap14/nifi NIFI-2334

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

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


commit 439db3a2fb54c1f7a0bcb07b61163b2fc1e86d2f
Author: Mark Payne 
Date:   2016-07-21T00:34:10Z

NIFI-2334: Delegate requests for cluster info to the cluster coordinator




---
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-2235) Conditions are inconsistent between Operate palette & context menu

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2235:
-

Assignee: Matt Gilman

> Conditions are inconsistent between Operate palette & context menu
> --
>
> Key: NIFI-2235
> URL: https://issues.apache.org/jira/browse/NIFI-2235
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Specifically, the ability to Copy was noticed as being different, but there 
> may be others. To replicate, create two processors and change permissions so 
> that you have permissions to view both but only permissions to modify one of 
> them.  I also gave myself NO permissions to modify the group that the 
> components are in. Select both processors in the UI. The palette gives the 
> ability to copy the components but the context menu has nothing in it.



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

[GitHub] nifi issue #674: NIFI-2310 - Shiftr Transform in JoltTransformJSON Processor...

[ijokarumawak]

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/674
  
Start 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] [Closed] (NIFI-2336) When the current process group is started or stopped, the flow is not saved

[Mark Payne (JIRA)]

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

Mark Payne closed NIFI-2336.


> When the current process group is started or stopped, the flow is not saved
> ---
>
> Key: NIFI-2336
> URL: https://issues.apache.org/jira/browse/NIFI-2336
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>
> If I click the 'start' or 'stop' button in the Operate palette, and then I 
> restart NiFI, the changes are not persisted across restarts.



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

[jira] [Commented] (NIFI-2332) When clustered, bulletins not showing the correct node

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2332:
--

Github user asfgit closed the pull request at:

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


> When clustered, bulletins not showing the correct node
> --
>
> Key: NIFI-2332
> URL: https://issues.apache.org/jira/browse/NIFI-2332
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Controller-level bulletins don't show any node id. Bulletins on processors 
> always show that the bulletin originated at the Cluster Coordinator.



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

[GitHub] nifi issue #692: NIFI-2332: Ensure that bulletin node address is set when cl...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/692
  
+1

Visually verified, and did contrib check build. I saw the error this is 
fixing all the time when starting up (nodes would not agree who was creating a 
bulletin). I demonstrated this resolves the issue on a secure 3 node cluster. 
Thanks @markap14, I will merge it in.


---
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 #696: NIFI-2336: Ensure that we save changes to the flow w...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-2336: Ensure that we save changes to the flow when we start or stop 
the current process group

NIFI-2336: Ensure that we save changes to the flow when we start or stop 
the current process group

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

$ git pull https://github.com/markap14/nifi NIFI-2336

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

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


commit ff0222e689cc622cb311ac8dae204587b1a68e7c
Author: Mark Payne 
Date:   2016-07-20T23:06:34Z

NIFI-2336: Ensure that we save changes to the flow when we start or stop 
the current process group




---
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-2289) Cluster sometimes gets into state where it always says 'no Cluster Coordinator elected'

[ASF subversion and git services (JIRA)]

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

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

Commit 7f2bda29d968694f62c7e776839efb448215f6f9 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=7f2bda2 ]

NIFI-2289: Ensure that we include Node ID's of all nodes when finding cluster 
coordinator, even if the node is currently still connecting or has not yet 
joined the cluster, which ccan be the case if all nodes in the cluster are 
restarting at the same time.

This closes #681

Signed-off-by: jpercivall 


> Cluster sometimes gets into state where it always says 'no Cluster 
> Coordinator elected'
> ---
>
> Key: NIFI-2289
> URL: https://issues.apache.org/jira/browse/NIFI-2289
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>
> When running in clustered mode, occasionally NiFi will get into a state where 
> it indicates for each request that no cluster coordinator exists, even though 
> one is clearly elected.



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

[jira] [Commented] (NIFI-2289) Cluster sometimes gets into state where it always says 'no Cluster Coordinator elected'

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2289:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/681
  
+1

Visually verified code, did contrib check build. Restarted a secure 3 node 
cluster many times all at the same time and never encountered problem. Thanks 
@markap14, I will merge it in.


> Cluster sometimes gets into state where it always says 'no Cluster 
> Coordinator elected'
> ---
>
> Key: NIFI-2289
> URL: https://issues.apache.org/jira/browse/NIFI-2289
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>
> When running in clustered mode, occasionally NiFi will get into a state where 
> it indicates for each request that no cluster coordinator exists, even though 
> one is clearly elected.



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

[jira] [Commented] (NIFI-1977) Property descriptors without explicit validators are not recognized

[Gregory Hart (JIRA)]

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

Gregory Hart commented on NIFI-1977:


I can confirm I'm seeing the same issue in 0.5.0. Calling 
`.addValidator(Validator.VALID)` when building the property resolves the issue. 
Are all properties required to have a validator? If so, I suggest explaining 
this in the error message.

> Property descriptors without explicit validators are not recognized
> ---
>
> Key: NIFI-1977
> URL: https://issues.apache.org/jira/browse/NIFI-1977
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.1
>Reporter: Andrew Grande
>
> Looks like a bug in a testing framework.
> I have a simple test case like this one:
> {code:java}
> @Test
> public void customHeader() {
> final TestRunner runner = 
> TestRunners.newTestRunner(ParseCSVRecord.class);
> runner.setProperty(PROP_CUSTOM_HEADER, "Column 1,Column 2");
> runner.enqueue("row1col1,row1col2\nrow2col1, row2col2");
> runner.run();
> {code}
> When a property is declared without an explicit validator, the test runner 
> fails complaining that Custom Header is not a supported property (yes, I've 
> added it to the descriptors list).
> {code:java}
> public static final PropertyDescriptor PROP_CUSTOM_HEADER = new 
> PropertyDescriptor.Builder()
> .name("Custom Header")
> .description("Use this header (delimited according to set rules) instead of 
> auto-discovering it from schema")
> .required(false)  
>   .expressionLanguageSupported(true)
> .build();
> {code}
> The intent here is to not have a validator declared, but rather implement 
> more complex logic in the customValidate() callback, but the test never gets 
> to that point.



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

[jira] [Commented] (NIFI-2268) HandleHttpRequest can use too many tasks and CPU

[Michael Moser (JIRA)]

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

Michael Moser commented on NIFI-2268:
-

Excellent approach [~markap14].

> HandleHttpRequest can use too many tasks and CPU
> 
>
> Key: NIFI-2268
> URL: https://issues.apache.org/jira/browse/NIFI-2268
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Michael Moser
>Priority: Minor
>
> With the default settings of HandleHttpRequest, user reports 100% CPU usage 
> and millions of scheduled tasks.  When this processor doesn't have work to 
> do, its onTrigger() should call ProcessContext.yield().  This is how the 
> ListenHTTP processor works, so it's an established pattern.



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

[GitHub] nifi issue #678: NIFI-2316, NIFI-2318: Ensure that we do not save the flow b...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/678
  
I believe this is due to NIFI-2335. I will re-test.

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


---
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-1323) UI visual design enhancement

[Colin Bowdery (JIRA)]

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

Colin Bowdery commented on NIFI-1323:
-

Hi Rob/All,
Is there any developer docs for the NiFi UI available? Specifically,
1. How is the current UI implemented? (not look and feel but code 
implementation)
2. How do we implement a new design? 
3. What technologies are supported (HTML5, JS, FLASH, etc..)?
4. Can we integrate 3rd party components (i.e. for graphs, buttons, drop-downs)

I would like to skill up and start contributing to the UI/UX aspects but am not 
sure where to start.

If nothing exists, with the groups help, perhaps I can start by generating some 
"HOW TO" documentation for the UI. I note this aspect is very much ignored on 
the NiFi webpage.

Many thanks,

Colin.

> UI visual design enhancement
> 
>
> Key: NIFI-1323
> URL: https://issues.apache.org/jira/browse/NIFI-1323
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Rob Moran
>Priority: Trivial
> Attachments: flowfont.zip, nifi-add-processor-dialog.png, 
> nifi-component-samples.png, 
> nifi-configure-processor-properties-set-value.png, 
> nifi-configure-processor-properties.png, 
> nifi-configure-processor-scheduling.png, 
> nifi-configure-processor-settings.png, nifi-dialog-samp...@800px.png, 
> nifi-drag-drop-compon...@2x.png, nifi-global-menu-pending-u...@2x.png, 
> nifi-global-menu.png, nifi-interaction-and-menu-samples.png, 
> nifi-lineage-gra...@800px.png, nifi-sample-fl...@800px.png, 
> nifi-sample-flow.png, nifi-search-resu...@2x.png, nifi-shell-samp...@800px.png
>
>
> (I will attach mockups and supporting files as they become available)
> I am starting to work on a design to modernize the look and feel of the NiFi 
> UI. The initial focus of the design is to freshen the UI (flat design, SVG 
> icons, etc.). Additionally, the new design will propose usability 
> improvements such as exposing more flow-related actions into collapsible 
> panes, improving hierarchy of information, etc.
> Going forward, the design plan is to help lay the foundation for other UI/UX 
> related issues such as those documented in NIFI-951.
> ---
> *flowfont.zip*
> Contains icon font and supporting files
> *nifi-add-processor-dialog.png*
> Dialog sample. This sample shows the 'Add Processor' dialog.
> *nifi-component-samples.png*
> To show styling for all components, as well as those components when a user 
> is unauthorized to access.
> *nifi-configure-processor-properties*
> *nifi-configure-processor-properties-set-value*
> *nifi-configure-processor-scheduling*
> *nifi-configure-processor-settings*
> Configure Processor dialog. See related Comments below (in Activity section).
> *nifi-dialog-sample-@800px*
> Dialog sample in 800px wide viewport. This sample shows the the 'Details' tab 
> of a provenance event.
> *nifi-drag-drop-component@2x*
> To show updated component toolbar button style and user interaction 
> improvements
> *nifi-drop.svg*
> NiFi logo without 'nifi
> *nifi-global-menu*
> To show global menu
> *nifi-global-menu-pending-user@2x*
> Demonstrates a generic notification with an aggregate count that appears on 
> the global menu icon. When the menu is displayed, the same notification (and 
> individual count) appears in line with the corresponding item.
> *nifi-interaction-and-menu-samples.png*
> To demonstrate user interactions - hover states, tooltips, menus, etc.
> *nifi-lineage-graph-@800px*
> To show lineage graph with explicit action to get back to data provenance 
> event list.
> *nifi-sample-flow-@800px*
> Shows a very useable UI down to around 800px in width. The thinking here is 
> that at anything lower than this, the NiFi user experience will change to 
> more of a monitoring and/or administrative type workflow. Future mockups will 
> be created to illustrate this.
> *nifi-logo.svg*
> NiFi logo complete
> *nifi-sample-flow.png*
> Mockup of sample flow. Updated to show revised tool and status bars. 
> Management related actions will move to a menu via mouseover (see 
> _nifi-global-menu_). Added benefits here include reducing clutter and more 
> user-friendly menu with text labels to reduce time spent scanning only a 
> large set of icons. This also helps gain valuable viewport width in a browser 
> (see _nifi-sample-flow-@800px_)
> *nifi-search-resu...@2x.png*
> Search results example
> *nifi-shell-sample-@800px*
> Shell sample in 800px wide viewport. This sample shows the 'Data Provenance' 
> table.



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

[jira] [Commented] (NIFI-2193) Command Line Keystore and Truststore utility

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2193:
--

GitHub user brosander opened a pull request:

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

NIFI-2193 - Command line SSL config utility as well as certificate au…

…thority client/server

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

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

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

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


commit 496f4f9cdc3cfee43e34684814c72f674261940d
Author: Bryan Rosander 
Date:   2016-07-06T20:56:08Z

NIFI-2193 - Command line SSL config utility as well as certificate 
authority client/server




> Command Line Keystore and Truststore utility
> 
>
> Key: NIFI-2193
> URL: https://issues.apache.org/jira/browse/NIFI-2193
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> In order to facilitate secure setup of NiFi, it would be useful to have a 
> command line utility capable of generating the required keystores, 
> truststore, and relevant configuration files.
> It should be able to generate keystores for each NiFi node, a truststore that 
> they all use, and relevant passwords and configuration files for using the 
> keystores and truststore.
> Additionally, in order to support distributed deployment, a web based 
> certificate authority with corresponding client will allow for each NiFi 
> instance to generate its own keypair and then request signing by the CA.



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

[jira] [Updated] (NIFI-2193) Command Line Keystore and Truststore utility

[Bryan Rosander (JIRA)]

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

Bryan Rosander updated NIFI-2193:
-
Description: 
In order to facilitate secure setup of NiFi, it would be useful to have a 
command line utility capable of generating the required keystores, truststore, 
and relevant configuration files.

It should be able to generate keystores for each NiFi node, a truststore that 
they all use, and relevant passwords and configuration files for using the 
keystores and truststore.

Additionally, in order to support distributed deployment, a web based 
certificate authority with corresponding client will allow for each NiFi 
instance to generate its own keypair and then request signing by the CA.

  was:
In order to facilitate secure setup of NiFi, it would be useful to have a 
command line utility capable of generating the required keystores, truststore, 
and relevant configuration files.

It should be able to generate keystores for each NiFi node, a truststore that 
they all use, and relevant passwords and configuration files for using the 
keystores and truststore.


> Command Line Keystore and Truststore utility
> 
>
> Key: NIFI-2193
> URL: https://issues.apache.org/jira/browse/NIFI-2193
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> In order to facilitate secure setup of NiFi, it would be useful to have a 
> command line utility capable of generating the required keystores, 
> truststore, and relevant configuration files.
> It should be able to generate keystores for each NiFi node, a truststore that 
> they all use, and relevant passwords and configuration files for using the 
> keystores and truststore.
> Additionally, in order to support distributed deployment, a web based 
> certificate authority with corresponding client will allow for each NiFi 
> instance to generate its own keypair and then request signing by the CA.



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

[jira] [Updated] (NIFI-2193) Command Line Keystore and Truststore utility

[Bryan Rosander (JIRA)]

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

Bryan Rosander updated NIFI-2193:
-
Issue Type: New Feature  (was: Bug)

> Command Line Keystore and Truststore utility
> 
>
> Key: NIFI-2193
> URL: https://issues.apache.org/jira/browse/NIFI-2193
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> In order to facilitate secure setup of NiFi, it would be useful to have a 
> command line utility capable of generating the required keystores, 
> truststore, and relevant configuration files.
> It should be able to generate keystores for each NiFi node, a truststore that 
> they all use, and relevant passwords and configuration files for using the 
> keystores and truststore.
> Additionally, in order to support distributed deployment, a web based 
> certificate authority with corresponding client will allow for each NiFi 
> instance to generate its own keypair and then request signing by the CA.



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

[GitHub] nifi issue #678: NIFI-2316, NIFI-2318: Ensure that we do not save the flow b...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/678
  
This isn't fixing NIFI-2316 for me. I applied this commit to the latest 
master, ran a 3 node secure cluster, created 2 processors and ran them. After I 
restarted, all the nodes correctly joined but all had stopped processors.

It is reproducible. 


---
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-2093) Clear state link on Component State window is hidden

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2093:
---
Resolution: Not A Problem
Status: Resolved  (was: Patch Available)

No longer a problem. The "clear state" button and filter are above the table 
and visible.

> Clear state link on Component State window is hidden
> 
>
> Key: NIFI-2093
> URL: https://issues.apache.org/jira/browse/NIFI-2093
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Fix For: 1.0.0
>
> Attachments: ComponentState-ConsumeKafka.png, State filter is 
> hidden.png
>
>
> It seems that ComponentStateEntity should have accessPolicy so that 
> CanvasUtis.supportsModification() can handle whether the link is active or 
> not.



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

[jira] [Commented] (NIFI-2330) If unable to connect to cluster, node loads an empty flow instead of loading current flow

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2330:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/686
  
+1

Visually verified code, contrib check built and secure 3 node cluster 
worked as expected. Thanks @markap14, I will merge it in.


> If unable to connect to cluster, node loads an empty flow instead of loading 
> current flow
> -
>
> Key: NIFI-2330
> URL: https://issues.apache.org/jira/browse/NIFI-2330
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> I have a three-node cluster that has a dataflow established. If I shut down 
> all nodes and start only one (running embedded zookeeper) so that the node is 
> not able to connect to cluster due to not able to reach zookeeper - the node 
> should load the current flow from disk and begin processing it. However, it 
> instead loads an empty flow, as is evident by navigating to the URI of the 
> node and seeing nothing on the canvas.



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

[jira] [Created] (NIFI-2334) When looking at Cluster page, some nodes do not show any any stats while others do

[Mark Payne (JIRA)]

Mark Payne created NIFI-2334:


 Summary: When looking at Cluster page, some nodes do not show any 
any stats while others do
 Key: NIFI-2334
 URL: https://issues.apache.org/jira/browse/NIFI-2334
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.0.0
Reporter: Mark Payne
Assignee: Mark Payne
Priority: Blocker
 Fix For: 1.0.0


When I open the cluster page on a 3 node cluster, I see different results 
depending on which node I'm on. The first node (which is the cluster 
coordinator) shows the correct stats for Active Threads, Queue/Size, Uptime, 
Last Heartbeat.

Node 2 shows stale values. Node 2 used to be the cluster coordinator.

Node 3 shows no values at all. Node 3 has never been the cluster coordinator.



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

[jira] [Commented] (NIFI-1972) New processor PutIgniteCache

[Mans Singh (JIRA)]

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

Mans Singh commented on NIFI-1972:
--

Thanks [~pvillard], [~aldrin], [~JPercivall] - for your help and advice.  Mans

> New processor PutIgniteCache
> 
>
> Key: NIFI-1972
> URL: https://issues.apache.org/jira/browse/NIFI-1972
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: 0.6.1
> Environment: All
>Reporter: Mans Singh
>Assignee: Mans Singh
>  Labels: cache,, ignite,, put,, streaming,
> Fix For: 1.0.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Create Nifi Ignite Processor to insert data into Apache Ignite Cache



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

[jira] [Updated] (NIFI-2211) Update NiFi architecture graphics for overview doc

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2211:

Summary: Update NiFi architecture graphics for overview doc  (was: Update 
zero-master-node.png)

> Update NiFi architecture graphics for overview doc
> --
>
> Key: NIFI-2211
> URL: https://issues.apache.org/jira/browse/NIFI-2211
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
>Assignee: Rob Moran
> Fix For: 1.0.0
>
> Attachments: zero-master-cluster.png, zero-master-node.png
>
>




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

[jira] [Updated] (NIFI-2211) Update zero-master-node.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2211:

Attachment: zero-master-cluster.png

> Update zero-master-node.png
> ---
>
> Key: NIFI-2211
> URL: https://issues.apache.org/jira/browse/NIFI-2211
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
>Assignee: Rob Moran
> Fix For: 1.0.0
>
> Attachments: zero-master-cluster.png, zero-master-node.png
>
>




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

[jira] [Resolved] (NIFI-2212) Update zero-master-cluster.png

[Rob Moran (JIRA)]

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

Rob Moran resolved NIFI-2212.
-
Resolution: Duplicate

> Update zero-master-cluster.png
> --
>
> Key: NIFI-2212
> URL: https://issues.apache.org/jira/browse/NIFI-2212
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
>Assignee: Rob Moran
> Fix For: 1.0.0
>
> Attachments: zero-master-cluster.png
>
>




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

[jira] [Commented] (NIFI-2333) When a flow consists only of controller-level reporting tasks/controller services, nodes cannot rejoin cluster once they have disconnected

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2333:
--

GitHub user markap14 opened a pull request:

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

NIFI-2333: Consider reporting tasks and controller services when 
determining whether or not flow is empty



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

$ git pull https://github.com/markap14/nifi NIFI-2333

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

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


commit 99e92e1569173c9512926c06ce0b30aadc2d73df
Author: Mark Payne 
Date:   2016-07-20T19:25:32Z

NIFI-2333: Consider reporting tasks and controller services when 
determining whether or not flow is empty




> When a flow consists only of controller-level reporting tasks/controller 
> services, nodes cannot rejoin cluster once they have disconnected
> --
>
> Key: NIFI-2333
> URL: https://issues.apache.org/jira/browse/NIFI-2333
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> I have a cluster with 3 nodes. If I disconnect and reconnect a node with 
> nothing in the flow, all works okay. If I add processors to the graph, all 
> works okay. But if I have no components on the graph but define 
> controller-level controller services or reporting tasks, then when I 
> disconnect the node it fails to reconnect when I click 'reconnect'. I end up 
> with the following stack trace:
> 2016-07-20 15:19:28,259 ERROR [Reconnect to Cluster] 
> o.a.nifi.controller.StandardFlowService Handling reconnection request failed 
> due to: 
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed 
> to connect node to cluster because local flow controller partially updated. 
> Administrator should disconnect node and review flow for corruption.
> org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed 
> to connect node to cluster because local flow controller partially updated. 
> Administrator should disconnect node and review flow for corruption.
> at 
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:869)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:591)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.access$300(StandardFlowService.java:97)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService$2.run(StandardFlowService.java:403)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> Caused by: 
> org.apache.nifi.controller.serialization.FlowSynchronizationException: 
> java.lang.IllegalStateException: The specified observer identifier already 
> exists.
> at 
> org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:358)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1375)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:81)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:670)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:841)
>  [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> ... 4 common frames omitted
> Caused by: java.lang.IllegalStateException: The specified observer identifier 
> already exists.
> at 
> org.apache.nifi.logging.repository.StandardLogRepository.addObserver(StandardLogRepository.java:134)
>  ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.FlowController.createReportingTask(FlowController.java:2734)
>  

[GitHub] nifi pull request #693: NIFI-2333: Consider reporting tasks and controller s...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-2333: Consider reporting tasks and controller services when 
determining whether or not flow is empty



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

$ git pull https://github.com/markap14/nifi NIFI-2333

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

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


commit 99e92e1569173c9512926c06ce0b30aadc2d73df
Author: Mark Payne 
Date:   2016-07-20T19:25:32Z

NIFI-2333: Consider reporting tasks and controller services when 
determining whether or not flow is empty




---
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-2333) When a flow consists only of controller-level reporting tasks/controller services, nodes cannot rejoin cluster once they have disconnected

[Mark Payne (JIRA)]

Mark Payne created NIFI-2333:


 Summary: When a flow consists only of controller-level reporting 
tasks/controller services, nodes cannot rejoin cluster once they have 
disconnected
 Key: NIFI-2333
 URL: https://issues.apache.org/jira/browse/NIFI-2333
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.0.0
Reporter: Mark Payne
Assignee: Mark Payne
Priority: Blocker
 Fix For: 1.0.0


I have a cluster with 3 nodes. If I disconnect and reconnect a node with 
nothing in the flow, all works okay. If I add processors to the graph, all 
works okay. But if I have no components on the graph but define 
controller-level controller services or reporting tasks, then when I disconnect 
the node it fails to reconnect when I click 'reconnect'. I end up with the 
following stack trace:

2016-07-20 15:19:28,259 ERROR [Reconnect to Cluster] 
o.a.nifi.controller.StandardFlowService Handling reconnection request failed 
due to: org.apache.nifi.controller.serialization.FlowSynchronizationException: 
Failed to connect node to cluster because local flow controller partially 
updated. Administrator should disconnect node and review flow for corruption.
org.apache.nifi.controller.serialization.FlowSynchronizationException: Failed 
to connect node to cluster because local flow controller partially updated. 
Administrator should disconnect node and review flow for corruption.
at 
org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:869)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:591)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService.access$300(StandardFlowService.java:97)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService$2.run(StandardFlowService.java:403)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
Caused by: 
org.apache.nifi.controller.serialization.FlowSynchronizationException: 
java.lang.IllegalStateException: The specified observer identifier already 
exists.
at 
org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:358)
 ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1375) 
~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:81)
 ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:670)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:841)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
... 4 common frames omitted
Caused by: java.lang.IllegalStateException: The specified observer identifier 
already exists.
at 
org.apache.nifi.logging.repository.StandardLogRepository.addObserver(StandardLogRepository.java:134)
 ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.FlowController.createReportingTask(FlowController.java:2734)
 ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowSynchronizer.addReportingTask(StandardFlowSynchronizer.java:467)
 ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:326)
 ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
... 8 common frames omitted



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

[jira] [Commented] (NIFI-2326) In testing extension classloader loaded twice in travis causes build failures

[ASF subversion and git services (JIRA)]

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

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

Commit 2a8be95480f52975f739c8e6fc09c31c50e489e7 in nifi's branch 
refs/heads/master from [~joewitt]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2a8be95 ]

NIFI-2326 This closes #685. fixed test breaking static class causing ordering 
issues.  Addressed potential issue in NarClassLoaders for multi-init scenarios 
- now idempotent for a given config


> In testing extension classloader loaded twice in travis causes build failures
> -
>
> Key: NIFI-2326
> URL: https://issues.apache.org/jira/browse/NIFI-2326
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Minor
> Fix For: 1.0.0
>
>
> Builds in travis have failed consistently for several days starting with 
> change to how templates are serialized.  The relationship is not clear but 
> the result is
> {quote}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.008 sec <<< 
> FAILURE! - in 
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest  
> Time elapsed: 0.008 sec  <<< ERROR!
> java.lang.IllegalStateException: Extensions class loaders have already been 
> loaded.
>   at org.apache.nifi.nar.NarClassLoaders.load(NarClassLoaders.java:67)
>   at 
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest.setupSuite(StandardControllerServiceProviderTest.java:41)
> {quote}



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

[jira] [Commented] (NIFI-2326) In testing extension classloader loaded twice in travis causes build failures

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2326:
--

Github user asfgit closed the pull request at:

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


> In testing extension classloader loaded twice in travis causes build failures
> -
>
> Key: NIFI-2326
> URL: https://issues.apache.org/jira/browse/NIFI-2326
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Minor
> Fix For: 1.0.0
>
>
> Builds in travis have failed consistently for several days starting with 
> change to how templates are serialized.  The relationship is not clear but 
> the result is
> {quote}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.008 sec <<< 
> FAILURE! - in 
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest  
> Time elapsed: 0.008 sec  <<< ERROR!
> java.lang.IllegalStateException: Extensions class loaders have already been 
> loaded.
>   at org.apache.nifi.nar.NarClassLoaders.load(NarClassLoaders.java:67)
>   at 
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest.setupSuite(StandardControllerServiceProviderTest.java:41)
> {quote}



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

[jira] [Updated] (NIFI-2212) Update zero-master-cluster.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2212:

Fix Version/s: 1.0.0

> Update zero-master-cluster.png
> --
>
> Key: NIFI-2212
> URL: https://issues.apache.org/jira/browse/NIFI-2212
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
>Assignee: Rob Moran
> Fix For: 1.0.0
>
> Attachments: zero-master-cluster.png
>
>




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

[jira] [Updated] (NIFI-2211) Update zero-master-node.png

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2211:

Fix Version/s: 1.0.0

> Update zero-master-node.png
> ---
>
> Key: NIFI-2211
> URL: https://issues.apache.org/jira/browse/NIFI-2211
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
>Assignee: Rob Moran
> Fix For: 1.0.0
>
> Attachments: zero-master-node.png
>
>




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

[jira] [Updated] (NIFI-2332) When clustered, bulletins not showing the correct node

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2332:
-
Assignee: Mark Payne
  Status: Patch Available  (was: Open)

> When clustered, bulletins not showing the correct node
> --
>
> Key: NIFI-2332
> URL: https://issues.apache.org/jira/browse/NIFI-2332
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Controller-level bulletins don't show any node id. Bulletins on processors 
> always show that the bulletin originated at the Cluster Coordinator.



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

[jira] [Commented] (NIFI-2332) When clustered, bulletins not showing the correct node

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2332:
--

GitHub user markap14 opened a pull request:

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

NIFI-2332: Ensure that bulletin node address is set when clustered but not 
overwritten if already set



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

$ git pull https://github.com/markap14/nifi NIFI-2332

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

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


commit f76e0d4e48b84533893248fb51bf44f66fc25e63
Author: Mark Payne 
Date:   2016-07-20T18:59:58Z

NIFI-2332: Ensure that bulletin node address is set when clustered but not 
overwritten if already set




> When clustered, bulletins not showing the correct node
> --
>
> Key: NIFI-2332
> URL: https://issues.apache.org/jira/browse/NIFI-2332
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Controller-level bulletins don't show any node id. Bulletins on processors 
> always show that the bulletin originated at the Cluster Coordinator.



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

[jira] [Commented] (NIFI-2326) In testing extension classloader loaded twice in travis causes build failures

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2326:
--

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/685
  
LGTM! Especially like cleaning job in _TemplateSerializer_ that was causing 
me issues when investigating something in the early stages of NIFI-826 and 
ironically I had to do almost the same to get around, so +1.


> In testing extension classloader loaded twice in travis causes build failures
> -
>
> Key: NIFI-2326
> URL: https://issues.apache.org/jira/browse/NIFI-2326
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Minor
> Fix For: 1.0.0
>
>
> Builds in travis have failed consistently for several days starting with 
> change to how templates are serialized.  The relationship is not clear but 
> the result is
> {quote}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.008 sec <<< 
> FAILURE! - in 
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest  
> Time elapsed: 0.008 sec  <<< ERROR!
> java.lang.IllegalStateException: Extensions class loaders have already been 
> loaded.
>   at org.apache.nifi.nar.NarClassLoaders.load(NarClassLoaders.java:67)
>   at 
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest.setupSuite(StandardControllerServiceProviderTest.java:41)
> {quote}



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

[jira] [Commented] (NIFI-2268) HandleHttpRequest can use too many tasks and CPU

[Mark Payne (JIRA)]

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

Mark Payne commented on NIFI-2268:
--

I think I would avoid calling context.yield() as that will result in delaying 
web requests by 1 second by default. This will result in pretty poor latency 
for most web requests by default. An alternate approach would be change the 
BlockingQueue.poll() call to use BlockingQueue.poll(10, TimeUnit.MILLISECONDS) 
- this will avoid crushing the CPU but will not cause 'artificial latency'.

> HandleHttpRequest can use too many tasks and CPU
> 
>
> Key: NIFI-2268
> URL: https://issues.apache.org/jira/browse/NIFI-2268
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Michael Moser
>Priority: Minor
>
> With the default settings of HandleHttpRequest, user reports 100% CPU usage 
> and millions of scheduled tasks.  When this processor doesn't have work to 
> do, its onTrigger() should call ProcessContext.yield().  This is how the 
> ListenHTTP processor works, so it's an established pattern.



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

[jira] [Created] (NIFI-2332) When clustered, bulletins not showing the correct node

[Mark Payne (JIRA)]

Mark Payne created NIFI-2332:


 Summary: When clustered, bulletins not showing the correct node
 Key: NIFI-2332
 URL: https://issues.apache.org/jira/browse/NIFI-2332
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.0.0
Reporter: Mark Payne
Priority: Blocker
 Fix For: 1.0.0


Controller-level bulletins don't show any node id. Bulletins on processors 
always show that the bulletin originated at the Cluster Coordinator.



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

[jira] [Assigned] (NIFI-2326) In testing extension classloader loaded twice in travis causes build failures

[Joseph Witt (JIRA)]

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

Joseph Witt reassigned NIFI-2326:
-

Assignee: Joseph Witt

> In testing extension classloader loaded twice in travis causes build failures
> -
>
> Key: NIFI-2326
> URL: https://issues.apache.org/jira/browse/NIFI-2326
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Minor
> Fix For: 1.0.0
>
>
> Builds in travis have failed consistently for several days starting with 
> change to how templates are serialized.  The relationship is not clear but 
> the result is
> {quote}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.008 sec <<< 
> FAILURE! - in 
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest  
> Time elapsed: 0.008 sec  <<< ERROR!
> java.lang.IllegalStateException: Extensions class loaders have already been 
> loaded.
>   at org.apache.nifi.nar.NarClassLoaders.load(NarClassLoaders.java:67)
>   at 
> org.apache.nifi.controller.service.StandardControllerServiceProviderTest.setupSuite(StandardControllerServiceProviderTest.java:41)
> {quote}



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

[jira] [Updated] (NIFI-2320) Update screenshot images in Getting Started guide for 1.0

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2320:
-
Fix Version/s: 1.0.0

> Update screenshot images in Getting Started guide for 1.0
> -
>
> Key: NIFI-2320
> URL: https://issues.apache.org/jira/browse/NIFI-2320
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
> Fix For: 1.0.0
>
>
> The screenshots in the documentation need to be updated for the new UI.
> This ticket is for the images used or added to the Getting Started guide.



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

[jira] [Commented] (NIFI-2320) Update screenshot images in Getting Started guide for 1.0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2320:
--

GitHub user andrewmlim opened a pull request:

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

NIFI-2320 Update existing Getting Starting images with new UI images



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

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

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

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


commit 53d0e97003a2a8715953032fa43f666141a41296
Author: Andrew Lim 
Date:   2016-07-20T18:23:30Z

NIFI-2320 Update existing Getting Starting images with new UI images




> Update screenshot images in Getting Started guide for 1.0
> -
>
> Key: NIFI-2320
> URL: https://issues.apache.org/jira/browse/NIFI-2320
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>
> The screenshots in the documentation need to be updated for the new UI.
> This ticket is for the images used or added to the Getting Started guide.



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

[GitHub] nifi pull request #691: NIFI-2320 Update existing Getting Starting images wi...

[andrewmlim]

GitHub user andrewmlim opened a pull request:

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

NIFI-2320 Update existing Getting Starting images with new UI images



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

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

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

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


commit 53d0e97003a2a8715953032fa43f666141a41296
Author: Andrew Lim 
Date:   2016-07-20T18:23:30Z

NIFI-2320 Update existing Getting Starting images with new UI images




---
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-2331) Authorization: Adding a user and then deleting that user causes and error and also removes privileges to Users & Policies

[Matt Gilman (JIRA)]

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

Matt Gilman reassigned NIFI-2331:
-

Assignee: Matt Gilman

> Authorization:  Adding a user and then deleting that user causes and error 
> and also removes privileges to Users & Policies
> --
>
> Key: NIFI-2331
> URL: https://issues.apache.org/jira/browse/NIFI-2331
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Matt Gilman
>  Labels: UI
>
> Login to system as the Initial Admin User.   This user has default read & 
> write privs to Users & Policies.
> Add a new user.  Then attempt to delete that user.  This results in an error 
> "Unable to perform the desired action due to insufficient permissions.  
> Contact the system administrator." even though this should be allowed.
> If you return to main UI, the initial admin user now cannot access User and 
> Policies menu items.



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

[jira] [Created] (NIFI-2331) Authorization: Adding a user and then deleting that user causes and error and also removes privileges to Users & Policies

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2331:


 Summary: Authorization:  Adding a user and then deleting that user 
causes and error and also removes privileges to Users & Policies
 Key: NIFI-2331
 URL: https://issues.apache.org/jira/browse/NIFI-2331
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Affects Versions: 1.0.0
Reporter: Andrew Lim


Login to system as the Initial Admin User.   This user has default read & write 
privs to Users & Policies.

Add a new user.  Then attempt to delete that user.  This results in an error 
"Unable to perform the desired action due to insufficient permissions.  Contact 
the system administrator." even though this should be allowed.

If you return to main UI, the initial admin user now cannot access User and 
Policies menu items.



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

[GitHub] nifi pull request #690: NIFI-2035: Verify existence of source and destinatio...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-2035: Verify existence of source and destination when creating a…

… connection

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

$ git pull https://github.com/markap14/nifi NIFI-2035

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

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


commit 07cc1748864a69ded3a62e6cb0debe22e4183586
Author: Mark Payne 
Date:   2016-06-20T18:55:08Z

NIFI-2035: Verify existence of source and destination when creating a 
connection




---
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-2035) Connection creation needs to verify that source and destination both exist during 1st phase of 2 phase commit

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2035:
-
Status: Patch Available  (was: Open)

> Connection creation needs to verify that source and destination both exist 
> during 1st phase of 2 phase commit
> -
>
> Key: NIFI-2035
> URL: https://issues.apache.org/jira/browse/NIFI-2035
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> When a connection is created, we don't verify in the first step that both the 
> source and destination exist. In the case of a Remote Process Group, where 
> the ports change in the background, this can become problematic, we one node 
> in the cluster may not have the same ports as another and the connection 
> creation could end up failing on that node, resulting in the node getting 
> kicked out of the cluster. We should also verify that the new destination 
> exists when updating a connection if its destination changes, as this could 
> happen there as well.



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

[jira] [Commented] (NIFI-2035) Connection creation needs to verify that source and destination both exist during 1st phase of 2 phase commit

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2035:
--

GitHub user markap14 opened a pull request:

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

NIFI-2035: Verify existence of source and destination when creating a…

… connection

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

$ git pull https://github.com/markap14/nifi NIFI-2035

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

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


commit 07cc1748864a69ded3a62e6cb0debe22e4183586
Author: Mark Payne 
Date:   2016-06-20T18:55:08Z

NIFI-2035: Verify existence of source and destination when creating a 
connection




> Connection creation needs to verify that source and destination both exist 
> during 1st phase of 2 phase commit
> -
>
> Key: NIFI-2035
> URL: https://issues.apache.org/jira/browse/NIFI-2035
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> When a connection is created, we don't verify in the first step that both the 
> source and destination exist. In the case of a Remote Process Group, where 
> the ports change in the background, this can become problematic, we one node 
> in the cluster may not have the same ports as another and the connection 
> creation could end up failing on that node, resulting in the node getting 
> kicked out of the cluster. We should also verify that the new destination 
> exists when updating a connection if its destination changes, as this could 
> happen there as well.



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

[jira] [Updated] (NIFI-1972) New processor PutIgniteCache

[Pierre Villard (JIRA)]

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

Pierre Villard updated NIFI-1972:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> New processor PutIgniteCache
> 
>
> Key: NIFI-1972
> URL: https://issues.apache.org/jira/browse/NIFI-1972
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: 0.6.1
> Environment: All
>Reporter: Mans Singh
>Assignee: Mans Singh
>  Labels: cache,, ignite,, put,, streaming,
> Fix For: 1.0.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Create Nifi Ignite Processor to insert data into Apache Ignite Cache



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

[jira] [Commented] (NIFI-2305) Nodes run "Primary Node Only" processors when disconnected from cluster

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2305:
--

GitHub user markap14 opened a pull request:

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

NIFI-2305: Do not run processors that are marked as Primary Node Only…

… if disconnected from cluster

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

$ git pull https://github.com/markap14/nifi NIFI-2305-0.x

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

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


commit 05c9cc6b790ef53c6cf1e5f6ceaba85122e8ccf1
Author: Mark Payne 
Date:   2016-07-20T16:39:26Z

NIFI-2305: Do not run processors that are marked as Primary Node Only if 
disconnected from cluster




> Nodes run "Primary Node Only" processors when disconnected from cluster
> ---
>
> Key: NIFI-2305
> URL: https://issues.apache.org/jira/browse/NIFI-2305
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0, 0.8.0
>
>
> Nodes that get disconnected from the cluster start running processors that 
> are considered 'primary node only'



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

[jira] [Commented] (NIFI-2305) Nodes run "Primary Node Only" processors when disconnected from cluster

[Mark Payne (JIRA)]

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

Mark Payne commented on NIFI-2305:
--

Not a problem - PR 689 created. Thanks!


> Nodes run "Primary Node Only" processors when disconnected from cluster
> ---
>
> Key: NIFI-2305
> URL: https://issues.apache.org/jira/browse/NIFI-2305
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0, 0.8.0
>
>
> Nodes that get disconnected from the cluster start running processors that 
> are considered 'primary node only'



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

[jira] [Commented] (NIFI-1972) New processor PutIgniteCache

[ASF subversion and git services (JIRA)]

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

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

Commit 259f5bba47b2890af936419e27a4dff141a7aeaa in nifi's branch 
refs/heads/master from [~mans2singh]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=259f5bb ]

NIFI-1972 - Ignite processor

This closes #502.

Signed-off-by: Pierre Villard 


> New processor PutIgniteCache
> 
>
> Key: NIFI-1972
> URL: https://issues.apache.org/jira/browse/NIFI-1972
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: 0.6.1
> Environment: All
>Reporter: Mans Singh
>Assignee: Mans Singh
>  Labels: cache,, ignite,, put,, streaming,
> Fix For: 1.0.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Create Nifi Ignite Processor to insert data into Apache Ignite Cache



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

[GitHub] nifi pull request #689: NIFI-2305: Do not run processors that are marked as ...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-2305: Do not run processors that are marked as Primary Node Only…

… if disconnected from cluster

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

$ git pull https://github.com/markap14/nifi NIFI-2305-0.x

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

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


commit 05c9cc6b790ef53c6cf1e5f6ceaba85122e8ccf1
Author: Mark Payne 
Date:   2016-07-20T16:39:26Z

NIFI-2305: Do not run processors that are marked as Primary Node Only if 
disconnected from cluster




---
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 #502: Nifi-1972 Apache Ignite Put Cache Processor

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #688: NIFI-2304: If node address is not set, default to lo...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-2304: If node address is not set, default to localhost, as the a…

…dmin guide says it should

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

$ git pull https://github.com/markap14/nifi NIFI-2304

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

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


commit c7415177426d7a18a7bdb54af0b57066dc5d5dbb
Author: Mark Payne 
Date:   2016-07-20T16:21:58Z

NIFI-2304: If node address is not set, default to localhost, as the admin 
guide says it should




---
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-2304) Cluster Coordinator reported incorrectly

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2304:
-
Status: Patch Available  (was: Open)

> Cluster Coordinator reported incorrectly
> 
>
> Key: NIFI-2304
> URL: https://issues.apache.org/jira/browse/NIFI-2304
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Bryan Bende
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.0.0
>
>
> I created a two node cluster locally, running embedded ZK on node1.. both 
> nodes start up, but when trying to access the UI on the second node, it says 
> no coordinator exists. 
> Looking in the logs the coordinator is being reported as ":8889" where 8889 
> is the node protocol port. I left the node host blank assuming it would 
> default to localhost, but looks like it isn't. When I filled in the node host 
> everything worked as expected.



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

[jira] [Commented] (NIFI-2304) Cluster Coordinator reported incorrectly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2304:
--

GitHub user markap14 opened a pull request:

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

NIFI-2304: If node address is not set, default to localhost, as the a…

…dmin guide says it should

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

$ git pull https://github.com/markap14/nifi NIFI-2304

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

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


commit c7415177426d7a18a7bdb54af0b57066dc5d5dbb
Author: Mark Payne 
Date:   2016-07-20T16:21:58Z

NIFI-2304: If node address is not set, default to localhost, as the admin 
guide says it should




> Cluster Coordinator reported incorrectly
> 
>
> Key: NIFI-2304
> URL: https://issues.apache.org/jira/browse/NIFI-2304
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Bryan Bende
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.0.0
>
>
> I created a two node cluster locally, running embedded ZK on node1.. both 
> nodes start up, but when trying to access the UI on the second node, it says 
> no coordinator exists. 
> Looking in the logs the coordinator is being reported as ":8889" where 8889 
> is the node protocol port. I left the node host blank assuming it would 
> default to localhost, but looks like it isn't. When I filled in the node host 
> everything worked as expected.



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

[jira] [Updated] (NIFI-2298) Add missing futures for ConsumeKafka

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky updated NIFI-2298:
---
Status: Patch Available  (was: Open)

NOTE to merger: Make sure it is merged to both master and 0.x branches

> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Oleg Zhurakousky
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[jira] [Commented] (NIFI-2298) Add missing futures for ConsumeKafka

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2298:
--

GitHub user olegz opened a pull request:

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

NIFI-2298 added Kafka consume attributes to a FlowFile



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

$ git pull https://github.com/olegz/nifi NIFI-2298

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

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


commit f0b62d477882b65fba84b94a0e5067749a5f6ee4
Author: Oleg Zhurakousky 
Date:   2016-07-20T16:18:55Z

NIFI-2298 added Kafka consume attributes to a FlowFile




> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Oleg Zhurakousky
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[GitHub] nifi pull request #687: NIFI-2298 added Kafka consume attributes to a FlowFi...

[olegz]

GitHub user olegz opened a pull request:

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

NIFI-2298 added Kafka consume attributes to a FlowFile



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

$ git pull https://github.com/olegz/nifi NIFI-2298

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

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


commit f0b62d477882b65fba84b94a0e5067749a5f6ee4
Author: Oleg Zhurakousky 
Date:   2016-07-20T16:18:55Z

NIFI-2298 added Kafka consume attributes to a FlowFile




---
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-2319) When clicking View FlowFiles on a connection, I am seeing only the FlowFiles on the node I'm connected to

[Joseph Percivall (JIRA)]

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

Joseph Percivall resolved NIFI-2319.

Resolution: Fixed

> When clicking View FlowFiles on a connection, I am seeing only the FlowFiles 
> on the node I'm connected to
> -
>
> Key: NIFI-2319
> URL: https://issues.apache.org/jira/browse/NIFI-2319
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>
> When I right-click on a connection and choose View FlowFiles, when running a 
> clustered instance of NiFi, I see only the FlowFiles that are on the node I'm 
> connected to. Unless I am connected to the currently elected cluster 
> coordinator - then I see the correct response, which is the merged result 
> from all nodes.



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

[jira] [Commented] (NIFI-2319) When clicking View FlowFiles on a connection, I am seeing only the FlowFiles on the node I'm connected to

[ASF subversion and git services (JIRA)]

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

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

Commit 2a7f135f1c8c9a31b1084860419383f4196e386c in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2a7f135 ]

NIFI-2319: Ensure that when we set cluster node id's and node addresses, that 
we do so only if they are not already populated

This closes #680

Signed-off-by: jpercivall 


> When clicking View FlowFiles on a connection, I am seeing only the FlowFiles 
> on the node I'm connected to
> -
>
> Key: NIFI-2319
> URL: https://issues.apache.org/jira/browse/NIFI-2319
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>
> When I right-click on a connection and choose View FlowFiles, when running a 
> clustered instance of NiFi, I see only the FlowFiles that are on the node I'm 
> connected to. Unless I am connected to the currently elected cluster 
> coordinator - then I see the correct response, which is the merged result 
> from all nodes.



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

[GitHub] nifi pull request #680: NIFI-2319: Ensure that when we set cluster node id's...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2319) When clicking View FlowFiles on a connection, I am seeing only the FlowFiles on the node I'm connected to

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2319:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/680
  
+1

Visually verified code and did a contrib check build. I built a secure 3 
node cluster and tested various different logic paths related to 
viewing/emptying the queue and they all worked as expected. Thanks @markap14, I 
will merge it in.


> When clicking View FlowFiles on a connection, I am seeing only the FlowFiles 
> on the node I'm connected to
> -
>
> Key: NIFI-2319
> URL: https://issues.apache.org/jira/browse/NIFI-2319
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>
> When I right-click on a connection and choose View FlowFiles, when running a 
> clustered instance of NiFi, I see only the FlowFiles that are on the node I'm 
> connected to. Unless I am connected to the currently elected cluster 
> coordinator - then I see the correct response, which is the merged result 
> from all nodes.



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

[GitHub] nifi issue #680: NIFI-2319: Ensure that when we set cluster node id's and no...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/680
  
+1

Visually verified code and did a contrib check build. I built a secure 3 
node cluster and tested various different logic paths related to 
viewing/emptying the queue and they all worked as expected. Thanks @markap14, I 
will merge it in.


---
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-2330) If unable to connect to cluster, node loads an empty flow instead of loading current flow

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2330:
--

GitHub user markap14 opened a pull request:

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

NIFI-2330: Ensure that we set ProcessGroupDTO's contents after popula…

…ting sets of components, as the contents dto now copies the sets

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

$ git pull https://github.com/markap14/nifi NIFI-2330

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

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


commit 4b22d8358b73126f7f062fcba3617df2198a6385
Author: Mark Payne 
Date:   2016-07-20T15:57:41Z

NIFI-2330: Ensure that we set ProcessGroupDTO's contents after populating 
sets of components, as the contents dto now copies the sets




> If unable to connect to cluster, node loads an empty flow instead of loading 
> current flow
> -
>
> Key: NIFI-2330
> URL: https://issues.apache.org/jira/browse/NIFI-2330
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> I have a three-node cluster that has a dataflow established. If I shut down 
> all nodes and start only one (running embedded zookeeper) so that the node is 
> not able to connect to cluster due to not able to reach zookeeper - the node 
> should load the current flow from disk and begin processing it. However, it 
> instead loads an empty flow, as is evident by navigating to the URI of the 
> node and seeing nothing on the canvas.



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

[GitHub] nifi pull request #686: NIFI-2330: Ensure that we set ProcessGroupDTO's cont...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-2330: Ensure that we set ProcessGroupDTO's contents after popula…

…ting sets of components, as the contents dto now copies the sets

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

$ git pull https://github.com/markap14/nifi NIFI-2330

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

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


commit 4b22d8358b73126f7f062fcba3617df2198a6385
Author: Mark Payne 
Date:   2016-07-20T15:57:41Z

NIFI-2330: Ensure that we set ProcessGroupDTO's contents after populating 
sets of components, as the contents dto now copies the sets




---
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-2330) If unable to connect to cluster, node loads an empty flow instead of loading current flow

[Mark Payne (JIRA)]

Mark Payne created NIFI-2330:


 Summary: If unable to connect to cluster, node loads an empty flow 
instead of loading current flow
 Key: NIFI-2330
 URL: https://issues.apache.org/jira/browse/NIFI-2330
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.0.0
Reporter: Mark Payne
Priority: Blocker
 Fix For: 1.0.0


I have a three-node cluster that has a dataflow established. If I shut down all 
nodes and start only one (running embedded zookeeper) so that the node is not 
able to connect to cluster due to not able to reach zookeeper - the node should 
load the current flow from disk and begin processing it. However, it instead 
loads an empty flow, as is evident by navigating to the URI of the node and 
seeing nothing on the canvas.



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

[jira] [Commented] (NIFI-2324) If we reach the maximum number of outstanding HTTP requests, logs should indicate which requests are outstanding

[ASF subversion and git services (JIRA)]

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

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

Commit 108c815988c8473989ebff35eb0f89120cb5cc19 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=108c815 ]

NIFI-2324: Log number of requests per URI if we have too many outstanding 
requests to replicate

This closes #683

Signed-off-by: jpercivall 


> If we reach the maximum number of outstanding HTTP requests, logs should 
> indicate which requests are outstanding
> 
>
> Key: NIFI-2324
> URL: https://issues.apache.org/jira/browse/NIFI-2324
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>




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

[jira] [Commented] (NIFI-2324) If we reach the maximum number of outstanding HTTP requests, logs should indicate which requests are outstanding

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2324:
--

Github user asfgit closed the pull request at:

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


> If we reach the maximum number of outstanding HTTP requests, logs should 
> indicate which requests are outstanding
> 
>
> Key: NIFI-2324
> URL: https://issues.apache.org/jira/browse/NIFI-2324
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>




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

[jira] [Updated] (NIFI-2324) If we reach the maximum number of outstanding HTTP requests, logs should indicate which requests are outstanding

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2324:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> If we reach the maximum number of outstanding HTTP requests, logs should 
> indicate which requests are outstanding
> 
>
> Key: NIFI-2324
> URL: https://issues.apache.org/jira/browse/NIFI-2324
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>




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

[jira] [Resolved] (NIFI-2327) nifi.apache.org web site has JS error: a.indexOf is not a function

[Koji Kawamura (JIRA)]

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

Koji Kawamura resolved NIFI-2327.
-
Resolution: Fixed
  Assignee: Koji Kawamura

I've add a workaround to limit JQuery version to 2.1.4. Confirmed the JS error 
is gone.

> nifi.apache.org web site has JS error: a.indexOf is not a function
> --
>
> Key: NIFI-2327
> URL: https://issues.apache.org/jira/browse/NIFI-2327
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>
> It was the first time for me to build and update the Apache NiFi Web site. 
> When I execute bower install without any bower component cache, JQuery 
> version had been updated from 2.1.4 to 3.1.0.
> Unfortunately JQuery 3.x has a breaking change affecting foundation.js. The 
> latest foundation.js [adds JQuery version limit up to 2.1.0 | 
> https://github.com/zurb/bower-foundation/commit/15d98294916c50ce8e6838bc035f4f136d4dc704]
>  for this. But this change has not been released as of this writing.
> A possible workaround is adding JQuery version limit at nifi-site/bower.json.



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

[jira] [Updated] (NIFI-2329) User authorization: Able to create a users with the same name which causes that user to lose User & Policies privileges

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2329:
-
Description: 
I had an initial admin user who had default privs to access and modify Users & 
Policies.  The UI allowed me to create another user with the same name.   After 
that, the user could no longer access Users (get the error "Unable to perform 
the desired action due to insufficient permissions. Contact the system 
administrator.") and can get into the Policies window, but can no longer make 
changes and see the message "Not authorized to access the policy for the 
specified resource."


  was:
I had an initial admin user who had default privs to access and modify Users & 
Policies.  The UI allowed me to create another user with the same name.   After 
that, the user could no longer access Users (get the error "Unable to perform 
the desired action due to insufficient permissions. Contact the system 
administrator." and can get into the Policies window, but can no longer make 
changes and see the message "Not authorized to access the policy for the 
specified resource."



> User authorization:  Able to create a users with the same name which causes 
> that user to lose User & Policies privileges
> 
>
> Key: NIFI-2329
> URL: https://issues.apache.org/jira/browse/NIFI-2329
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Priority: Critical
>
> I had an initial admin user who had default privs to access and modify Users 
> & Policies.  The UI allowed me to create another user with the same name.   
> After that, the user could no longer access Users (get the error "Unable to 
> perform the desired action due to insufficient permissions. Contact the 
> system administrator.") and can get into the Policies window, but can no 
> longer make changes and see the message "Not authorized to access the policy 
> for the specified resource."



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