[jira] [Commented] (NIFI-1833) Add support for Azure Blob Storage and Table Storage

[Lev Brailovskiy (JIRA)]

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

Lev Brailovskiy commented on NIFI-1833:
---

When you expect this commit to be merged?

> Add support for Azure Blob Storage and Table Storage
> 
>
> Key: NIFI-1833
> URL: https://issues.apache.org/jira/browse/NIFI-1833
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Simon Elliston Ball
>Priority: Minor
>
> It would be useful to have an Azure equivalent of the current S3 capability. 
> Azure also provides a Table storage mechanism, providing simple key value 
> storage. Since the Azure SDKs are Apache Licensed, this should be reasonably 
> straightforward. A first cut is available as an addition to the existing 
> azure bundle.



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

[jira] [Updated] (NIFI-2566) Clustered Nodes can become out of sync regarding which node is coordinator

[Joseph Percivall (JIRA)]

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

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

> Clustered Nodes can become out of sync regarding which node is coordinator
> --
>
> Key: NIFI-2566
> URL: https://issues.apache.org/jira/browse/NIFI-2566
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Occasionally, I will see the UI telling me that no Cluster Coordinator has 
> been elected. However, I can see in the logs that the node is sending 
> heartbeats to the coordinator.



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

[jira] [Commented] (NIFI-2566) Clustered Nodes can become out of sync regarding which node is coordinator

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2566:
--

Github user asfgit closed the pull request at:

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


> Clustered Nodes can become out of sync regarding which node is coordinator
> --
>
> Key: NIFI-2566
> URL: https://issues.apache.org/jira/browse/NIFI-2566
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Occasionally, I will see the UI telling me that no Cluster Coordinator has 
> been elected. However, I can see in the logs that the node is sending 
> heartbeats to the coordinator.



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

[jira] [Commented] (NIFI-2566) Clustered Nodes can become out of sync regarding which node is coordinator

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2566: Refactored to allow just the Leader Election Manager to be 
responsible for determining who is the Cluster Coordinator

NIFI-2566: Removed storage of cluster roles from heartbeats and 
NodeConnectionStatus; use LeaderElectionManager to determine roles instead

NIFI-2566: Updated Heartbeats so that if a node is out-of-sync with cluster 
topology, cluster coordinator will provide updated information back to the nodes

NIFI-2566: Fixed issue that prevented standalone instance from starting by 
creating a standalone-instance version of the Leader Election Manager. Also 
added Controller Service enabled/disabled state to fingerprint rather than 
attempting to update the state when joining the cluster, as the implementation 
was incorrect and the correct implementation will be a rather significant 
effort that doesn't have to happen for 1.0.0 release

This closes #866

Signed-off-by: jpercivall 


> Clustered Nodes can become out of sync regarding which node is coordinator
> --
>
> Key: NIFI-2566
> URL: https://issues.apache.org/jira/browse/NIFI-2566
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Occasionally, I will see the UI telling me that no Cluster Coordinator has 
> been elected. However, I can see in the logs that the node is sending 
> heartbeats to the coordinator.



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

[jira] [Commented] (NIFI-2566) Clustered Nodes can become out of sync regarding which node is coordinator

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2566: Refactored to allow just the Leader Election Manager to be 
responsible for determining who is the Cluster Coordinator

NIFI-2566: Removed storage of cluster roles from heartbeats and 
NodeConnectionStatus; use LeaderElectionManager to determine roles instead

NIFI-2566: Updated Heartbeats so that if a node is out-of-sync with cluster 
topology, cluster coordinator will provide updated information back to the nodes

NIFI-2566: Fixed issue that prevented standalone instance from starting by 
creating a standalone-instance version of the Leader Election Manager. Also 
added Controller Service enabled/disabled state to fingerprint rather than 
attempting to update the state when joining the cluster, as the implementation 
was incorrect and the correct implementation will be a rather significant 
effort that doesn't have to happen for 1.0.0 release

This closes #866

Signed-off-by: jpercivall 


> Clustered Nodes can become out of sync regarding which node is coordinator
> --
>
> Key: NIFI-2566
> URL: https://issues.apache.org/jira/browse/NIFI-2566
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Occasionally, I will see the UI telling me that no Cluster Coordinator has 
> been elected. However, I can see in the logs that the node is sending 
> heartbeats to the coordinator.



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

[jira] [Commented] (NIFI-2566) Clustered Nodes can become out of sync regarding which node is coordinator

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2566: Refactored to allow just the Leader Election Manager to be 
responsible for determining who is the Cluster Coordinator

NIFI-2566: Removed storage of cluster roles from heartbeats and 
NodeConnectionStatus; use LeaderElectionManager to determine roles instead

NIFI-2566: Updated Heartbeats so that if a node is out-of-sync with cluster 
topology, cluster coordinator will provide updated information back to the nodes

NIFI-2566: Fixed issue that prevented standalone instance from starting by 
creating a standalone-instance version of the Leader Election Manager. Also 
added Controller Service enabled/disabled state to fingerprint rather than 
attempting to update the state when joining the cluster, as the implementation 
was incorrect and the correct implementation will be a rather significant 
effort that doesn't have to happen for 1.0.0 release

This closes #866

Signed-off-by: jpercivall 


> Clustered Nodes can become out of sync regarding which node is coordinator
> --
>
> Key: NIFI-2566
> URL: https://issues.apache.org/jira/browse/NIFI-2566
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Occasionally, I will see the UI telling me that no Cluster Coordinator has 
> been elected. However, I can see in the logs that the node is sending 
> heartbeats to the coordinator.



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

[jira] [Commented] (NIFI-2566) Clustered Nodes can become out of sync regarding which node is coordinator

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2566: Refactored to allow just the Leader Election Manager to be 
responsible for determining who is the Cluster Coordinator

NIFI-2566: Removed storage of cluster roles from heartbeats and 
NodeConnectionStatus; use LeaderElectionManager to determine roles instead

NIFI-2566: Updated Heartbeats so that if a node is out-of-sync with cluster 
topology, cluster coordinator will provide updated information back to the nodes

NIFI-2566: Fixed issue that prevented standalone instance from starting by 
creating a standalone-instance version of the Leader Election Manager. Also 
added Controller Service enabled/disabled state to fingerprint rather than 
attempting to update the state when joining the cluster, as the implementation 
was incorrect and the correct implementation will be a rather significant 
effort that doesn't have to happen for 1.0.0 release

This closes #866

Signed-off-by: jpercivall 


> Clustered Nodes can become out of sync regarding which node is coordinator
> --
>
> Key: NIFI-2566
> URL: https://issues.apache.org/jira/browse/NIFI-2566
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Occasionally, I will see the UI telling me that no Cluster Coordinator has 
> been elected. However, I can see in the logs that the node is sending 
> heartbeats to the coordinator.



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

[jira] [Commented] (NIFI-2574) Update NiFiProperties usage to a context based accessor rather than static singleton

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2574:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/872
  
As of right now, I have merged these commits into [PR 
834](https://github.com/apache/nifi/pull/834/commits/d4ad014cf6ba0ded6a69f3532aacf41ce0260b89)
 and the build compiles, checkstyle passes, and all current tests pass. 

There is still substantial cleanup work to do and because of the change 
from `NiFiProperties.getInstance()` to using `NiFiPropertiesLoader.get()`, the 
integration with Spring for *web-api* still needs to occur. 

Thanks for the help @joewitt . 


> Update NiFiProperties usage to a context based accessor rather than static 
> singleton
> 
>
> Key: NIFI-2574
> URL: https://issues.apache.org/jira/browse/NIFI-2574
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Configuration, Core Framework
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>  Labels: migration
> Fix For: 1.0.0
>
>
> This is a key step to move our longstanding odd static singleton usage of 
> NiFiProperties which enables a loader to exist which will encapsulate all 
> logic for dealing with encrypted properties as is the goal of the parent task.



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

[GitHub] nifi issue #872: NIFI-2574 checkpoint commit to allow 1831 progress

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/872
  
As of right now, I have merged these commits into [PR 
834](https://github.com/apache/nifi/pull/834/commits/d4ad014cf6ba0ded6a69f3532aacf41ce0260b89)
 and the build compiles, checkstyle passes, and all current tests pass. 

There is still substantial cleanup work to do and because of the change 
from `NiFiProperties.getInstance()` to using `NiFiPropertiesLoader.get()`, the 
integration with Spring for *web-api* still needs to occur. 

Thanks for the help @joewitt . 


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

[GitHub] nifi issue #877: QueryDatabaseTable updates

[patricker]

Github user patricker commented on the issue:

https://github.com/apache/nifi/pull/877
  
Yeah, I haven't loaded in the NiFi style guide into IntelliJ; it was just 
trying to be helpful with the * imports.

Should be all updated.

All of my test cases are very positive outcome focused; not sure if you 
guys have any goals surrounding negative testing.


---
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 #877: QueryDatabaseTable updates

[mattyb149]

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

https://github.com/apache/nifi/pull/877#discussion_r75051917
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/QueryDatabaseTableTest.java
 ---
@@ -43,16 +43,9 @@
 import java.io.File;
 import java.io.IOException;
 import java.io.InputStream;
-import java.sql.Connection;
-import java.sql.DriverManager;
-import java.sql.SQLException;
-import java.sql.SQLNonTransientConnectionException;
-import java.sql.Statement;
-import java.sql.Types;
-import java.util.Arrays;
-import java.util.Collections;
-import java.util.HashMap;
-import java.util.Map;
+import java.sql.*;
+import java.text.SimpleDateFormat;
+import java.util.*;
--- End diff --

Same comments as above about star imports


---
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 #877: QueryDatabaseTable updates

[mattyb149]

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

https://github.com/apache/nifi/pull/877#discussion_r75051853
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/QueryDatabaseTable.java
 ---
@@ -260,6 +310,20 @@ protected String getQuery(DatabaseAdapter dbAdapter, 
String tableName, String co
 }
 
 
+protected Map getDefaultMaxValueProperties(final 
Map properties){
+final Map defaultMaxValues = new HashMap();
+
+for (final Map.Entry entry : 
properties.entrySet()) {
+final String key = entry.getKey().getName();
+
+if(!key.startsWith(INTIIAL_MAX_VALUE_PROP_START)) continue;
--- End diff --

Not sure (yet) if our checkstyle allows the one-line-if, but if you're 
already in here making changes, could you add the explicit braces? Superfluous 
I know, but consistent and extensible :)


---
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 #877: QueryDatabaseTable updates

[mattyb149]

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

https://github.com/apache/nifi/pull/877#discussion_r75051737
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/QueryDatabaseTable.java
 ---
@@ -75,10 +66,19 @@
 + "to fetch only those records that have max values greater than 
the retained values. This can be used for "
 + "incremental fetching, fetching of newly added rows, etc. To 
clear the maximum values, clear the state of the processor "
 + "per the State Management documentation")
-@WritesAttribute(attribute = "querydbtable.row.count")
+@WritesAttributes({
+@WritesAttribute(attribute = "querydbtable.row.count"),
+@WritesAttribute(attribute="fragment.identifier", description="If 
'Max Rows in Flow File' is set then all FlowFiles from the same query result 
set "
++ "will have the same value for the fragment.identifier 
attribute. This can then be used to correlate the results."),
+@WritesAttribute(attribute="fragment.index", description="If 'Max 
Rows in Flow File' is set then the position of this FlowFile in the list of 
outgoing FlowFiles that were all derived from the same result set FlowFile. 
This can be "
++ "used in conjunction with the fragment.identifier 
attribute to know which FlowFiles originated from the same query result set and 
in what order  "
++ "FlowFiles were produced")})
+@DynamicProperty(name = "Initial Max Value", value = "Attribute Expression 
Language", supportsExpressionLanguage = false, description = "Specifies an 
initial "
--- End diff --

This is excellent use of documentation!


---
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 #877: QueryDatabaseTable updates

[mattyb149]

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

https://github.com/apache/nifi/pull/877#discussion_r75051588
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/QueryDatabaseTable.java
 ---
@@ -90,6 +90,15 @@
 
.addValidator(StandardValidators.NON_NEGATIVE_INTEGER_VALIDATOR)
 .build();
 
+public static final PropertyDescriptor MAX_ROWS_PER_FLOW_FILE = new 
PropertyDescriptor.Builder()
+.name("Max Rows in Flow File")
--- End diff --

Maybe "Max Rows Per Flow File"? minor/cosmetic point but might make it more 
clear for users. Would need to be changed elsewhere in the file for consistency


---
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-2585) Add attributes to track where a flow file came from when receiving over site-to-site

[Bryan Bende (JIRA)]

Bryan Bende created NIFI-2585:
-

 Summary: Add attributes to track where a flow file came from when 
receiving over site-to-site
 Key: NIFI-2585
 URL: https://issues.apache.org/jira/browse/NIFI-2585
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Bryan Bende
Priority: Minor
 Fix For: 1.1.0


With MiNiFi starting be used to send data to a central NiFi, it would be 
helpful if information about the sending host and port was added to each flow 
file received over site-to-site. Currently this information is available and 
used to generate the transit URI in the RECEIVE event, but this information 
isn't available to downstream processors that might want to make routing 
decisions.

For reference:
https://github.com/apache/nifi/blob/e23b2356172e128086585fe2c425523c3628d0e7/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-site-to-site/src/main/java/org/apache/nifi/remote/protocol/AbstractFlowFileServerProtocol.java#L452

A possible approach might be to add two attributes to each flow file, something 
like "remote.host" and "remote.address" where remote.host has only the sending 
hostname, and remote.address has the sending host and port.



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

[GitHub] nifi pull request #877: QueryDatabaseTable updates

[mattyb149]

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

https://github.com/apache/nifi/pull/877#discussion_r75051357
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/QueryDatabaseTable.java
 ---
@@ -90,6 +90,15 @@
 
.addValidator(StandardValidators.NON_NEGATIVE_INTEGER_VALIDATOR)
 .build();
 
+public static final PropertyDescriptor MAX_ROWS_PER_FLOW_FILE = new 
PropertyDescriptor.Builder()
+.name("Max Rows in Flow File")
+.description("The maximum number of result rows that will be 
included in a single FlowFile. " +
--- End diff --

Good idea! I like it :) Lately we've been encouraging folks to add the 
"friendly" name (like "Max Rows in Flow File") using displayName() in the 
builder, and something like "qdbt-max-rows" as the name(), to help with 
internationalization. I realize the other properties don't follow this, and 
it's not a requirement, just mentioning it here to get the word out :)


---
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 #877: QueryDatabaseTable updates

[mattyb149]

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

https://github.com/apache/nifi/pull/877#discussion_r75051154
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/QueryDatabaseTable.java
 ---
@@ -17,11 +17,8 @@
 package org.apache.nifi.processors.standard;
 
 import org.apache.commons.lang3.StringUtils;
-import org.apache.nifi.annotation.behavior.EventDriven;
-import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.*;
--- End diff --

Our coding standards discourage the use of star imports, mind replacing 
this with the individual imports? Please and thanks!


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

[jira] [Commented] (NIFI-2584) PutSQL Timestamp Format Issue

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2584:
--

GitHub user patricker opened a pull request:

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

NIFI-2584

In NIFI-2576 I mistakenly put 'hh' into my timestamp format rather than 
'HH', so it was running on 12-hour formatting without an am/pm qualifier. The 
correct format is 'HH'.

I fixed the test case to identify this issue.

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

$ git pull https://github.com/patricker/nifi NIFI-2584

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

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


commit 0198eb73f3b32caec68edb4d49509d79e66184c3
Author: Peter Wicks 
Date:   2016-08-17T01:16:44Z

NIFI-2584




> PutSQL Timestamp Format Issue
> -
>
> Key: NIFI-2584
> URL: https://issues.apache.org/jira/browse/NIFI-2584
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Peter Wicks
>
> In NIFI-2576 I mistakenly put 'hh' into my timestamp format rather than 'HH', 
> so it was running on 12-hour formatting without an am/pm qualifier.  The 
> correct format is 'HH'.



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

[GitHub] nifi pull request #878: NIFI-2584

[patricker]

GitHub user patricker opened a pull request:

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

NIFI-2584

In NIFI-2576 I mistakenly put 'hh' into my timestamp format rather than 
'HH', so it was running on 12-hour formatting without an am/pm qualifier. The 
correct format is 'HH'.

I fixed the test case to identify this issue.

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

$ git pull https://github.com/patricker/nifi NIFI-2584

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

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


commit 0198eb73f3b32caec68edb4d49509d79e66184c3
Author: Peter Wicks 
Date:   2016-08-17T01:16:44Z

NIFI-2584




---
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-2582) QueryDatabaseTable should support splitting the ResultSet into multiple flow files

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2582:
--

GitHub user patricker opened a pull request:

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

QueryDatabaseTable updates

NIFI-2582 - QueryDatabaseTable should support splitting the ResultSet into 
multiple flow files
NIFI-2583 - QueryDatabaseTable should allow you to specify an initial Max 
Value

Appropriate Unit Tests have also been developed.

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

$ git pull https://github.com/patricker/nifi QDB2

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

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


commit 7c3419839559072b75e9a7cc5402b8f3e97c116e
Author: Peter Wicks 
Date:   2016-08-17T01:10:16Z

NIFI-2582
NIFI-2583




> QueryDatabaseTable should support splitting the ResultSet into multiple flow 
> files
> --
>
> Key: NIFI-2582
> URL: https://issues.apache.org/jira/browse/NIFI-2582
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Peter Wicks
>
> A new Property, that defaults to disabled, should allow for ResultSets to be 
> split up into multiple output flow files.



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

[GitHub] nifi pull request #877: QueryDatabaseTable updates

[patricker]

GitHub user patricker opened a pull request:

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

QueryDatabaseTable updates

NIFI-2582 - QueryDatabaseTable should support splitting the ResultSet into 
multiple flow files
NIFI-2583 - QueryDatabaseTable should allow you to specify an initial Max 
Value

Appropriate Unit Tests have also been developed.

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

$ git pull https://github.com/patricker/nifi QDB2

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

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


commit 7c3419839559072b75e9a7cc5402b8f3e97c116e
Author: Peter Wicks 
Date:   2016-08-17T01:10:16Z

NIFI-2582
NIFI-2583




---
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-2582) QueryDatabaseTable should support splitting the ResultSet into multiple flow files

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2582:
--

Github user patricker closed the pull request at:

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


> QueryDatabaseTable should support splitting the ResultSet into multiple flow 
> files
> --
>
> Key: NIFI-2582
> URL: https://issues.apache.org/jira/browse/NIFI-2582
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Peter Wicks
>
> A new Property, that defaults to disabled, should allow for ResultSets to be 
> split up into multiple output flow files.



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

[GitHub] nifi pull request #876: QueryDatabaseTable updates

[patricker]

Github user patricker closed the pull request at:

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


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

[GitHub] nifi issue #866: NIFI-2566: Refactoring to improve robustness of cluster

[JPercivall]

Github user JPercivall commented on the issue:

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

Visually verified code, and did a contrib check build rebased to master. In 
a 3 node secure cluster did all sorts of tests involving connecting, 
disconnecting, restarting, and starting/stopping components. All behaved 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.
---

[GitHub] nifi issue #850: NIFI-2547: Add DeleteHDFS Processor

[mattyb149]

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/850
  
Just a couple of minor comments; otherwise looks great, thanks!


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

[jira] [Commented] (NIFI-2547) Add DeleteHDFS Processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2547:
--

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

https://github.com/apache/nifi/pull/850#discussion_r75044365
  
--- Diff: 
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/test/java/org/apache/nifi/processors/hadoop/TestDeleteHDFS.java
 ---
@@ -0,0 +1,187 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.hadoop;
+
+import static org.junit.Assert.assertEquals;
+import static org.mockito.Mockito.any;
+import static org.mockito.Mockito.mock;
+import static org.mockito.Mockito.when;
+
+import java.io.IOException;
+import java.util.List;
+import java.util.Map;
+
+import org.apache.hadoop.fs.FileStatus;
+import org.apache.hadoop.fs.FileSystem;
+import org.apache.hadoop.fs.Path;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.hadoop.KerberosProperties;
+import org.apache.nifi.util.MockFlowFile;
+import org.apache.nifi.util.NiFiProperties;
+import org.apache.nifi.util.TestRunner;
+import org.apache.nifi.util.TestRunners;
+import org.junit.Before;
+import org.junit.Test;
+
+import com.google.common.collect.Maps;
+
+public class TestDeleteHDFS {
+private NiFiProperties mockNiFiProperties;
+private FileSystem mockFileSystem;
+private KerberosProperties kerberosProperties;
+
+@Before
+public void setup() throws Exception {
+mockNiFiProperties = mock(NiFiProperties.class);
+
when(mockNiFiProperties.getKerberosConfigurationFile()).thenReturn(null);
+kerberosProperties = KerberosProperties.create(mockNiFiProperties);
+mockFileSystem = mock(FileSystem.class);
--- End diff --

Is it better to mock here or use the target/ area (since HDFS defaults to 
local FS) for file existence, deletion, etc.?


> Add DeleteHDFS Processor 
> -
>
> Key: NIFI-2547
> URL: https://issues.apache.org/jira/browse/NIFI-2547
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Ricky Saltzer
>Assignee: Ricky Saltzer
>
> There are times where a user may want to remove a file or directory from 
> HDFS. The reasons for this vary, but to provide some context, I currently 
> have a pipeline where I need to periodically delete files that my NiFi 
> pipeline is producing. In my case, it's a "Delete files after they are 7 days 
> old". 
> Currently, I have to use the {{ExecuteStreamCommand}} processor and manually 
> call {{hdfs dfs -rm}}, which is awful when dealing with a large amount of 
> files. For one, an entire JVM is spun up for each delete, and two, when 
> deleting directories with thousands of files, it can sometimes cause the 
> command to hang indefinitely. 
> With that being said, I am proposing we add a {{DeleteHDFS}} processor which 
> meets the following criteria. 
> * Can delete both directories and files
> * Can delete directories recursively
> * Supports the dynamic expression language 
> * Supports using glob paths (e.g. /data/for/2017/08/*)
> * Capable of being a downstream processor as well as a standalone processor



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

[GitHub] nifi pull request #850: NIFI-2547: Add DeleteHDFS Processor

[mattyb149]

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

https://github.com/apache/nifi/pull/850#discussion_r75044365
  
--- Diff: 
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/test/java/org/apache/nifi/processors/hadoop/TestDeleteHDFS.java
 ---
@@ -0,0 +1,187 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.hadoop;
+
+import static org.junit.Assert.assertEquals;
+import static org.mockito.Mockito.any;
+import static org.mockito.Mockito.mock;
+import static org.mockito.Mockito.when;
+
+import java.io.IOException;
+import java.util.List;
+import java.util.Map;
+
+import org.apache.hadoop.fs.FileStatus;
+import org.apache.hadoop.fs.FileSystem;
+import org.apache.hadoop.fs.Path;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.hadoop.KerberosProperties;
+import org.apache.nifi.util.MockFlowFile;
+import org.apache.nifi.util.NiFiProperties;
+import org.apache.nifi.util.TestRunner;
+import org.apache.nifi.util.TestRunners;
+import org.junit.Before;
+import org.junit.Test;
+
+import com.google.common.collect.Maps;
+
+public class TestDeleteHDFS {
+private NiFiProperties mockNiFiProperties;
+private FileSystem mockFileSystem;
+private KerberosProperties kerberosProperties;
+
+@Before
+public void setup() throws Exception {
+mockNiFiProperties = mock(NiFiProperties.class);
+
when(mockNiFiProperties.getKerberosConfigurationFile()).thenReturn(null);
+kerberosProperties = KerberosProperties.create(mockNiFiProperties);
+mockFileSystem = mock(FileSystem.class);
--- End diff --

Is it better to mock here or use the target/ area (since HDFS defaults to 
local FS) for file existence, deletion, etc.?


---
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-2547) Add DeleteHDFS Processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2547:
--

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

https://github.com/apache/nifi/pull/850#discussion_r75044228
  
--- Diff: 
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/DeleteHDFS.java
 ---
@@ -0,0 +1,161 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.hadoop;
+
+import java.io.IOException;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+
+import org.apache.hadoop.fs.FileStatus;
+import org.apache.hadoop.fs.FileSystem;
+import org.apache.hadoop.fs.Path;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.TriggerWhenEmpty;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import com.google.common.collect.Lists;
+import com.google.common.collect.Maps;
+
+@TriggerWhenEmpty
+@InputRequirement(InputRequirement.Requirement.INPUT_ALLOWED)
+@Tags({ "hadoop", "HDFS", "delete", "remove", "filesystem" })
+@CapabilityDescription("Deletes a file from HDFS. The file can be provided 
as an attribute from an incoming FlowFile, "
++ "or a statically set file that is periodically removed. If this 
processor has an incoming connection, it"
++ "will ignore running on a periodic basis and instead rely on 
incoming FlowFiles to trigger a delete. "
++ "Optionally, you may specify use a wildcard character to match 
multiple files or directories.")
+public class DeleteHDFS extends AbstractHadoopProcessor {
+public static final Relationship REL_SUCCESS = new 
Relationship.Builder()
+.name("success")
+.description("FlowFiles will be routed here if the delete 
command was successful")
+.build();
+
+public static final Relationship REL_FAILURE = new 
Relationship.Builder()
+.name("failure")
+.description("FlowFiles will be routed here if the delete 
command was unsuccessful")
+.build();
+
+public static final PropertyDescriptor FILE_OR_DIRECTORY = new 
PropertyDescriptor.Builder()
+.name("File or Directory")
+.description("The HDFS file or directory to delete. A wildcard 
expression may be used to only delete certain files")
+.required(true)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.expressionLanguageSupported(true)
+.build();
+
+public static final PropertyDescriptor RECURSIVE = new 
PropertyDescriptor.Builder()
+.name("Recursive")
+.description("Remove contents of a non-empty directory 
recursively")
+.allowableValues("true", "false")
+.required(true)
+.defaultValue("true")
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.build();
+
+private static final Set relationships;
+
+static {
+final Set relationshipSet = new HashSet<>();
+relationshipSet.add(REL_SUCCESS);
+relationshipSet.add(REL_FAILURE);
+relationships = Collections.unmodifiableSet(relationshipSet);
 

[GitHub] nifi pull request #850: NIFI-2547: Add DeleteHDFS Processor

[mattyb149]

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

https://github.com/apache/nifi/pull/850#discussion_r75044228
  
--- Diff: 
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/DeleteHDFS.java
 ---
@@ -0,0 +1,161 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.hadoop;
+
+import java.io.IOException;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+
+import org.apache.hadoop.fs.FileStatus;
+import org.apache.hadoop.fs.FileSystem;
+import org.apache.hadoop.fs.Path;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.TriggerWhenEmpty;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import com.google.common.collect.Lists;
+import com.google.common.collect.Maps;
+
+@TriggerWhenEmpty
+@InputRequirement(InputRequirement.Requirement.INPUT_ALLOWED)
+@Tags({ "hadoop", "HDFS", "delete", "remove", "filesystem" })
+@CapabilityDescription("Deletes a file from HDFS. The file can be provided 
as an attribute from an incoming FlowFile, "
++ "or a statically set file that is periodically removed. If this 
processor has an incoming connection, it"
++ "will ignore running on a periodic basis and instead rely on 
incoming FlowFiles to trigger a delete. "
++ "Optionally, you may specify use a wildcard character to match 
multiple files or directories.")
+public class DeleteHDFS extends AbstractHadoopProcessor {
+public static final Relationship REL_SUCCESS = new 
Relationship.Builder()
+.name("success")
+.description("FlowFiles will be routed here if the delete 
command was successful")
+.build();
+
+public static final Relationship REL_FAILURE = new 
Relationship.Builder()
+.name("failure")
+.description("FlowFiles will be routed here if the delete 
command was unsuccessful")
+.build();
+
+public static final PropertyDescriptor FILE_OR_DIRECTORY = new 
PropertyDescriptor.Builder()
+.name("File or Directory")
+.description("The HDFS file or directory to delete. A wildcard 
expression may be used to only delete certain files")
+.required(true)
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.expressionLanguageSupported(true)
+.build();
+
+public static final PropertyDescriptor RECURSIVE = new 
PropertyDescriptor.Builder()
+.name("Recursive")
+.description("Remove contents of a non-empty directory 
recursively")
+.allowableValues("true", "false")
+.required(true)
+.defaultValue("true")
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.build();
+
+private static final Set relationships;
+
+static {
+final Set relationshipSet = new HashSet<>();
+relationshipSet.add(REL_SUCCESS);
+relationshipSet.add(REL_FAILURE);
+relationships = Collections.unmodifiableSet(relationshipSet);
+}
+
+@Override
+protected List getSupportedPropertyDescriptors() {
+List props = new ArrayList<>(properties);
+props.add(FILE_OR_DIRECTORY);
+props.add(RECURSIVE);
+   

[GitHub] nifi pull request #850: NIFI-2547: Add DeleteHDFS Processor

[mattyb149]

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

https://github.com/apache/nifi/pull/850#discussion_r75044175
  
--- Diff: 
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/DeleteHDFS.java
 ---
@@ -0,0 +1,161 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.hadoop;
+
+import java.io.IOException;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+
+import org.apache.hadoop.fs.FileStatus;
+import org.apache.hadoop.fs.FileSystem;
+import org.apache.hadoop.fs.Path;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.TriggerWhenEmpty;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import com.google.common.collect.Lists;
+import com.google.common.collect.Maps;
+
+@TriggerWhenEmpty
+@InputRequirement(InputRequirement.Requirement.INPUT_ALLOWED)
+@Tags({ "hadoop", "HDFS", "delete", "remove", "filesystem" })
+@CapabilityDescription("Deletes a file from HDFS. The file can be provided 
as an attribute from an incoming FlowFile, "
++ "or a statically set file that is periodically removed. If this 
processor has an incoming connection, it"
++ "will ignore running on a periodic basis and instead rely on 
incoming FlowFiles to trigger a delete. "
++ "Optionally, you may specify use a wildcard character to match 
multiple files or directories.")
+public class DeleteHDFS extends AbstractHadoopProcessor {
+public static final Relationship REL_SUCCESS = new 
Relationship.Builder()
+.name("success")
+.description("FlowFiles will be routed here if the delete 
command was successful")
+.build();
+
+public static final Relationship REL_FAILURE = new 
Relationship.Builder()
+.name("failure")
+.description("FlowFiles will be routed here if the delete 
command was unsuccessful")
+.build();
+
+public static final PropertyDescriptor FILE_OR_DIRECTORY = new 
PropertyDescriptor.Builder()
+.name("File or Directory")
--- End diff --

Not a requirement, but lately it's been suggested to use displayName() in 
the PropertyDescriptor.Builder() for the "friendly" name, and name() as 
something more machine friendly, as we move towards internationalization.


---
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-2547) Add DeleteHDFS Processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2547:
--

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

https://github.com/apache/nifi/pull/850#discussion_r75044175
  
--- Diff: 
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/DeleteHDFS.java
 ---
@@ -0,0 +1,161 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.hadoop;
+
+import java.io.IOException;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+
+import org.apache.hadoop.fs.FileStatus;
+import org.apache.hadoop.fs.FileSystem;
+import org.apache.hadoop.fs.Path;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.TriggerWhenEmpty;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import com.google.common.collect.Lists;
+import com.google.common.collect.Maps;
+
+@TriggerWhenEmpty
+@InputRequirement(InputRequirement.Requirement.INPUT_ALLOWED)
+@Tags({ "hadoop", "HDFS", "delete", "remove", "filesystem" })
+@CapabilityDescription("Deletes a file from HDFS. The file can be provided 
as an attribute from an incoming FlowFile, "
++ "or a statically set file that is periodically removed. If this 
processor has an incoming connection, it"
++ "will ignore running on a periodic basis and instead rely on 
incoming FlowFiles to trigger a delete. "
++ "Optionally, you may specify use a wildcard character to match 
multiple files or directories.")
+public class DeleteHDFS extends AbstractHadoopProcessor {
+public static final Relationship REL_SUCCESS = new 
Relationship.Builder()
+.name("success")
+.description("FlowFiles will be routed here if the delete 
command was successful")
+.build();
+
+public static final Relationship REL_FAILURE = new 
Relationship.Builder()
+.name("failure")
+.description("FlowFiles will be routed here if the delete 
command was unsuccessful")
+.build();
+
+public static final PropertyDescriptor FILE_OR_DIRECTORY = new 
PropertyDescriptor.Builder()
+.name("File or Directory")
--- End diff --

Not a requirement, but lately it's been suggested to use displayName() in 
the PropertyDescriptor.Builder() for the "friendly" name, and name() as 
something more machine friendly, as we move towards internationalization.


> Add DeleteHDFS Processor 
> -
>
> Key: NIFI-2547
> URL: https://issues.apache.org/jira/browse/NIFI-2547
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Ricky Saltzer
>Assignee: Ricky Saltzer
>
> There are times where a user may want to remove a file or directory from 
> HDFS. The reasons for this vary, but to provide some context, I currently 
> have a pipeline where I need to periodically delete files that my NiFi 
> pipeline is producing. In my case, it's a "Delete files after they are 7 days 
> old". 
> Currently, I have to use the {{ExecuteStreamCommand}} processor and manually 
> call {{hdfs dfs -rm}}, which is awful when dealing with a large amount of 
> files. For one, an entire JVM 

[jira] [Commented] (NIFI-2574) Update NiFiProperties usage to a context based accessor rather than static singleton

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2574:
---

MonitorDiskUsage is simplified to be about monitoring the specified directory 
and threshold.  This needs to be documented in the migration guide as people 
using the old one will need to configure a monitor for each paritition they 
wish to watch.

> Update NiFiProperties usage to a context based accessor rather than static 
> singleton
> 
>
> Key: NIFI-2574
> URL: https://issues.apache.org/jira/browse/NIFI-2574
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Configuration, Core Framework
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>  Labels: migration
> Fix For: 1.0.0
>
>
> This is a key step to move our longstanding odd static singleton usage of 
> NiFiProperties which enables a loader to exist which will encapsulate all 
> logic for dealing with encrypted properties as is the goal of the parent task.



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

[jira] [Updated] (NIFI-2574) Update NiFiProperties usage to a context based accessor rather than static singleton

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2574:
--
Labels: migration  (was: )

> Update NiFiProperties usage to a context based accessor rather than static 
> singleton
> 
>
> Key: NIFI-2574
> URL: https://issues.apache.org/jira/browse/NIFI-2574
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Configuration, Core Framework
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>  Labels: migration
> Fix For: 1.0.0
>
>
> This is a key step to move our longstanding odd static singleton usage of 
> NiFiProperties which enables a loader to exist which will encapsulate all 
> logic for dealing with encrypted properties as is the goal of the parent task.



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

[jira] [Commented] (NIFI-2574) Update NiFiProperties usage to a context based accessor rather than static singleton

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2574:
---

Almost done removing all use of NiFiProperties.getInstance().  Fortunately 
found that between processors, controller services, and reporting tasks only 
two used NiFiProperties.  One was invalid usage and should be replaced with 
properties (MonitorDiskUsage) and the other(s) were using Kerberos Service 
Principal accessors.  For the former just fixing to be properties as it should. 
 For the latter introduced a KerberosContext which is on the 
ProcessorInitializationContext, ReportingTaskInitializationContext, and the 
ControllerServiceInitializationContext.

> Update NiFiProperties usage to a context based accessor rather than static 
> singleton
> 
>
> Key: NIFI-2574
> URL: https://issues.apache.org/jira/browse/NIFI-2574
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Configuration, Core Framework
>Reporter: Joseph Witt
>Assignee: Joseph Witt
> Fix For: 1.0.0
>
>
> This is a key step to move our longstanding odd static singleton usage of 
> NiFiProperties which enables a loader to exist which will encapsulate all 
> logic for dealing with encrypted properties as is the goal of the parent task.



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

[jira] [Created] (NIFI-2584) PutSQL Timestamp Format Issue

[Peter Wicks (JIRA)]

Peter Wicks created NIFI-2584:
-

 Summary: PutSQL Timestamp Format Issue
 Key: NIFI-2584
 URL: https://issues.apache.org/jira/browse/NIFI-2584
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core Framework
Reporter: Peter Wicks


In NIFI-2576 I mistakenly put 'hh' into my timestamp format rather than 'HH', 
so it was running on 12-hour formatting without an am/pm qualifier.  The 
correct format is 'HH'.



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

[GitHub] nifi pull request #875: Nifi 2477

[trixpan]

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

https://github.com/apache/nifi/pull/875#discussion_r75027919
  
--- Diff: nifi-docs/src/main/asciidoc/administration-guide.adoc ---
@@ -169,6 +169,81 @@ Now that the User Interface has been secured, we can 
easily secure Site-to-Site
 accomplished by setting the `nifi.remote.input.secure` and 
`nifi.cluster.protocol.is.secure` properties, respectively, to `true`.
 
 
+TLS Generation Toolkit
+~~
+
+In order to facilitate the secure setup of NiFi, a tls-toolkit command 
line utility is available to automatically generate the required keystores, 
truststore, and relevant configuration files. This is especially useful for 
securing multiple NiFi nodes, which can be a tedious and error-prone process.
+
+The tls-toolkit has two primary modes of operation:
+
+1. Standalone -- generates the certificate authority, keystores, 
truststores, and nifi.properties files in one command.
+2. Client/Server mode -- uses a Certificate Authority Server that accepts 
Certificate Signing Requests from clients, signs them, and sends the resulting 
certificates back.  Both client and server validate the other’s identity 
through a shared secret.
+
+Standalone
+^^
+Standalone mode can be invoked by running “tls-toolkit.sh standalone 
-h” which will print the usage information along with descriptions of options 
that can be specified.
+
+The most common options to specify are:
+
+* -n (or --hostnames) a comma-separated list of hostnames that you’d 
like to generate certificates for.  It can be specified multiple times.  Range 
and instance patterns are supported. (see below for details)
+* -f (or --nifiPropertiesFile) a base nifi.properties file that the tool 
will update for each host
+* -o (or --outputDirectory) the directory to use for the resulting 
Certificate Authority files and NiFi configurations.  A subdirectory will be 
made for each host.
+
+Hostname Patterns:
+
+* Square brackets can be used in order to easily specify a range of 
hostnames. Example: [01-20]
+* Parentheses can be used in order to specify that more than one NiFi 
instance will run on the given host(s). Example: (5)
+
+Examples:
--- End diff --

+1 on @bbende comment


---
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-2582) QueryDatabaseTable should support splitting the ResultSet into multiple flow files

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2582:
--

GitHub user patricker opened a pull request:

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

QueryDatabaseTable updates

NIFI-2582 - QueryDatabaseTable should support splitting the ResultSet into 
multiple flow files
NIFI-2583 - QueryDatabaseTable should allow you to specify an initial Max 
Value

Appropriate Unit Tests have also been developed.

FYI: I tried to following the branching guidelines... we'll see how that 
goes.

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

$ git pull https://github.com/patricker/nifi QDB1

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

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


commit 92eb864c96dc3096c28f6d3a2e13402d7bc0a292
Author: Peter Wicks 
Date:   2016-08-15T16:49:37Z

NIFI-2356

commit b28806b52f0a7c7d35e2713db0495c9af6a55641
Author: Peter Wicks 
Date:   2016-08-15T17:47:46Z

Sync

commit ab0568341c5639998f1a292311a58069ead21e7a
Author: Peter Wicks 
Date:   2016-08-15T21:50:47Z

NIFI-2576

commit 1c7ea31346ce1dbd80b2fd392be1d2f4dfccbabe
Author: Peter Wicks 
Date:   2016-08-15T21:52:45Z

Merge remote-tracking branch 'upstream/master'

commit 4ce80fa69ac8524756818dd6d530954985b430c5
Author: Peter Wicks 
Date:   2016-08-15T22:00:31Z

NIFI-2576

commit c680ff7f17cf67a778e5afd31f7283f5ea7f8a73
Author: Peter Wicks 
Date:   2016-08-16T03:03:30Z

NIFI-2576

commit 69fd3df515803d87213fd5f8d1f6d1ebde42e088
Author: Peter Wicks 
Date:   2016-08-16T15:08:33Z

QDB1

commit 4b87f56dfd136b25c3c7b14f8f6f0023b8740e7a
Author: Peter Wicks 
Date:   2016-08-16T21:16:57Z

QDB1

commit aa59b954784f4a26526b87c10034bb0eb2397d9a
Author: Peter Wicks 
Date:   2016-08-16T21:36:00Z

QDB1

commit 7b4bf15cde8327ae086320c8b6a2be3be40499c3
Author: Peter Wicks 
Date:   2016-08-16T21:42:01Z

QDB1




> QueryDatabaseTable should support splitting the ResultSet into multiple flow 
> files
> --
>
> Key: NIFI-2582
> URL: https://issues.apache.org/jira/browse/NIFI-2582
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Peter Wicks
>
> A new Property, that defaults to disabled, should allow for ResultSets to be 
> split up into multiple output flow files.



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

[GitHub] nifi pull request #876: QueryDatabaseTable updates

[patricker]

GitHub user patricker opened a pull request:

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

QueryDatabaseTable updates

NIFI-2582 - QueryDatabaseTable should support splitting the ResultSet into 
multiple flow files
NIFI-2583 - QueryDatabaseTable should allow you to specify an initial Max 
Value

Appropriate Unit Tests have also been developed.

FYI: I tried to following the branching guidelines... we'll see how that 
goes.

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

$ git pull https://github.com/patricker/nifi QDB1

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

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


commit 92eb864c96dc3096c28f6d3a2e13402d7bc0a292
Author: Peter Wicks 
Date:   2016-08-15T16:49:37Z

NIFI-2356

commit b28806b52f0a7c7d35e2713db0495c9af6a55641
Author: Peter Wicks 
Date:   2016-08-15T17:47:46Z

Sync

commit ab0568341c5639998f1a292311a58069ead21e7a
Author: Peter Wicks 
Date:   2016-08-15T21:50:47Z

NIFI-2576

commit 1c7ea31346ce1dbd80b2fd392be1d2f4dfccbabe
Author: Peter Wicks 
Date:   2016-08-15T21:52:45Z

Merge remote-tracking branch 'upstream/master'

commit 4ce80fa69ac8524756818dd6d530954985b430c5
Author: Peter Wicks 
Date:   2016-08-15T22:00:31Z

NIFI-2576

commit c680ff7f17cf67a778e5afd31f7283f5ea7f8a73
Author: Peter Wicks 
Date:   2016-08-16T03:03:30Z

NIFI-2576

commit 69fd3df515803d87213fd5f8d1f6d1ebde42e088
Author: Peter Wicks 
Date:   2016-08-16T15:08:33Z

QDB1

commit 4b87f56dfd136b25c3c7b14f8f6f0023b8740e7a
Author: Peter Wicks 
Date:   2016-08-16T21:16:57Z

QDB1

commit aa59b954784f4a26526b87c10034bb0eb2397d9a
Author: Peter Wicks 
Date:   2016-08-16T21:36:00Z

QDB1

commit 7b4bf15cde8327ae086320c8b6a2be3be40499c3
Author: Peter Wicks 
Date:   2016-08-16T21:42:01Z

QDB1




---
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-2583) QueryDatabaseTable should allow you to specify an initial Max Value

[Peter Wicks (JIRA)]

Peter Wicks created NIFI-2583:
-

 Summary: QueryDatabaseTable should allow you to specify an initial 
Max Value
 Key: NIFI-2583
 URL: https://issues.apache.org/jira/browse/NIFI-2583
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Peter Wicks


QueryDatabaseTable should allow you to specify an initial Max Value for max 
value columns. This value would be read from custom properties, added by users, 
one for each max value column that they want to provide a max value for.

If a value for a column already exists in the State then this initial value is 
ignored.  Clearing the state will cause the initial value to be read again.

This will provide a method by which an operations person could stop a job,  
clear state, move the initial value for a column to an appropriate value, then 
start the job again. Thus re-ingesting all data from a certain value forward 
again.



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

[jira] [Created] (NIFI-2582) QueryDatabaseTable should support splitting the ResultSet into multiple flow files

[Peter Wicks (JIRA)]

Peter Wicks created NIFI-2582:
-

 Summary: QueryDatabaseTable should support splitting the ResultSet 
into multiple flow files
 Key: NIFI-2582
 URL: https://issues.apache.org/jira/browse/NIFI-2582
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core Framework
Affects Versions: 1.0.0
Reporter: Peter Wicks


A new Property, that defaults to disabled, should allow for ResultSets to be 
split up into multiple output flow files.



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

[GitHub] nifi pull request #875: Nifi 2477

[bbende]

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

https://github.com/apache/nifi/pull/875#discussion_r75010710
  
--- Diff: nifi-docs/src/main/asciidoc/administration-guide.adoc ---
@@ -169,6 +169,81 @@ Now that the User Interface has been secured, we can 
easily secure Site-to-Site
 accomplished by setting the `nifi.remote.input.secure` and 
`nifi.cluster.protocol.is.secure` properties, respectively, to `true`.
 
 
+TLS Generation Toolkit
+~~
+
+In order to facilitate the secure setup of NiFi, a tls-toolkit command 
line utility is available to automatically generate the required keystores, 
truststore, and relevant configuration files. This is especially useful for 
securing multiple NiFi nodes, which can be a tedious and error-prone process.
+
+The tls-toolkit has two primary modes of operation:
+
+1. Standalone -- generates the certificate authority, keystores, 
truststores, and nifi.properties files in one command.
+2. Client/Server mode -- uses a Certificate Authority Server that accepts 
Certificate Signing Requests from clients, signs them, and sends the resulting 
certificates back.  Both client and server validate the other’s identity 
through a shared secret.
+
+Standalone
+^^
+Standalone mode can be invoked by running “tls-toolkit.sh standalone 
-h” which will print the usage information along with descriptions of options 
that can be specified.
+
+The most common options to specify are:
+
+* -n (or --hostnames) a comma-separated list of hostnames that you’d 
like to generate certificates for.  It can be specified multiple times.  Range 
and instance patterns are supported. (see below for details)
+* -f (or --nifiPropertiesFile) a base nifi.properties file that the tool 
will update for each host
+* -o (or --outputDirectory) the directory to use for the resulting 
Certificate Authority files and NiFi configurations.  A subdirectory will be 
made for each host.
+
+Hostname Patterns:
+
+* Square brackets can be used in order to easily specify a range of 
hostnames. Example: [01-20]
+* Parentheses can be used in order to specify that more than one NiFi 
instance will run on the given host(s). Example: (5)
+
+Examples:
--- End diff --

Should we show one example generating a client p12? I think that will be 
very common.


---
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-2534) Error when stopping a process group the user doesn't have any permission for

[Bryan Bende (JIRA)]

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

Bryan Bende resolved NIFI-2534.
---
Resolution: Fixed

> Error when stopping a process group the user doesn't have any permission for
> 
>
> Key: NIFI-2534
> URL: https://issues.apache.org/jira/browse/NIFI-2534
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Bryan Bende
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> I created a process group in a secure instance, then overrode the policy for 
> "view component" such that no user had view component for the group (left the 
> modify component inheriting from parent). Then right-clicked the process 
> group and chose stop, and the circle in the header stayed spinning.
> In Chrome Dev tools the error showed on line 1090 of nf-process-group.js 
> if (processGroupMap.has(processGroup.id)) {
> Saying "id" is undefined.



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

[jira] [Commented] (NIFI-2534) Error when stopping a process group the user doesn't have any permission for

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2534:
--

Github user asfgit closed the pull request at:

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


> Error when stopping a process group the user doesn't have any permission for
> 
>
> Key: NIFI-2534
> URL: https://issues.apache.org/jira/browse/NIFI-2534
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Bryan Bende
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> I created a process group in a secure instance, then overrode the policy for 
> "view component" such that no user had view component for the group (left the 
> modify component inheriting from parent). Then right-clicked the process 
> group and chose stop, and the circle in the header stayed spinning.
> In Chrome Dev tools the error showed on line 1090 of nf-process-group.js 
> if (processGroupMap.has(processGroup.id)) {
> Saying "id" is undefined.



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

[jira] [Commented] (NIFI-2534) Error when stopping a process group the user doesn't have any permission for

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2534: - Refreshing using component IDs. - Code clean up.

This closes #874.

Signed-off-by: Bryan Bende 


> Error when stopping a process group the user doesn't have any permission for
> 
>
> Key: NIFI-2534
> URL: https://issues.apache.org/jira/browse/NIFI-2534
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Bryan Bende
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> I created a process group in a secure instance, then overrode the policy for 
> "view component" such that no user had view component for the group (left the 
> modify component inheriting from parent). Then right-clicked the process 
> group and chose stop, and the circle in the header stayed spinning.
> In Chrome Dev tools the error showed on line 1090 of nf-process-group.js 
> if (processGroupMap.has(processGroup.id)) {
> Saying "id" is undefined.



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

[GitHub] nifi pull request #874: Addressing issue when refresh Process Groups the use...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] nifi issue #874: Addressing issue when refresh Process Groups the user does ...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/874
  
Looks good, will merge to master


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

[jira] [Commented] (NIFI-2477) Document tls-toolkit

[Bryan Rosander (JIRA)]

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

Bryan Rosander commented on NIFI-2477:
--

[~andrewmlim] I opened a second pull request with your commit as well as an 
update that reflects the functional changes from NIFI-2476.

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

> Document tls-toolkit
> 
>
> Key: NIFI-2477
> URL: https://issues.apache.org/jira/browse/NIFI-2477
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Bryan Rosander
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> tls-toolkit created as part of NIFI-2193 needs to be documented in order to 
> be a useful utility to ease the burden of configuring tls for one or more 
> NiFi instances.



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

[jira] [Comment Edited] (NIFI-2477) Document tls-toolkit

[Bryan Rosander (JIRA)]

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

Bryan Rosander edited comment on NIFI-2477 at 8/16/16 7:44 PM:
---

Hey [~andrewmlim], I opened a second pull request with your commit as well as 
an update that reflects the functional changes from NIFI-2476.

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


was (Author: bryanrosan...@gmail.com):
[~andrewmlim] I opened a second pull request with your commit as well as an 
update that reflects the functional changes from NIFI-2476.

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

> Document tls-toolkit
> 
>
> Key: NIFI-2477
> URL: https://issues.apache.org/jira/browse/NIFI-2477
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Bryan Rosander
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> tls-toolkit created as part of NIFI-2193 needs to be documented in order to 
> be a useful utility to ease the burden of configuring tls for one or more 
> NiFi instances.



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

[jira] [Commented] (NIFI-2534) Error when stopping a process group the user doesn't have any permission for

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2534:
--

GitHub user mcgilman opened a pull request:

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

Addressing issue when refresh Process Groups the user does not have READ 
access to

NIFI-2534:
- Refreshing using component IDs.
- Code clean up.

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

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

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

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


commit 2b17318de2526c4bab82d525346213ee2b8f191d
Author: Matt Gilman 
Date:   2016-08-16T19:29:29Z

NIFI-2534:
- Refreshing using component IDs.
- Code clean up.




> Error when stopping a process group the user doesn't have any permission for
> 
>
> Key: NIFI-2534
> URL: https://issues.apache.org/jira/browse/NIFI-2534
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Bryan Bende
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> I created a process group in a secure instance, then overrode the policy for 
> "view component" such that no user had view component for the group (left the 
> modify component inheriting from parent). Then right-clicked the process 
> group and chose stop, and the circle in the header stayed spinning.
> In Chrome Dev tools the error showed on line 1090 of nf-process-group.js 
> if (processGroupMap.has(processGroup.id)) {
> Saying "id" is undefined.



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

[GitHub] nifi issue #874: Addressing issue when refresh Process Groups the user does ...

[bbende]

Github user bbende commented on the issue:

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


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

[jira] [Commented] (NIFI-2477) Document tls-toolkit

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2477:
--

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/849
  
superseded by #875


> Document tls-toolkit
> 
>
> Key: NIFI-2477
> URL: https://issues.apache.org/jira/browse/NIFI-2477
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Bryan Rosander
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> tls-toolkit created as part of NIFI-2193 needs to be documented in order to 
> be a useful utility to ease the burden of configuring tls for one or more 
> NiFi instances.



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

[GitHub] nifi issue #875: Nifi 2477

[brosander]

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/875
  
supersedes #849


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

[GitHub] nifi issue #849: NIFI-2477 Document TLS generation tool in Admin and Develop...

[brosander]

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/849
  
superseded by #875


---
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 #875: Nifi 2477

[brosander]

GitHub user brosander opened a pull request:

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

Nifi 2477



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

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

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

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


commit 8c72a5a208d418ba35c26b31b430315c517d3c32
Author: Andrew Lim 
Date:   2016-08-12T18:44:38Z

NIFI-2477 Document TLS generation tool in Admin and Developer Guides

commit 5e8b3ac9e5ad00ff96489de212da38a596cf3546
Author: Bryan Rosander 
Date:   2016-08-16T18:48:35Z

NIFI-2477 - Updating admin guide to account for NIFI-2476




---
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 #874: Addressing issue when refresh Process Groups the use...

[mcgilman]

GitHub user mcgilman opened a pull request:

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

Addressing issue when refresh Process Groups the user does not have READ 
access to

NIFI-2534:
- Refreshing using component IDs.
- Code clean up.

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

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

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

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


commit 2b17318de2526c4bab82d525346213ee2b8f191d
Author: Matt Gilman 
Date:   2016-08-16T19:29:29Z

NIFI-2534:
- Refreshing using component IDs.
- Code clean up.




---
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-2569) Allow multiple NiFi instances on same host, make range generation easier

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2569:
--

Github user asfgit closed the pull request at:

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


> Allow multiple NiFi instances on same host, make range generation easier
> 
>
> Key: NIFI-2569
> URL: https://issues.apache.org/jira/browse/NIFI-2569
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
> Fix For: 1.0.0
>
>
> In the standalone tool:
> * In order to facilitate local secure clustering, we should be able to 
> generate multiple certificates for the same hostname.
> * We should also be able to update ports in nifi.properties to increment in 
> that scenario.
> * The keystore entries in nifi.properties should start with ./conf/ so that 
> the files in each host folder can just be copied to a NiFi instance.
> * Specifying a range of hosts should be easier.
> To that end, I've added range expansion.  [] denote a range to include in the 
> hostname, () denote instance numbers for that hostname.
> This can be used as follows:
> nifi[01-3].domain expands to nifi01.domain, nifi02.domain, nifi03.domain
> nifi(2) will create 2 instances of nifi with corresponding certificates and 
> nifi.properties with incremented port numbers.
> These can be combined to something like:
> nifi[1-10].subdomain[1-4].domain(2) for 2 instances of nifi running on each 
> host in the expanded set of ranges
> If you need distinct ports for all nifi instances (not just those with the 
> same hostname), that can be achieved by specifying a global order with -G.
> ex: bin/tls-toolkit.sh standalone -n nifi[3-5].domain -G nifi[1-100].domain
> This would generate nifi3.domain, nifi4.domain, nifi5.domain and allot them 
> distinct ports derteministically mapped from the range of nifi[1-100].domain 
> so that later updates specifying the same global order won't have conflicting 
> port assignments.



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

[jira] [Commented] (NIFI-2569) Allow multiple NiFi instances on same host, make range generation easier

[ASF subversion and git services (JIRA)]

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

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

Commit 2fd39676a887151aa4124a824fc0cd756b9fac3b in nifi's branch 
refs/heads/master from [~bryanrosan...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2fd3967 ]

NIFI-2569 - Multiple instances on same host, range enhancements, 
nifi.properties incrementing ports NIFI-2569 - Updating main class in windows 
bat file

This closes #861.

Signed-off-by: Bryan Bende 


> Allow multiple NiFi instances on same host, make range generation easier
> 
>
> Key: NIFI-2569
> URL: https://issues.apache.org/jira/browse/NIFI-2569
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
> Fix For: 1.0.0
>
>
> In the standalone tool:
> * In order to facilitate local secure clustering, we should be able to 
> generate multiple certificates for the same hostname.
> * We should also be able to update ports in nifi.properties to increment in 
> that scenario.
> * The keystore entries in nifi.properties should start with ./conf/ so that 
> the files in each host folder can just be copied to a NiFi instance.
> * Specifying a range of hosts should be easier.
> To that end, I've added range expansion.  [] denote a range to include in the 
> hostname, () denote instance numbers for that hostname.
> This can be used as follows:
> nifi[01-3].domain expands to nifi01.domain, nifi02.domain, nifi03.domain
> nifi(2) will create 2 instances of nifi with corresponding certificates and 
> nifi.properties with incremented port numbers.
> These can be combined to something like:
> nifi[1-10].subdomain[1-4].domain(2) for 2 instances of nifi running on each 
> host in the expanded set of ranges
> If you need distinct ports for all nifi instances (not just those with the 
> same hostname), that can be achieved by specifying a global order with -G.
> ex: bin/tls-toolkit.sh standalone -n nifi[3-5].domain -G nifi[1-100].domain
> This would generate nifi3.domain, nifi4.domain, nifi5.domain and allot them 
> distinct ports derteministically mapped from the range of nifi[1-100].domain 
> so that later updates specifying the same global order won't have conflicting 
> port assignments.



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

[jira] [Commented] (NIFI-2569) Allow multiple NiFi instances on same host, make range generation easier

[ASF subversion and git services (JIRA)]

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

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

Commit 2fd39676a887151aa4124a824fc0cd756b9fac3b in nifi's branch 
refs/heads/master from [~bryanrosan...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2fd3967 ]

NIFI-2569 - Multiple instances on same host, range enhancements, 
nifi.properties incrementing ports NIFI-2569 - Updating main class in windows 
bat file

This closes #861.

Signed-off-by: Bryan Bende 


> Allow multiple NiFi instances on same host, make range generation easier
> 
>
> Key: NIFI-2569
> URL: https://issues.apache.org/jira/browse/NIFI-2569
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
> Fix For: 1.0.0
>
>
> In the standalone tool:
> * In order to facilitate local secure clustering, we should be able to 
> generate multiple certificates for the same hostname.
> * We should also be able to update ports in nifi.properties to increment in 
> that scenario.
> * The keystore entries in nifi.properties should start with ./conf/ so that 
> the files in each host folder can just be copied to a NiFi instance.
> * Specifying a range of hosts should be easier.
> To that end, I've added range expansion.  [] denote a range to include in the 
> hostname, () denote instance numbers for that hostname.
> This can be used as follows:
> nifi[01-3].domain expands to nifi01.domain, nifi02.domain, nifi03.domain
> nifi(2) will create 2 instances of nifi with corresponding certificates and 
> nifi.properties with incremented port numbers.
> These can be combined to something like:
> nifi[1-10].subdomain[1-4].domain(2) for 2 instances of nifi running on each 
> host in the expanded set of ranges
> If you need distinct ports for all nifi instances (not just those with the 
> same hostname), that can be achieved by specifying a global order with -G.
> ex: bin/tls-toolkit.sh standalone -n nifi[3-5].domain -G nifi[1-100].domain
> This would generate nifi3.domain, nifi4.domain, nifi5.domain and allot them 
> distinct ports derteministically mapped from the range of nifi[1-100].domain 
> so that later updates specifying the same global order won't have conflicting 
> port assignments.



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

[jira] [Updated] (NIFI-2569) Allow multiple NiFi instances on same host, make range generation easier

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-2569:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Allow multiple NiFi instances on same host, make range generation easier
> 
>
> Key: NIFI-2569
> URL: https://issues.apache.org/jira/browse/NIFI-2569
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
> Fix For: 1.0.0
>
>
> In the standalone tool:
> * In order to facilitate local secure clustering, we should be able to 
> generate multiple certificates for the same hostname.
> * We should also be able to update ports in nifi.properties to increment in 
> that scenario.
> * The keystore entries in nifi.properties should start with ./conf/ so that 
> the files in each host folder can just be copied to a NiFi instance.
> * Specifying a range of hosts should be easier.
> To that end, I've added range expansion.  [] denote a range to include in the 
> hostname, () denote instance numbers for that hostname.
> This can be used as follows:
> nifi[01-3].domain expands to nifi01.domain, nifi02.domain, nifi03.domain
> nifi(2) will create 2 instances of nifi with corresponding certificates and 
> nifi.properties with incremented port numbers.
> These can be combined to something like:
> nifi[1-10].subdomain[1-4].domain(2) for 2 instances of nifi running on each 
> host in the expanded set of ranges
> If you need distinct ports for all nifi instances (not just those with the 
> same hostname), that can be achieved by specifying a global order with -G.
> ex: bin/tls-toolkit.sh standalone -n nifi[3-5].domain -G nifi[1-100].domain
> This would generate nifi3.domain, nifi4.domain, nifi5.domain and allot them 
> distinct ports derteministically mapped from the range of nifi[1-100].domain 
> so that later updates specifying the same global order won't have conflicting 
> port assignments.



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

[GitHub] nifi pull request #861: NIFI-2569 - Multiple instances on same host, range e...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2569) Allow multiple NiFi instances on same host, make range generation easier

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2569:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/861
  
I was able to use the toolkit to generate all the configs for a two-node 
secure cluster and got into the UI using the generated p12. Everything looks 
good, will merge to master.


> Allow multiple NiFi instances on same host, make range generation easier
> 
>
> Key: NIFI-2569
> URL: https://issues.apache.org/jira/browse/NIFI-2569
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
> Fix For: 1.0.0
>
>
> In the standalone tool:
> * In order to facilitate local secure clustering, we should be able to 
> generate multiple certificates for the same hostname.
> * We should also be able to update ports in nifi.properties to increment in 
> that scenario.
> * The keystore entries in nifi.properties should start with ./conf/ so that 
> the files in each host folder can just be copied to a NiFi instance.
> * Specifying a range of hosts should be easier.
> To that end, I've added range expansion.  [] denote a range to include in the 
> hostname, () denote instance numbers for that hostname.
> This can be used as follows:
> nifi[01-3].domain expands to nifi01.domain, nifi02.domain, nifi03.domain
> nifi(2) will create 2 instances of nifi with corresponding certificates and 
> nifi.properties with incremented port numbers.
> These can be combined to something like:
> nifi[1-10].subdomain[1-4].domain(2) for 2 instances of nifi running on each 
> host in the expanded set of ranges
> If you need distinct ports for all nifi instances (not just those with the 
> same hostname), that can be achieved by specifying a global order with -G.
> ex: bin/tls-toolkit.sh standalone -n nifi[3-5].domain -G nifi[1-100].domain
> This would generate nifi3.domain, nifi4.domain, nifi5.domain and allot them 
> distinct ports derteministically mapped from the range of nifi[1-100].domain 
> so that later updates specifying the same global order won't have conflicting 
> port assignments.



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

[GitHub] nifi issue #861: NIFI-2569 - Multiple instances on same host, range enhancem...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/861
  
I was able to use the toolkit to generate all the configs for a two-node 
secure cluster and got into the UI using the generated p12. Everything looks 
good, will merge to master.


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

[jira] [Created] (NIFI-2581) Context menus and tooltips getting hidden after automatic refresh

[Jeff Storck (JIRA)]

Jeff Storck created NIFI-2581:
-

 Summary: Context menus and tooltips getting hidden after automatic 
refresh
 Key: NIFI-2581
 URL: https://issues.apache.org/jira/browse/NIFI-2581
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Affects Versions: 1.0.0
Reporter: Jeff Storck
Priority: Minor


When the NiFi UI's automatic refresh occurs, if there are context menus 
(right-click) or tooltips (for validation and bulletins) visible, they get 
hidden when the refresh completes.



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

[jira] [Created] (NIFI-2580) Improve EvaluateJSONPath docs

[Randy Gelhausen (JIRA)]

Randy Gelhausen created NIFI-2580:
-

 Summary: Improve EvaluateJSONPath docs
 Key: NIFI-2580
 URL: https://issues.apache.org/jira/browse/NIFI-2580
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Randy Gelhausen


{"http.request.uri":"/","http.context.identifier":"2fd145e5-1a7f-40d9-a187-5e5eb2734d0e","http.query.string":"a=1"}

To extract JSON fields with '.'s in the key, you must use a particular escape 
sequence: $.['http.param.a']

The EvaluateJSONPath docs could use a blurb with this information.



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

[jira] [Reopened] (NIFI-2534) Error when stopping a process group the user doesn't have any permission for

[Matt Gilman (JIRA)]

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

Matt Gilman reopened NIFI-2534:
---
  Assignee: Matt Gilman  (was: Scott Aslan)

Reopening to update solution to better handle reload requests of components 
which the current user does not have READ access to.

> Error when stopping a process group the user doesn't have any permission for
> 
>
> Key: NIFI-2534
> URL: https://issues.apache.org/jira/browse/NIFI-2534
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Bryan Bende
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> I created a process group in a secure instance, then overrode the policy for 
> "view component" such that no user had view component for the group (left the 
> modify component inheriting from parent). Then right-clicked the process 
> group and chose stop, and the circle in the header stayed spinning.
> In Chrome Dev tools the error showed on line 1090 of nf-process-group.js 
> if (processGroupMap.has(processGroup.id)) {
> Saying "id" is undefined.



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

[jira] [Commented] (NIFI-2574) Update NiFiProperties usage to a context based accessor rather than static singleton

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2574:
--

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

https://github.com/apache/nifi/pull/872#discussion_r74981298
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/src/test/groovy/org/apache/nifi/web/security/x509/ocsp/OcspCertificateValidatorGroovyTest.groovy
 ---
@@ -65,7 +65,8 @@ public class OcspCertificateValidatorGroovyTest {
 
 @Before
 public void setUp() throws Exception {
-mockProperties = [getProperty: { String propertyName -> return 
"value_for_${propertyName}" }] as NiFiProperties
+mockProperties = [getProperty: { String propertyName -> return 
"value_for_${propertyName}"
+,getPropertyKeys: { -> return ["A", "set"] as Set}] as 
NiFiProperties
--- End diff --

Actually I'm getting weird errors, doesn't look like map coercion likes the 
getProperty method, possibly because that method is used all over Groovy 
meta-classes and such. This could replace the above:

mockProperties = new NiFiProperties() {
@Override
String getProperty(String key) {
return 'value_for_' + key
}

@Override
Set getPropertyKeys() {
return ["A", "set"]
}
}


> Update NiFiProperties usage to a context based accessor rather than static 
> singleton
> 
>
> Key: NIFI-2574
> URL: https://issues.apache.org/jira/browse/NIFI-2574
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Configuration, Core Framework
>Reporter: Joseph Witt
>Assignee: Joseph Witt
> Fix For: 1.0.0
>
>
> This is a key step to move our longstanding odd static singleton usage of 
> NiFiProperties which enables a loader to exist which will encapsulate all 
> logic for dealing with encrypted properties as is the goal of the parent task.



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

[GitHub] nifi pull request #872: NIFI-2574 checkpoint commit to allow 1831 progress

[mattyb149]

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

https://github.com/apache/nifi/pull/872#discussion_r74981298
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/src/test/groovy/org/apache/nifi/web/security/x509/ocsp/OcspCertificateValidatorGroovyTest.groovy
 ---
@@ -65,7 +65,8 @@ public class OcspCertificateValidatorGroovyTest {
 
 @Before
 public void setUp() throws Exception {
-mockProperties = [getProperty: { String propertyName -> return 
"value_for_${propertyName}" }] as NiFiProperties
+mockProperties = [getProperty: { String propertyName -> return 
"value_for_${propertyName}"
+,getPropertyKeys: { -> return ["A", "set"] as Set}] as 
NiFiProperties
--- End diff --

Actually I'm getting weird errors, doesn't look like map coercion likes the 
getProperty method, possibly because that method is used all over Groovy 
meta-classes and such. This could replace the above:

mockProperties = new NiFiProperties() {
@Override
String getProperty(String key) {
return 'value_for_' + key
}

@Override
Set getPropertyKeys() {
return ["A", "set"]
}
}


---
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-2569) Allow multiple NiFi instances on same host, make range generation easier

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2569:
--

Github user bbende commented on the issue:

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


> Allow multiple NiFi instances on same host, make range generation easier
> 
>
> Key: NIFI-2569
> URL: https://issues.apache.org/jira/browse/NIFI-2569
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
> Fix For: 1.0.0
>
>
> In the standalone tool:
> * In order to facilitate local secure clustering, we should be able to 
> generate multiple certificates for the same hostname.
> * We should also be able to update ports in nifi.properties to increment in 
> that scenario.
> * The keystore entries in nifi.properties should start with ./conf/ so that 
> the files in each host folder can just be copied to a NiFi instance.
> * Specifying a range of hosts should be easier.
> To that end, I've added range expansion.  [] denote a range to include in the 
> hostname, () denote instance numbers for that hostname.
> This can be used as follows:
> nifi[01-3].domain expands to nifi01.domain, nifi02.domain, nifi03.domain
> nifi(2) will create 2 instances of nifi with corresponding certificates and 
> nifi.properties with incremented port numbers.
> These can be combined to something like:
> nifi[1-10].subdomain[1-4].domain(2) for 2 instances of nifi running on each 
> host in the expanded set of ranges
> If you need distinct ports for all nifi instances (not just those with the 
> same hostname), that can be achieved by specifying a global order with -G.
> ex: bin/tls-toolkit.sh standalone -n nifi[3-5].domain -G nifi[1-100].domain
> This would generate nifi3.domain, nifi4.domain, nifi5.domain and allot them 
> distinct ports derteministically mapped from the range of nifi[1-100].domain 
> so that later updates specifying the same global order won't have conflicting 
> port assignments.



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

[GitHub] nifi issue #861: NIFI-2569 - Multiple instances on same host, range enhancem...

[bbende]

Github user bbende commented on the issue:

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


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

[jira] [Commented] (NIFI-2574) Update NiFiProperties usage to a context based accessor rather than static singleton

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2574:
--

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

https://github.com/apache/nifi/pull/872#discussion_r74976276
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/src/test/groovy/org/apache/nifi/web/security/x509/ocsp/OcspCertificateValidatorGroovyTest.groovy
 ---
@@ -65,7 +65,8 @@ public class OcspCertificateValidatorGroovyTest {
 
 @Before
 public void setUp() throws Exception {
-mockProperties = [getProperty: { String propertyName -> return 
"value_for_${propertyName}" }] as NiFiProperties
+mockProperties = [getProperty: { String propertyName -> return 
"value_for_${propertyName}"
+,getPropertyKeys: { -> return ["A", "set"] as Set}] as 
NiFiProperties
--- End diff --

Just needs a brace at the end of line 68


> Update NiFiProperties usage to a context based accessor rather than static 
> singleton
> 
>
> Key: NIFI-2574
> URL: https://issues.apache.org/jira/browse/NIFI-2574
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Configuration, Core Framework
>Reporter: Joseph Witt
>Assignee: Joseph Witt
> Fix For: 1.0.0
>
>
> This is a key step to move our longstanding odd static singleton usage of 
> NiFiProperties which enables a loader to exist which will encapsulate all 
> logic for dealing with encrypted properties as is the goal of the parent task.



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

[GitHub] nifi pull request #872: NIFI-2574 checkpoint commit to allow 1831 progress

[mattyb149]

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

https://github.com/apache/nifi/pull/872#discussion_r74976276
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/src/test/groovy/org/apache/nifi/web/security/x509/ocsp/OcspCertificateValidatorGroovyTest.groovy
 ---
@@ -65,7 +65,8 @@ public class OcspCertificateValidatorGroovyTest {
 
 @Before
 public void setUp() throws Exception {
-mockProperties = [getProperty: { String propertyName -> return 
"value_for_${propertyName}" }] as NiFiProperties
+mockProperties = [getProperty: { String propertyName -> return 
"value_for_${propertyName}"
+,getPropertyKeys: { -> return ["A", "set"] as Set}] as 
NiFiProperties
--- End diff --

Just needs a brace at the end of line 68


---
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-2465) InferAvroSchema not evaluating EL against incoming FlowFile

[Bryan Bende (JIRA)]

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

Bryan Bende resolved NIFI-2465.
---
Resolution: Fixed

> InferAvroSchema not evaluating EL against incoming FlowFile
> ---
>
> Key: NIFI-2465
> URL: https://issues.apache.org/jira/browse/NIFI-2465
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.5.0, 0.5.1, 0.7.0, 0.6.1
>Reporter: Bryan Bende
>Assignee: Simon Elliston Ball
>Priority: Minor
> Fix For: 1.0.0
>
>
> Many of the properties in InferAvroSchema support expression language, but 
> don't evaluate it against an incoming flow file. 
> Some examples:
> {code}
> context.getProperty(RECORD_NAME).evaluateAttributeExpressions().getValue()
> context.getProperty(HEADER_LINE_SKIP_COUNT).evaluateAttributeExpressions().asInteger()
> context.getProperty(ESCAPE_STRING).evaluateAttributeExpressions().getValue()  
>
> context.getProperty(QUOTE_STRING).evaluateAttributeExpressions().getValue()
> {code}
> These should all use the incoming flow file.



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

[jira] [Commented] (NIFI-2465) InferAvroSchema not evaluating EL against incoming FlowFile

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2465:
--

Github user asfgit closed the pull request at:

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


> InferAvroSchema not evaluating EL against incoming FlowFile
> ---
>
> Key: NIFI-2465
> URL: https://issues.apache.org/jira/browse/NIFI-2465
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.5.0, 0.5.1, 0.7.0, 0.6.1
>Reporter: Bryan Bende
>Assignee: Simon Elliston Ball
>Priority: Minor
> Fix For: 1.1.0
>
>
> Many of the properties in InferAvroSchema support expression language, but 
> don't evaluate it against an incoming flow file. 
> Some examples:
> {code}
> context.getProperty(RECORD_NAME).evaluateAttributeExpressions().getValue()
> context.getProperty(HEADER_LINE_SKIP_COUNT).evaluateAttributeExpressions().asInteger()
> context.getProperty(ESCAPE_STRING).evaluateAttributeExpressions().getValue()  
>
> context.getProperty(QUOTE_STRING).evaluateAttributeExpressions().getValue()
> {code}
> These should all use the incoming flow file.



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

[GitHub] nifi issue #863: NIFI-2465 - InferAvroSchema EL support based on incoming Fl...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/863
  
I made one small change to also evaluate the record name and num records to 
analyze when doing JSON, but other than that looks good and merged to master, 
thanks!


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

[jira] [Commented] (NIFI-2465) InferAvroSchema not evaluating EL against incoming FlowFile

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2465:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/863
  
I made one small change to also evaluate the record name and num records to 
analyze when doing JSON, but other than that looks good and merged to master, 
thanks!


> InferAvroSchema not evaluating EL against incoming FlowFile
> ---
>
> Key: NIFI-2465
> URL: https://issues.apache.org/jira/browse/NIFI-2465
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.5.0, 0.5.1, 0.7.0, 0.6.1
>Reporter: Bryan Bende
>Assignee: Simon Elliston Ball
>Priority: Minor
> Fix For: 1.1.0
>
>
> Many of the properties in InferAvroSchema support expression language, but 
> don't evaluate it against an incoming flow file. 
> Some examples:
> {code}
> context.getProperty(RECORD_NAME).evaluateAttributeExpressions().getValue()
> context.getProperty(HEADER_LINE_SKIP_COUNT).evaluateAttributeExpressions().asInteger()
> context.getProperty(ESCAPE_STRING).evaluateAttributeExpressions().getValue()  
>
> context.getProperty(QUOTE_STRING).evaluateAttributeExpressions().getValue()
> {code}
> These should all use the incoming flow file.



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

[GitHub] nifi pull request #863: NIFI-2465 - InferAvroSchema EL support based on inco...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2465) InferAvroSchema not evaluating EL against incoming FlowFile

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2465 - InferAvroSchema EL support based on incoming FlowFiles

This closes #863.

Signed-off-by: Bryan Bende 


> InferAvroSchema not evaluating EL against incoming FlowFile
> ---
>
> Key: NIFI-2465
> URL: https://issues.apache.org/jira/browse/NIFI-2465
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.5.0, 0.5.1, 0.7.0, 0.6.1
>Reporter: Bryan Bende
>Assignee: Simon Elliston Ball
>Priority: Minor
> Fix For: 1.1.0
>
>
> Many of the properties in InferAvroSchema support expression language, but 
> don't evaluate it against an incoming flow file. 
> Some examples:
> {code}
> context.getProperty(RECORD_NAME).evaluateAttributeExpressions().getValue()
> context.getProperty(HEADER_LINE_SKIP_COUNT).evaluateAttributeExpressions().asInteger()
> context.getProperty(ESCAPE_STRING).evaluateAttributeExpressions().getValue()  
>
> context.getProperty(QUOTE_STRING).evaluateAttributeExpressions().getValue()
> {code}
> These should all use the incoming flow file.



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

[GitHub] nifi issue #863: NIFI-2465 - InferAvroSchema EL support based on incoming Fl...

[bbende]

Github user bbende commented on the issue:

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


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

[GitHub] nifi issue #873: Decoupling kerberos service and spnego principles and keyta...

[YolandaMDavis]

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/873
  
@mcgilman I'll take a look


---
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-2579) Support accessing FlowFile content directly via expression language

[Randy Gelhausen (JIRA)]

Randy Gelhausen created NIFI-2579:
-

 Summary: Support accessing FlowFile content directly via 
expression language
 Key: NIFI-2579
 URL: https://issues.apache.org/jira/browse/NIFI-2579
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Randy Gelhausen


If you want to use a FlowFile's content in routing logic, or in metadata for 
external APIs, you must use an ExtractText processor to pull the content into 
an attribute. This is confusing and seems extraneous- the natural inclination 
is to dive into expression language seeking the "content" property which 
doesn't exist today.



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

[GitHub] nifi pull request #873: Decoupling kerberos service and spnego principles an...

[mcgilman]

GitHub user mcgilman opened a pull request:

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

Decoupling kerberos service and spnego principles and keytabs

NIFI-2561: - Decoupling kerberos service and spnego principles and keytabs.

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

$ git pull https://github.com/mcgilman/nifi 2561

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

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


commit 94d21c748b7b5372add9c601d40006b3fedec47c
Author: Matt Gilman 
Date:   2016-08-16T15:13:36Z

NIFI-2561: - Decoupling kerberos service and spnege principles and keytabs.




---
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-2534) Error when stopping a process group the user doesn't have any permission for

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-2534:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Error when stopping a process group the user doesn't have any permission for
> 
>
> Key: NIFI-2534
> URL: https://issues.apache.org/jira/browse/NIFI-2534
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Bryan Bende
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 1.0.0
>
>
> I created a process group in a secure instance, then overrode the policy for 
> "view component" such that no user had view component for the group (left the 
> modify component inheriting from parent). Then right-clicked the process 
> group and chose stop, and the circle in the header stayed spinning.
> In Chrome Dev tools the error showed on line 1090 of nf-process-group.js 
> if (processGroupMap.has(processGroup.id)) {
> Saying "id" is undefined.



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

[GitHub] nifi pull request #867: [NIFI-2534] Fix JS error when stopping a process gro...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2534) Error when stopping a process group the user doesn't have any permission for

[ASF subversion and git services (JIRA)]

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

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

Commit 26f5c496d1d5345d4ab7e9f7a7af523e70101f44 in nifi's branch 
refs/heads/master from [~scottyaslan]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=26f5c49 ]

NIFI-2534 Fix JS error when stopping a process group

This closes #867.

Signed-off-by: Bryan Bende 


> Error when stopping a process group the user doesn't have any permission for
> 
>
> Key: NIFI-2534
> URL: https://issues.apache.org/jira/browse/NIFI-2534
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Bryan Bende
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 1.0.0
>
>
> I created a process group in a secure instance, then overrode the policy for 
> "view component" such that no user had view component for the group (left the 
> modify component inheriting from parent). Then right-clicked the process 
> group and chose stop, and the circle in the header stayed spinning.
> In Chrome Dev tools the error showed on line 1090 of nf-process-group.js 
> if (processGroupMap.has(processGroup.id)) {
> Saying "id" is undefined.



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

[jira] [Commented] (NIFI-2534) Error when stopping a process group the user doesn't have any permission for

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2534:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/867
  
Looks good, will merge to master, thanks!


> Error when stopping a process group the user doesn't have any permission for
> 
>
> Key: NIFI-2534
> URL: https://issues.apache.org/jira/browse/NIFI-2534
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Bryan Bende
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 1.0.0
>
>
> I created a process group in a secure instance, then overrode the policy for 
> "view component" such that no user had view component for the group (left the 
> modify component inheriting from parent). Then right-clicked the process 
> group and chose stop, and the circle in the header stayed spinning.
> In Chrome Dev tools the error showed on line 1090 of nf-process-group.js 
> if (processGroupMap.has(processGroup.id)) {
> Saying "id" is undefined.



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

[GitHub] nifi issue #867: [NIFI-2534] Fix JS error when stopping a process group

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/867
  
Looks good, will merge to master, thanks!


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

[jira] [Commented] (NIFI-2566) Clustered Nodes can become out of sync regarding which node is coordinator

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2566:
--

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/866
  
@JPercivall I pushed an update that should address this issue.


> Clustered Nodes can become out of sync regarding which node is coordinator
> --
>
> Key: NIFI-2566
> URL: https://issues.apache.org/jira/browse/NIFI-2566
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Occasionally, I will see the UI telling me that no Cluster Coordinator has 
> been elected. However, I can see in the logs that the node is sending 
> heartbeats to the coordinator.



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

[GitHub] nifi issue #866: NIFI-2566: Refactoring to improve robustness of cluster

[markap14]

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/866
  
@JPercivall I pushed an update that should address this 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.
---

[GitHub] nifi issue #867: [NIFI-2534] Fix JS error when stopping a process group

[bbende]

Github user bbende commented on the issue:

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


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

[jira] [Commented] (NIFI-2576) PutSQL assumes all Timestamps are provided in Epoch

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2576:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/869
  
Thanks for update, merged to master!

Just an FYI, I had a bit of trouble getting the changes to apply from the 
PR onto master... for future it would be easiest to have a specific branch with 
only one commit for the initial PR, rather than submitting from your master to 
NiFi master. Thanks again.


> PutSQL assumes all Timestamps are provided in Epoch
> ---
>
> Key: NIFI-2576
> URL: https://issues.apache.org/jira/browse/NIFI-2576
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Peter Wicks
>Assignee: Bryan Bende
> Fix For: 1.0.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When PutSQL sees a TIMESTAMP data type it assumes that it's being provided as 
> a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro 
> return timestamps as strings; and thus following the Avro->JSON->JSON To SQL 
> Route leads to timestamps as being strings.



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

[GitHub] nifi issue #869: NIFI-2576 - PutSQL assumes all Timestamps are provided in E...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/869
  
Thanks for update, merged to master!

Just an FYI, I had a bit of trouble getting the changes to apply from the 
PR onto master... for future it would be easiest to have a specific branch with 
only one commit for the initial PR, rather than submitting from your master to 
NiFi master. Thanks again.


---
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-2576) PutSQL assumes all Timestamps are provided in Epoch

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2576 Allowing PutSQL to use timestamps in epoch or string format

This closes #869.

Signed-off-by: Bryan Bende 


> PutSQL assumes all Timestamps are provided in Epoch
> ---
>
> Key: NIFI-2576
> URL: https://issues.apache.org/jira/browse/NIFI-2576
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Peter Wicks
>Assignee: Bryan Bende
> Fix For: 1.0.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When PutSQL sees a TIMESTAMP data type it assumes that it's being provided as 
> a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro 
> return timestamps as strings; and thus following the Avro->JSON->JSON To SQL 
> Route leads to timestamps as being strings.



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

[GitHub] nifi pull request #869: NIFI-2576 - PutSQL assumes all Timestamps are provid...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2576) PutSQL assumes all Timestamps are provided in Epoch

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-2576:
--
Fix Version/s: 1.0.0

> PutSQL assumes all Timestamps are provided in Epoch
> ---
>
> Key: NIFI-2576
> URL: https://issues.apache.org/jira/browse/NIFI-2576
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Peter Wicks
>Assignee: Bryan Bende
> Fix For: 1.0.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When PutSQL sees a TIMESTAMP data type it assumes that it's being provided as 
> a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro 
> return timestamps as strings; and thus following the Avro->JSON->JSON To SQL 
> Route leads to timestamps as being strings.



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

[jira] [Updated] (NIFI-2576) PutSQL assumes all Timestamps are provided in Epoch

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-2576:
--
Status: Patch Available  (was: Open)

> PutSQL assumes all Timestamps are provided in Epoch
> ---
>
> Key: NIFI-2576
> URL: https://issues.apache.org/jira/browse/NIFI-2576
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Peter Wicks
>Assignee: Bryan Bende
> Fix For: 1.0.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When PutSQL sees a TIMESTAMP data type it assumes that it's being provided as 
> a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro 
> return timestamps as strings; and thus following the Avro->JSON->JSON To SQL 
> Route leads to timestamps as being strings.



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

[jira] [Assigned] (NIFI-2576) PutSQL assumes all Timestamps are provided in Epoch

[Bryan Bende (JIRA)]

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

Bryan Bende reassigned NIFI-2576:
-

Assignee: Bryan Bende

> PutSQL assumes all Timestamps are provided in Epoch
> ---
>
> Key: NIFI-2576
> URL: https://issues.apache.org/jira/browse/NIFI-2576
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Peter Wicks
>Assignee: Bryan Bende
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When PutSQL sees a TIMESTAMP data type it assumes that it's being provided as 
> a Long in Epoch format.
> This doesn't make much sense since the Query Database tools that return Avro 
> return timestamps as strings; and thus following the Avro->JSON->JSON To SQL 
> Route leads to timestamps as being strings.



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

[jira] [Created] (NIFI-2578) RPG on NiFi 1.0 does not generate user auth request on NiFi 0.x

[Matthew Clarke (JIRA)]

Matthew Clarke created NIFI-2578:


 Summary: RPG on NiFi 1.0 does not generate user auth request on 
NiFi 0.x
 Key: NIFI-2578
 URL: https://issues.apache.org/jira/browse/NIFI-2578
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.0.0
Reporter: Matthew Clarke
Priority: Blocker


If you add a RPG to a secured NiFi 1.0 and point it at a secured NiFi 0.x 
release.  An authorization request is not generated on the NIFi 0.x 
instance/cluster.  The RPG on NiFi 1.0 shows unauthorized on the RPG.  This 
would require an admin for the NiFi 0.x to manually edit the 
authorized-users.xml file and restart their production NiFi 0.x to add the new 
RPG users.



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

[jira] [Commented] (NIFI-2397) Create 0.x patch for premature closure on content stream

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2397:
--

Github user mosermw closed the pull request at:

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


> Create 0.x patch for premature closure on content stream
> 
>
> Key: NIFI-2397
> URL: https://issues.apache.org/jira/browse/NIFI-2397
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Reporter: Joseph Witt
>Assignee: Michael Moser
>Priority: Blocker
> Fix For: 0.8.0, 0.7.1
>
>




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

[jira] [Commented] (NIFI-2397) Create 0.x patch for premature closure on content stream

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2397:
--

Github user mosermw commented on the issue:

https://github.com/apache/nifi/pull/844
  
Awesome, thanks @pvillard31, I was worried that this wouldn't apply cleanly 
after the recent changes to the same code from NIFI-2551, but I'm glad it 
worked out.


> Create 0.x patch for premature closure on content stream
> 
>
> Key: NIFI-2397
> URL: https://issues.apache.org/jira/browse/NIFI-2397
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Reporter: Joseph Witt
>Assignee: Michael Moser
>Priority: Blocker
> Fix For: 0.8.0, 0.7.1
>
>




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

[GitHub] nifi issue #844: NIFI-2397 merging patch for NIFI-2376 from master into 0.x ...

[mosermw]

Github user mosermw commented on the issue:

https://github.com/apache/nifi/pull/844
  
Awesome, thanks @pvillard31, I was worried that this wouldn't apply cleanly 
after the recent changes to the same code from NIFI-2551, but I'm glad it 
worked out.


---
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.
---