[jira] [Commented] (NIFI-2936) TestExecuteProcess errors in Travis CI environment

[Koji Kawamura (JIRA)]

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

Koji Kawamura commented on NIFI-2936:
-

The same error with Travis happened on CentOS.

> TestExecuteProcess errors in Travis CI environment
> --
>
> Key: NIFI-2936
> URL: https://issues.apache.org/jira/browse/NIFI-2936
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Reporter: Aldrin Piri
>Assignee: Koji Kawamura
>Priority: Blocker
> Fix For: 1.1.0
>
>
> The introduction of redirecting error stream and the accompanying tests for 
> TestExecuteProcess [1] are causing Travis to have issues with the build 
> fairly consistently starting with the initial travis build #4109 [2]. 
> [1] 
> https://github.com/apache/nifi/commit/27dba60f27579ca9f33aa1afbf4bb46182d57df4
> [2] https://travis-ci.org/apache/nifi/builds/168776478



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

[GitHub] nifi-minifi pull request #:

[trixpan]

Github user trixpan commented on the pull request:


https://github.com/apache/nifi-minifi/commit/483a4f996197b33c3e4de594a33f51e4b573fc44#commitcomment-19592136
  
In minifi-docs/src/main/markdown/minifi-java-agent-quick-start.md:
In minifi-docs/src/main/markdown/minifi-java-agent-quick-start.md on line 
275:
Verb missing 


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

[GitHub] nifi-minifi pull request #:

[trixpan]

Github user trixpan commented on the pull request:


https://github.com/apache/nifi-minifi/commit/483a4f996197b33c3e4de594a33f51e4b573fc44#commitcomment-19592190
  
In minifi-docs/src/main/markdown/minifi-java-agent-quick-start.md:
In minifi-docs/src/main/markdown/minifi-java-agent-quick-start.md on line 
93:
May be worth to explain how TLS can be used.  And aren't handlehhtprequest 
and handlehhtpreply dependent on controller services? 


---
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-2955) NiFi 1.0 UI works slower then NiFi 0.7.1

[Dmitry Lukyanov (JIRA)]

Dmitry Lukyanov created NIFI-2955:
-

 Summary: NiFi 1.0 UI works slower then NiFi 0.7.1
 Key: NIFI-2955
 URL: https://issues.apache.org/jira/browse/NIFI-2955
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Affects Versions: 1.0.0
Reporter: Dmitry Lukyanov
Priority: Minor


The User Interface of the NiFi in the version 1.0 works slower then UI in 0.7.1
It seems that browser consumes more memory...

Firefox 42.0



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

[jira] [Commented] (NIFI-2934) Archiver still not respecting nifi.content.repository.archive.max.usage.percentage

[Joseph Gresock (JIRA)]

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

Joseph Gresock commented on NIFI-2934:
--

I was able to reproduce the scenario described in the ticket.  The log 
statements that I see spammed after restarting nifi is:

2016-10-27 13:18:20,991 INFO [main] o.a.n.c.repository.FileSystemRepository 
Found unknown file /data/nifi/content_repository/123/1477571460115-1147 
(10485760 bytes) in File System Repository; archiving file

In the case I reproduced, this was printed for ~5600 files in the 
content_repository.  After this point, the disk usage went back down below the 
configured max usage percentage.

One NiFi dev asked me if there were any files in the 
content_repository/*/archive directories during this scenario.  I just checked, 
and in the worker that has not been restarted yet, there are no files in 
archive.  However, in the worker that has been restarted, ~1GB is in the 
archive directories.

> Archiver still not respecting 
> nifi.content.repository.archive.max.usage.percentage
> --
>
> Key: NIFI-2934
> URL: https://issues.apache.org/jira/browse/NIFI-2934
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.7.0, 0.7.1
>Reporter: Joseph Gresock
> Attachments: Disk-Usage-Increasing.png, NiFi-80-percent-disk.png, 
> Queued.png, System-Diagnostics.png, content_repository usage.png, lsof.txt
>
>
> This seems related to NIFI-1726: we've noticed that the content repository 
> takes up increasingly more space over time, even beyond the configured max 
> usage percentage (see images).  After restarting the NiFi cluster we get an 
> immediate drop in disk usage with lots of log statements indicating that 
> expired content is being removed.  
> Not sure if this is related, but we also often get "Too many open files" 
> during this expiration process after NiFi restart, despite lsof indicating a 
> count far lower than our configured nofile and fs-max.
> In the environment indicated by the pictures,  
> nifi.content.repository.archive.max.usage.percentage = 50%.  Note that the 
> flow itself only has ~240GB queued across the entire cluster, but each 
> content_repository directory has over 360GB on each worker.  Also note the 
> disk usage graph increasing above 50% on each worker, until we finally 
> restart and then the usage drops below 50%.



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

[jira] [Commented] (NIFI-2955) NiFi 1.0 UI works slower then NiFi 0.7.1

[Scott Aslan (JIRA)]

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

Scott Aslan commented on NIFI-2955:
---

Dmitry,

Thank you for filing a Jira. Could you possibly provide more details as to how 
to reproduce and where specifically you are feeling 'slowness'?

-Scott Aslan

> NiFi 1.0 UI works slower then NiFi 0.7.1
> 
>
> Key: NIFI-2955
> URL: https://issues.apache.org/jira/browse/NIFI-2955
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Dmitry Lukyanov
>Priority: Minor
>
> The User Interface of the NiFi in the version 1.0 works slower then UI in 
> 0.7.1
> It seems that browser consumes more memory...
> Firefox 42.0



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

[jira] [Created] (NIFI-2956) GetHDFS - directory path is evaluated once

[Pierre Villard (JIRA)]

Pierre Villard created NIFI-2956:


 Summary: GetHDFS - directory path is evaluated once
 Key: NIFI-2956
 URL: https://issues.apache.org/jira/browse/NIFI-2956
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 1.0.0
Reporter: Pierre Villard
Assignee: Pierre Villard


The directory path in GetHDFS processor accepts expression language but the 
path is only evaluated once. Consequently, it is not possible to set a path 
like:

{code}
/my/path/${now():format('/MM/dd')}
{code}

Workaround: use ListHDFS processor in combination with FetchHDFS processor.



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

[jira] [Commented] (NIFI-2116) Translate Documentation Into Spanish

[Chagara (JIRA)]

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

Chagara commented on NIFI-2116:
---

I'll try to update this weekend and try to complete more of the docs.

> Translate Documentation Into Spanish
> 
>
> Key: NIFI-2116
> URL: https://issues.apache.org/jira/browse/NIFI-2116
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Documentation & Website
>Reporter: Chagara
>Assignee: Chagara
>Priority: Minor
>
> Create documentation in Spanish to expand NIFI reach.



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

[GitHub] nifi issue #854: NIFI-2564 Add support for HL7 composite component names

[jfrazee]

Github user jfrazee commented on the issue:

https://github.com/apache/nifi/pull/854
  
@trixpan I'll be getting back to this today. There was a bug fix that had 
to slide in before this too so it's not going to rebase cleanly anymore.


---
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 #1161: NIFI-2950 Adding support for whole number hex value...

[JPercivall]

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

https://github.com/apache/nifi/pull/1161#discussion_r85343844
  
--- Diff: nifi-docs/src/main/asciidoc/expression-language-guide.adoc ---
@@ -1645,6 +1649,34 @@ Divide. This is to preserve backwards compatibility 
and to not force rounding er
 
|===
 
 [.function]
+=== fromRadix
+
+*Description*: [.description]#Converts the Subject from a specified Radix 
(or number base) to a base ten whole number. The subject will converted as is, 
without interpretation, and all characters
+must be valid for the base being converted from. For example converting 
"0xFF" from hex will not work due to it not x not being a valid hex character.
--- End diff --

Yup you're right, will fix.


---
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-2950) Allow literal interpretation of hex numbers as whole numbers in EL

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2950:
--

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

https://github.com/apache/nifi/pull/1161#discussion_r85343844
  
--- Diff: nifi-docs/src/main/asciidoc/expression-language-guide.adoc ---
@@ -1645,6 +1649,34 @@ Divide. This is to preserve backwards compatibility 
and to not force rounding er
 
|===
 
 [.function]
+=== fromRadix
+
+*Description*: [.description]#Converts the Subject from a specified Radix 
(or number base) to a base ten whole number. The subject will converted as is, 
without interpretation, and all characters
+must be valid for the base being converted from. For example converting 
"0xFF" from hex will not work due to it not x not being a valid hex character.
--- End diff --

Yup you're right, will fix.


> Allow literal interpretation of hex numbers as whole numbers in EL
> --
>
> Key: NIFI-2950
> URL: https://issues.apache.org/jira/browse/NIFI-2950
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>Priority: Minor
>
> Currently in EL you cannot pass hex numbers as a whole number and instead 
> only decimals support them. Whole numbers should support being passed in as 
> hex too.
> This was brought up by this SO[1] question.
> [1] 
> http://stackoverflow.com/questions/40265791/applying-string-manipulations-mathematical-operations-to-the-contents-of-a-flow/40267507#40267507



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

[jira] [Commented] (NIFI-2564) Add support for HL7 composite component names

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2564:
--

Github user jfrazee commented on the issue:

https://github.com/apache/nifi/pull/854
  
@trixpan I'll be getting back to this today. There was a bug fix that had 
to slide in before this too so it's not going to rebase cleanly anymore.


> Add support for HL7 composite component names
> -
>
> Key: NIFI-2564
> URL: https://issues.apache.org/jira/browse/NIFI-2564
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Priority: Minor
>
> NIFI-2090 added parsing for segments and components but didn't include the 
> "friendly" names for the composite components. For example, 
> ExtractHL7Attributes can currently parse and output PID.PatientName.XPN.2, 
> which corresponds to the patient's given name, but it'd be more helpful if 
> the attribute was something like PID.PatientName.GivenName or 
> PID.PatientName.XPN.GivenName.



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

[GitHub] nifi issue #1155: Edit Policy - Bulk user/group add

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/1155
  
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 pull request #1163: NIFI-2956 - GetHDFS - fixed directory path evaluati...

[pvillard31]

GitHub user pvillard31 opened a pull request:

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

NIFI-2956 - GetHDFS - fixed directory path evaluation



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

$ git pull https://github.com/pvillard31/nifi NIFI-2956

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

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


commit 549ff4b97678b6e7952a6ca10c04a773486156f7
Author: Pierre Villard 
Date:   2016-10-27T14:37:29Z

NIFI-2956 - GetHDFS - fixed directly path evaluation




---
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-2956) GetHDFS - directory path is evaluated once

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2956:
--

GitHub user pvillard31 opened a pull request:

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

NIFI-2956 - GetHDFS - fixed directory path evaluation



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

$ git pull https://github.com/pvillard31/nifi NIFI-2956

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

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


commit 549ff4b97678b6e7952a6ca10c04a773486156f7
Author: Pierre Villard 
Date:   2016-10-27T14:37:29Z

NIFI-2956 - GetHDFS - fixed directly path evaluation




> GetHDFS - directory path is evaluated once
> --
>
> Key: NIFI-2956
> URL: https://issues.apache.org/jira/browse/NIFI-2956
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>
> The directory path in GetHDFS processor accepts expression language but the 
> path is only evaluated once. Consequently, it is not possible to set a path 
> like:
> {code}
> /my/path/${now():format('/MM/dd')}
> {code}
> Workaround: use ListHDFS processor in combination with FetchHDFS processor.



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

[jira] [Commented] (NIFI-2956) GetHDFS - directory path is evaluated once

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2956:
---

[~pvillard] if you can find some reviewer traction for this please do go ahead 
and put it on 1.1.  I tried to get the 1.1 list down to a releasable level and 
we should avoid bringing new unreviewed things in but if you do get traction 
please do go ahead and put on there.

thanks

> GetHDFS - directory path is evaluated once
> --
>
> Key: NIFI-2956
> URL: https://issues.apache.org/jira/browse/NIFI-2956
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Pierre Villard
>Assignee: Pierre Villard
> Fix For: 1.2.0
>
>
> The directory path in GetHDFS processor accepts expression language but the 
> path is only evaluated once. Consequently, it is not possible to set a path 
> like:
> {code}
> /my/path/${now():format('/MM/dd')}
> {code}
> Workaround: use ListHDFS processor in combination with FetchHDFS processor.



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

[jira] [Updated] (NIFI-2956) GetHDFS - directory path is evaluated once

[Pierre Villard (JIRA)]

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

Pierre Villard updated NIFI-2956:
-
Fix Version/s: 1.2.0
   Status: Patch Available  (was: Open)

I don't set the fix version to 1.1.0 as we are trying to get 1.1.0 out and 
based on the fact that there is a workaround to this issue. For now I'll set 
the fix version to 1.2.0 but if someone wants to have a look... feel free to do 
so!

> GetHDFS - directory path is evaluated once
> --
>
> Key: NIFI-2956
> URL: https://issues.apache.org/jira/browse/NIFI-2956
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Pierre Villard
>Assignee: Pierre Villard
> Fix For: 1.2.0
>
>
> The directory path in GetHDFS processor accepts expression language but the 
> path is only evaluated once. Consequently, it is not possible to set a path 
> like:
> {code}
> /my/path/${now():format('/MM/dd')}
> {code}
> Workaround: use ListHDFS processor in combination with FetchHDFS processor.



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

[jira] [Commented] (NIFI-2286) Policies: "Add user to policy" and "Remove" icons do not have hover help text

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2884: - Adding support to selecting multiple users before updating a 
policy.
NIFI-2533: - Only including a user/group in the search results if they are not 
currently selected.
NIFI-2286: - Providing a tooltip for the add user and remove policy button.

This closes #1155.

Signed-off-by: Bryan Bende 


> Policies:  "Add user to policy" and "Remove" icons do not have hover help text
> --
>
> Key: NIFI-2286
> URL: https://issues.apache.org/jira/browse/NIFI-2286
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Matt Gilman
>Priority: Minor
>  Labels: UI
> Fix For: 1.1.0
>
>
> The "Add user to policy" and "Remove" buttons in the Access Policies window 
> do not have any help text displayed when the user hovers over them.
> This will be really helpful especially to new users of the Authorization API.



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

[jira] [Commented] (NIFI-2884) UI - Support bulk user/group add when editing a policy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2884:
--

Github user asfgit closed the pull request at:

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


> UI - Support bulk user/group add when editing a policy
> --
>
> Key: NIFI-2884
> URL: https://issues.apache.org/jira/browse/NIFI-2884
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>




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

[jira] [Commented] (NIFI-2533) When searching for users to add to a policy, should filter out users that are already on the policy

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2884: - Adding support to selecting multiple users before updating a 
policy.
NIFI-2533: - Only including a user/group in the search results if they are not 
currently selected.
NIFI-2286: - Providing a tooltip for the add user and remove policy button.

This closes #1155.

Signed-off-by: Bryan Bende 


> When searching for users to add to a policy, should filter out users that are 
> already on the policy
> ---
>
> Key: NIFI-2533
> URL: https://issues.apache.org/jira/browse/NIFI-2533
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: NIFI-2533.png
>
>
> As shown in the attached screenshot.  User1 is already on the policy.  When 
> adding additional users to the policy, the "Search users" window should 
> filter out User1 from the list.



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

[GitHub] nifi pull request #1155: Edit Policy - Bulk user/group add

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2884) UI - Support bulk user/group add when editing a policy

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2884: - Adding support to selecting multiple users before updating a 
policy.
NIFI-2533: - Only including a user/group in the search results if they are not 
currently selected.
NIFI-2286: - Providing a tooltip for the add user and remove policy button.

This closes #1155.

Signed-off-by: Bryan Bende 


> UI - Support bulk user/group add when editing a policy
> --
>
> Key: NIFI-2884
> URL: https://issues.apache.org/jira/browse/NIFI-2884
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>




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

[jira] [Updated] (NIFI-2884) UI - Support bulk user/group add when editing a policy

[Bryan Bende (JIRA)]

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

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

> UI - Support bulk user/group add when editing a policy
> --
>
> Key: NIFI-2884
> URL: https://issues.apache.org/jira/browse/NIFI-2884
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.1.0
>
>




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

[jira] [Updated] (NIFI-2533) When searching for users to add to a policy, should filter out users that are already on the policy

[Bryan Bende (JIRA)]

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

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

> When searching for users to add to a policy, should filter out users that are 
> already on the policy
> ---
>
> Key: NIFI-2533
> URL: https://issues.apache.org/jira/browse/NIFI-2533
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: NIFI-2533.png
>
>
> As shown in the attached screenshot.  User1 is already on the policy.  When 
> adding additional users to the policy, the "Search users" window should 
> filter out User1 from the list.



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

[jira] [Updated] (NIFI-2286) Policies: "Add user to policy" and "Remove" icons do not have hover help text

[Bryan Bende (JIRA)]

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

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

> Policies:  "Add user to policy" and "Remove" icons do not have hover help text
> --
>
> Key: NIFI-2286
> URL: https://issues.apache.org/jira/browse/NIFI-2286
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Matt Gilman
>Priority: Minor
>  Labels: UI
> Fix For: 1.1.0
>
>
> The "Add user to policy" and "Remove" buttons in the Access Policies window 
> do not have any help text displayed when the user hovers over them.
> This will be really helpful especially to new users of the Authorization API.



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

[jira] [Created] (NIFI-2957) ZooKeeper migration toolkit

[Jeff Storck (JIRA)]

Jeff Storck created NIFI-2957:
-

 Summary: ZooKeeper migration toolkit
 Key: NIFI-2957
 URL: https://issues.apache.org/jira/browse/NIFI-2957
 Project: Apache NiFi
  Issue Type: New Feature
  Components: Tools and Build
Affects Versions: 0.7.1, 1.0.0
Reporter: Jeff Storck
Assignee: Jeff Storck
 Fix For: 1.2.0


When upgrading from NiFi 0.x to 1.x, or when it is desired to move from the 
embedded ZooKeeper to an external ZooKeeper, state from ZooKeeper needs to be 
migrated.

Initial considerations:
* Username/password protection of nodes is not supported in NiFi 1.x.. Those 
nodes that are configured that way in ZooKeeper need to be migrated to have an 
open ACL.
* The toolkit will support a mode to read data from a configurable root node in 
a source ZooKeeper, and the data will be written to a file designated via CLI.
* The toolkit will support a mode to write data to a destination ZooKeeper
* The toolkit will not allow data to be written to the same ZooKeeper from 
which the source data was obtained.
* The toolkit will not support reconnecting to ZooKeeper if it is disconnected. 
 The user can rerun the tool.
* The toolkit will support ZooKeepers configured with Kerberos.



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

[jira] [Assigned] (NIFI-2564) Add support for HL7 composite component names

[Joseph Witt (JIRA)]

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

Joseph Witt reassigned NIFI-2564:
-

Assignee: Joseph Witt

> Add support for HL7 composite component names
> -
>
> Key: NIFI-2564
> URL: https://issues.apache.org/jira/browse/NIFI-2564
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Assignee: Joseph Witt
>Priority: Minor
>
> NIFI-2090 added parsing for segments and components but didn't include the 
> "friendly" names for the composite components. For example, 
> ExtractHL7Attributes can currently parse and output PID.PatientName.XPN.2, 
> which corresponds to the patient's given name, but it'd be more helpful if 
> the attribute was something like PID.PatientName.GivenName or 
> PID.PatientName.XPN.GivenName.



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

[jira] [Commented] (NIFI-2943) tls-toolkit pkcs12 truststore 0 entries

[Bryan Rosander (JIRA)]

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

Bryan Rosander commented on NIFI-2943:
--

If you tell the keytool to use Bouncy Castle, it can see the truststore entry:
{code}
keytool -list -keystore truststore.pkcs12 -providername BC -providerpath 
../../nifi-toolkit-1.1.0-SNAPSHOT/lib/bcprov-jdk15on-1.54.jar -providerclass 
org.bouncycastle.jce.provider.BouncyCastleProvider -storetype PKCS12 -storepass 
CHANGE

Keystore type: PKCS12
Keystore provider: BC

Your keystore contains 1 entry

nifi-cert, Oct 27, 2016, trustedCertEntry,
Certificate fingerprint (SHA1): 
FA:33:64:AC:0A:34:2B:B8:2D:27:DA:96:4F:7A:FB:72:FF:D4:DB:9
{code}

> tls-toolkit pkcs12 truststore 0 entries
> ---
>
> Key: NIFI-2943
> URL: https://issues.apache.org/jira/browse/NIFI-2943
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>Priority: Minor
>
> When pkcs12 is used by the tls-toolkit, the resulting truststore has no 
> entries when inspected by the keytool and the tls-toolkit certificate 
> authority certificate is not trusted by NiFi.
> This seems to be due to the Java pkcs12 provider not supporting certificate 
> entries:
> http://stackoverflow.com/questions/3614239/pkcs12-java-keystore-from-ca-and-user-certificate-in-java#answer-3614405
> The Bouncy Castle provider does seem to support certificates but we may not 
> want to explicitly use that provider from within NiFi.



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

[jira] [Created] (NIFI-2958) Missing Error Message in PutElasticsearchHttp

[Justin M Cavinee (JIRA)]

Justin M Cavinee created NIFI-2958:
--

 Summary: Missing Error Message in PutElasticsearchHttp
 Key: NIFI-2958
 URL: https://issues.apache.org/jira/browse/NIFI-2958
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Reporter: Justin M Cavinee
Priority: Minor


Error messages are not being shown properly when the push to Elastic Search 
fails.  

When I get a failure, it just reads:
Failed to Insert StandardFlowFileRecord[..] into Elastic Search due to , 
transferring to failure.

With nothing following the due to.  If I use curl to directly push to content 
to ElasticSearch then I do get a proper error message, which should be put into 
the Elastic Search log.



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

[jira] [Updated] (NIFI-2850) Provide ability for a FlowFile to be migrated from one Process Session to another

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2850:
--
Assignee: Oleg Zhurakousky  (was: Joseph Witt)

> Provide ability for a FlowFile to be migrated from one Process Session to 
> another
> -
>
> Key: NIFI-2850
> URL: https://issues.apache.org/jira/browse/NIFI-2850
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Oleg Zhurakousky
> Fix For: 1.1.0
>
>
> Currently, the MergeContent processor creates a separate ProcessSession for 
> each FlowFile that it pulls. This is done so that we can ensure that we can 
> commit all Process Sessions when a bin is full. Unfortunately, this means 
> that MergeContent is required to call ProcessSession.get() many times, which 
> adds a lot of contention on the FlowFile Queue. If we allow FlowFiles to be 
> migrated from 1 session to another, we can have a session per bin, and then 
> use ProcessSession.get(100) to greatly reduce lock contention. This will 
> likely have benefits in other processors as well.



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

[jira] [Updated] (NIFI-2724) JMX Processor

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2724:
--
Assignee: Andre  (was: Joseph Witt)

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



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

[jira] [Updated] (NIFI-2920) Swapped FlowFiles are not removed from content repo when a queue is emptied.

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-2920:
--
Attachment: NIFI-2920.patch

I took [~markap14] 's patch from NIFI-2925 which was for 1.0 and ported it to 
0.x. From my testing this appears to resolve the problem described.

> Swapped FlowFiles are not removed from content repo when a queue is emptied.
> 
>
> Key: NIFI-2920
> URL: https://issues.apache.org/jira/browse/NIFI-2920
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.1
> Environment: Linux
>Reporter: Matthew Clarke
>Priority: Blocker
> Fix For: 0.8.0
>
> Attachments: NIFI-2920.patch
>
>
> If a queue contains enough FlowFiles to trigger swapping to occur and a user 
> selects "empty queue" or sets file expiration, only the content claims 
> associated to FlowFiles that were not swapped get removed from the content 
> repository.  All other content claims are left in the content repository and 
> are not moved to archive and/or purged.
> A restart of NiFi will produce app log messages about these unknown files 
> left in the content repo and will at that time move them to archive or purge 
> them.



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

[jira] [Commented] (NIFI-2934) Archiver still not respecting nifi.content.repository.archive.max.usage.percentage

[Bryan Bende (JIRA)]

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

Bryan Bende commented on NIFI-2934:
---

[~jgresock] I posted a patch on https://issues.apache.org/jira/browse/NIFI-2920 
for what appears to be a similar problem. Was wondering if you wanted to try 
running with that patch and see if it resolves the issues you have been seeing.

> Archiver still not respecting 
> nifi.content.repository.archive.max.usage.percentage
> --
>
> Key: NIFI-2934
> URL: https://issues.apache.org/jira/browse/NIFI-2934
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.7.0, 0.7.1
>Reporter: Joseph Gresock
> Attachments: Disk-Usage-Increasing.png, NiFi-80-percent-disk.png, 
> Queued.png, System-Diagnostics.png, content_repository usage.png, lsof.txt
>
>
> This seems related to NIFI-1726: we've noticed that the content repository 
> takes up increasingly more space over time, even beyond the configured max 
> usage percentage (see images).  After restarting the NiFi cluster we get an 
> immediate drop in disk usage with lots of log statements indicating that 
> expired content is being removed.  
> Not sure if this is related, but we also often get "Too many open files" 
> during this expiration process after NiFi restart, despite lsof indicating a 
> count far lower than our configured nofile and fs-max.
> In the environment indicated by the pictures,  
> nifi.content.repository.archive.max.usage.percentage = 50%.  Note that the 
> flow itself only has ~240GB queued across the entire cluster, but each 
> content_repository directory has over 360GB on each worker.  Also note the 
> disk usage graph increasing above 50% on each worker, until we finally 
> restart and then the usage drops below 50%.



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

[jira] [Updated] (NIFI-2920) Swapped FlowFiles are not removed from content repo when a queue is emptied.

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-2920:
--
Affects Version/s: 0.7.0
   0.7.1

> Swapped FlowFiles are not removed from content repo when a queue is emptied.
> 
>
> Key: NIFI-2920
> URL: https://issues.apache.org/jira/browse/NIFI-2920
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.7.0, 0.6.1, 0.7.1
> Environment: Linux
>Reporter: Matthew Clarke
>Priority: Blocker
> Fix For: 0.8.0
>
> Attachments: NIFI-2920.patch
>
>
> If a queue contains enough FlowFiles to trigger swapping to occur and a user 
> selects "empty queue" or sets file expiration, only the content claims 
> associated to FlowFiles that were not swapped get removed from the content 
> repository.  All other content claims are left in the content repository and 
> are not moved to archive and/or purged.
> A restart of NiFi will produce app log messages about these unknown files 
> left in the content repo and will at that time move them to archive or purge 
> them.



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

[jira] [Updated] (NIFI-2369) ConvertCSVtoAvro should allow EL for CSV Properties

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2369:
--
Assignee: Matt Burgess  (was: Joseph Witt)

> ConvertCSVtoAvro should allow EL for CSV Properties
> ---
>
> Key: NIFI-2369
> URL: https://issues.apache.org/jira/browse/NIFI-2369
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
> Environment: N/A
>Reporter: Simon Elliston Ball
>Assignee: Matt Burgess
>Priority: Minor
>  Labels: starter
> Attachments: ConvertCSVAvro_-_Delimiter_Example.xml
>
>
> When creating a common processing flow, it would be useful to be able to 
> parameterise the CSV properties, delimiter, quote and escape characters and 
> other processing settings. It should be possible to set these based on 
> attributes of the incoming CSV file.



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

[jira] [Created] (NIFI-2959) TLS Toolkit should provide the correct DN to authorizers.xml for the Initial Admin Identity

[Andy LoPresto (JIRA)]

Andy LoPresto created NIFI-2959:
---

 Summary: TLS Toolkit should provide the correct DN to 
authorizers.xml for the Initial Admin Identity
 Key: NIFI-2959
 URL: https://issues.apache.org/jira/browse/NIFI-2959
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Tools and Build
Affects Versions: 1.0.0
Reporter: Andy LoPresto


Users frequently experience a user permission error when trying to access a 
secured instance of NiFi after using the TLS toolkit to create a client 
certificate because the whitespace formatting of the provided DN differs from 
the resulting certificate subject. The toolkit should output a clear log line 
with the exact string that should be copied to {{authorizers.xml}} *Initial 
Admin Identity* when a client certificate is generated, and if a special flag 
is invoked during the command line call, the provided {{authorizers.xml}} 
should be updated directly. 



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

[jira] [Commented] (NIFI-2943) tls-toolkit pkcs12 truststore 0 entries

[Andy LoPresto (JIRA)]

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

Andy LoPresto commented on NIFI-2943:
-

This is good to know and document, but we can't expect users to be aware of 
this. If they search online for "use keytool to check truststore", the vast 
majority of instructions will not include this information. 

> tls-toolkit pkcs12 truststore 0 entries
> ---
>
> Key: NIFI-2943
> URL: https://issues.apache.org/jira/browse/NIFI-2943
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>Priority: Minor
>
> When pkcs12 is used by the tls-toolkit, the resulting truststore has no 
> entries when inspected by the keytool and the tls-toolkit certificate 
> authority certificate is not trusted by NiFi.
> This seems to be due to the Java pkcs12 provider not supporting certificate 
> entries:
> http://stackoverflow.com/questions/3614239/pkcs12-java-keystore-from-ca-and-user-certificate-in-java#answer-3614405
> The Bouncy Castle provider does seem to support certificates but we may not 
> want to explicitly use that provider from within NiFi.



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

[GitHub] nifi issue #1151: [NIFI-2888] Display processor fill color when zoomed in/ou...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1151
  
Personally, I think if we're going to attempt to draw a preview of the 
processor block we need to fill in some of the empty space. Can we try putting 
in the name of the processor and drawing the two blue bars where we would 
render the In/Out stats?

Also, can we use more of the vertical space for the preview in the color 
dialog for a label? Currently, it looks like the label preview is the same 
dimensions as a processor.


---
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-2888) Display processor fill color when sufficiently zoomed out.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2888:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1151
  
Personally, I think if we're going to attempt to draw a preview of the 
processor block we need to fill in some of the empty space. Can we try putting 
in the name of the processor and drawing the two blue bars where we would 
render the In/Out stats?

Also, can we use more of the vertical space for the preview in the color 
dialog for a label? Currently, it looks like the label preview is the same 
dimensions as a processor.


> Display processor fill color when sufficiently zoomed out.
> --
>
> Key: NIFI-2888
> URL: https://issues.apache.org/jira/browse/NIFI-2888
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.2.0
>
> Attachments: processor-change-color.png
>
>
> As a user when viewing the zoomed out overview of my flow I want to be able 
> to quickly identify processors based on their fill color.



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

[jira] [Updated] (NIFI-2369) ConvertCSVtoAvro should allow EL for CSV Properties

[Matt Burgess (JIRA)]

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

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

> ConvertCSVtoAvro should allow EL for CSV Properties
> ---
>
> Key: NIFI-2369
> URL: https://issues.apache.org/jira/browse/NIFI-2369
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
> Environment: N/A
>Reporter: Simon Elliston Ball
>Assignee: Matt Burgess
>Priority: Minor
>  Labels: starter
> Attachments: ConvertCSVAvro_-_Delimiter_Example.xml
>
>
> When creating a common processing flow, it would be useful to be able to 
> parameterise the CSV properties, delimiter, quote and escape characters and 
> other processing settings. It should be possible to set these based on 
> attributes of the incoming CSV file.



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

[GitHub] nifi pull request #1164: NIFI-2954 - Treating bcprov and bcpkix dependencies...

[apiri]

GitHub user apiri opened a pull request:

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

NIFI-2954 - Treating bcprov and bcpkix dependencies as provided by nifi in 
lib

NIFI-2954 - Treating bcprov and bcpkix dependencies as provided by nifi in 
lib and updating projects to include them as provided where needed.

Not sure of the best direction to take this, but the general thought 
process were to treat bcprov and bcpkix as "framework level" dependencies and 
include them in lib.  This allowed these common, foundational libraries to be 
shared by the entirety of the extension space.

I am not a fan of having to add these every place the BC items are 
transitively used but did not also want to make a specified dependency in a 
parent pom across the entirety of the project.


Before patch:
```
drwxr-xr-x 3 apiri staff  102 Oct 27 15:08 nifi-1.1.0-SNAPSHOT-bin
-rw-r--r-- 1 apiri staff 608M Oct 27 15:09 nifi-1.1.0-SNAPSHOT-bin.tar.gz
-rw-r--r-- 1 apiri staff 608M Oct 27 15:08 nifi-1.1.0-SNAPSHOT-bin.zip
```

After patch:
```
drwxr-xr-x 3 apiri staff  102 Oct 27 15:17 nifi-1.1.0-SNAPSHOT-bin
-rw-r--r-- 1 apiri staff 778M Oct 27 15:18 nifi-1.1.0-SNAPSHOT-bin.tar.gz
-rw-r--r-- 1 apiri staff 779M Oct 27 15:18 nifi-1.1.0-SNAPSHOT-bin.zip
```

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

$ git pull https://github.com/apiri/incubator-nifi nifi-2954

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

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


commit bc4b358b477df0cc113b14af02b5f89d0b1b38e5
Author: Aldrin Piri 
Date:   2016-10-27T19:12:39Z

NIFI-2954 - Treating bcprov and bcpkix dependencies as provided by nifi in 
lib and updating projects to include them as provided where needed.




---
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-2954) Bouncycastle dependencies are duplicated throughout NARs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2954:
--

GitHub user apiri opened a pull request:

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

NIFI-2954 - Treating bcprov and bcpkix dependencies as provided by nifi in 
lib

NIFI-2954 - Treating bcprov and bcpkix dependencies as provided by nifi in 
lib and updating projects to include them as provided where needed.

Not sure of the best direction to take this, but the general thought 
process were to treat bcprov and bcpkix as "framework level" dependencies and 
include them in lib.  This allowed these common, foundational libraries to be 
shared by the entirety of the extension space.

I am not a fan of having to add these every place the BC items are 
transitively used but did not also want to make a specified dependency in a 
parent pom across the entirety of the project.


Before patch:
```
drwxr-xr-x 3 apiri staff  102 Oct 27 15:08 nifi-1.1.0-SNAPSHOT-bin
-rw-r--r-- 1 apiri staff 608M Oct 27 15:09 nifi-1.1.0-SNAPSHOT-bin.tar.gz
-rw-r--r-- 1 apiri staff 608M Oct 27 15:08 nifi-1.1.0-SNAPSHOT-bin.zip
```

After patch:
```
drwxr-xr-x 3 apiri staff  102 Oct 27 15:17 nifi-1.1.0-SNAPSHOT-bin
-rw-r--r-- 1 apiri staff 778M Oct 27 15:18 nifi-1.1.0-SNAPSHOT-bin.tar.gz
-rw-r--r-- 1 apiri staff 779M Oct 27 15:18 nifi-1.1.0-SNAPSHOT-bin.zip
```

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

$ git pull https://github.com/apiri/incubator-nifi nifi-2954

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

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


commit bc4b358b477df0cc113b14af02b5f89d0b1b38e5
Author: Aldrin Piri 
Date:   2016-10-27T19:12:39Z

NIFI-2954 - Treating bcprov and bcpkix dependencies as provided by nifi in 
lib and updating projects to include them as provided where needed.




> Bouncycastle dependencies are duplicated throughout NARs
> 
>
> Key: NIFI-2954
> URL: https://issues.apache.org/jira/browse/NIFI-2954
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>
> I was working with some of the NiFi dependencies for incorporation with/use 
> by MiNiFi and saw that several libraries were duplicated throughout all NARs.
> Of note were the bouncycastle dependencies which, together, are ~4MB in size.
> {code}
> # apiri @ computer in /usr/local/opt/nifi/libexec [17:20:23]
> $ find {lib,work} -type f -name '*bcprov-jdk15on*' | wc -l
>   54
> # apiri @ computer in /usr/local/opt/nifi/libexec [17:20:28]
> $ find {lib,work} -type f -name '*bcpkix*' | wc -l
>   53
> # apiri @ computer in /usr/local/opt/nifi/libexec [17:20:33]
> $ ls -lash 
> work/nar/framework/nifi-framework-nar-1.0.0.nar-unpacked/META-INF/bundled-dependencies/bcprov-jdk15on-1.54.jar
> 3.2M -rw-r--r-- 1 apiri admin 3.2M Oct  4 12:24 
> work/nar/framework/nifi-framework-nar-1.0.0.nar-unpacked/META-INF/bundled-dependencies/bcprov-jdk15on-1.54.jar
> # apiri @ computer in /usr/local/opt/nifi/libexec [17:20:39]
> $ ls -lash 
> work/nar/framework/nifi-framework-nar-1.0.0.nar-unpacked/META-INF/bundled-dependencies/bcpkix-jdk15on-1.54.jar
> 660K -rw-r--r-- 1 apiri admin 658K Oct  4 12:24 
> work/nar/framework/nifi-framework-nar-1.0.0.nar-unpacked/META-INF/bundled-dependencies/bcpkix-jdk15on-1.54.jar
> {code}



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

[jira] [Commented] (NIFI-2959) TLS Toolkit should provide the correct DN to authorizers.xml for the Initial Admin Identity

[Bryan Rosander (JIRA)]

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

Bryan Rosander commented on NIFI-2959:
--

Client mode does log DN but could be clearer about it ex:
{code}
2016-10-27 15:12:10,319 INFO [main] 
o.a.n.t.t.s.c.TlsCertificateSigningRequestPerformer Got certificate with dn 
CN=localhost, OU=NIFI
{code}

Standalone needs similar logging and they both need to be clearer about what 
should be copied to authorizers.xml

> TLS Toolkit should provide the correct DN to authorizers.xml for the Initial 
> Admin Identity
> ---
>
> Key: NIFI-2959
> URL: https://issues.apache.org/jira/browse/NIFI-2959
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>  Labels: security, tls-toolkit
>
> Users frequently experience a user permission error when trying to access a 
> secured instance of NiFi after using the TLS toolkit to create a client 
> certificate because the whitespace formatting of the provided DN differs from 
> the resulting certificate subject. The toolkit should output a clear log line 
> with the exact string that should be copied to {{authorizers.xml}} *Initial 
> Admin Identity* when a client certificate is generated, and if a special flag 
> is invoked during the command line call, the provided {{authorizers.xml}} 
> should be updated directly. 



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

[jira] [Updated] (NIFI-2954) Bouncycastle dependencies are duplicated throughout NARs

[Aldrin Piri (JIRA)]

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

Aldrin Piri updated NIFI-2954:
--
Status: Patch Available  (was: In Progress)

> Bouncycastle dependencies are duplicated throughout NARs
> 
>
> Key: NIFI-2954
> URL: https://issues.apache.org/jira/browse/NIFI-2954
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>
> I was working with some of the NiFi dependencies for incorporation with/use 
> by MiNiFi and saw that several libraries were duplicated throughout all NARs.
> Of note were the bouncycastle dependencies which, together, are ~4MB in size.
> {code}
> # apiri @ computer in /usr/local/opt/nifi/libexec [17:20:23]
> $ find {lib,work} -type f -name '*bcprov-jdk15on*' | wc -l
>   54
> # apiri @ computer in /usr/local/opt/nifi/libexec [17:20:28]
> $ find {lib,work} -type f -name '*bcpkix*' | wc -l
>   53
> # apiri @ computer in /usr/local/opt/nifi/libexec [17:20:33]
> $ ls -lash 
> work/nar/framework/nifi-framework-nar-1.0.0.nar-unpacked/META-INF/bundled-dependencies/bcprov-jdk15on-1.54.jar
> 3.2M -rw-r--r-- 1 apiri admin 3.2M Oct  4 12:24 
> work/nar/framework/nifi-framework-nar-1.0.0.nar-unpacked/META-INF/bundled-dependencies/bcprov-jdk15on-1.54.jar
> # apiri @ computer in /usr/local/opt/nifi/libexec [17:20:39]
> $ ls -lash 
> work/nar/framework/nifi-framework-nar-1.0.0.nar-unpacked/META-INF/bundled-dependencies/bcpkix-jdk15on-1.54.jar
> 660K -rw-r--r-- 1 apiri admin 658K Oct  4 12:24 
> work/nar/framework/nifi-framework-nar-1.0.0.nar-unpacked/META-INF/bundled-dependencies/bcpkix-jdk15on-1.54.jar
> {code}



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

[jira] [Commented] (NIFI-2943) tls-toolkit pkcs12 truststore 0 entries

[Bryan Rosander (JIRA)]

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

Bryan Rosander commented on NIFI-2943:
--

Agree, this more in the know/document category, figured it made sense to put it 
in the jira in hopes it might help someone someday :)

> tls-toolkit pkcs12 truststore 0 entries
> ---
>
> Key: NIFI-2943
> URL: https://issues.apache.org/jira/browse/NIFI-2943
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>Priority: Minor
>
> When pkcs12 is used by the tls-toolkit, the resulting truststore has no 
> entries when inspected by the keytool and the tls-toolkit certificate 
> authority certificate is not trusted by NiFi.
> This seems to be due to the Java pkcs12 provider not supporting certificate 
> entries:
> http://stackoverflow.com/questions/3614239/pkcs12-java-keystore-from-ca-and-user-certificate-in-java#answer-3614405
> The Bouncy Castle provider does seem to support certificates but we may not 
> want to explicitly use that provider from within NiFi.



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

[jira] [Updated] (NIFI-2915) Replace incorrect images in User Guide

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2915:
-
Summary: Replace incorrect images in User Guide  (was: View Details Icon in 
User Guide is incorrect)

> Replace incorrect images in User Guide
> --
>
> Key: NIFI-2915
> URL: https://issues.apache.org/jira/browse/NIFI-2915
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Trivial
>
> In the User Guide "Adding Controller Services for Dataflows" section, in Step 
> #5 the View Details icon image referenced is incorrect (iconViewDetails.png). 
>  It should reference iconDetails.png.



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

[jira] [Updated] (NIFI-2915) Replace incorrect images in User Guide

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2915:
-
Description: 
In the User Guide "Adding Controller Services for Dataflows" section, in Step 
#5 the View Details icon image referenced is incorrect (iconViewDetails.png).  
It should reference iconDetails.png.

Also, in the same doc in "Anatomy of a Remote Process Group" the iconSecure.png 
still references the old UI.

  was:In the User Guide "Adding Controller Services for Dataflows" section, in 
Step #5 the View Details icon image referenced is incorrect 
(iconViewDetails.png).  It should reference iconDetails.png.


> Replace incorrect images in User Guide
> --
>
> Key: NIFI-2915
> URL: https://issues.apache.org/jira/browse/NIFI-2915
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Trivial
>
> In the User Guide "Adding Controller Services for Dataflows" section, in Step 
> #5 the View Details icon image referenced is incorrect (iconViewDetails.png). 
>  It should reference iconDetails.png.
> Also, in the same doc in "Anatomy of a Remote Process Group" the 
> iconSecure.png still references the old UI.



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

[jira] [Created] (NIFI-2960) Remove unused documentation images

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2960:


 Summary: Remove unused documentation images
 Key: NIFI-2960
 URL: https://issues.apache.org/jira/browse/NIFI-2960
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Documentation & Website
Affects Versions: 1.0.0
Reporter: Andrew Lim
Priority: Trivial


There are images that are no longer used in the 1.0 documentation as they 
reference the 0.x UI:

anonymous-access.png
controller-services-edit-buttons2.png
iconFlowHistory.png
iconInputPortSmall.png
iconOutputPortSmall.png
iconSettings.png
iconSummary.png
iconUsers.png
iconViewDetails.png
nifi-arch-cluster.png
nifi-arch.png
reporting-tasks-edit-buttons.png
request-access.png
status-bar.png



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

[GitHub] nifi issue #583: NIFI-2115 Detailed Version Info for About Box

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/583
  
Hey @jvwing... I had a chance to check out the update. Everything looks 
good but I do have one other comment that I probably should have noticed 
before. Given the build details ultimately come from `nifi.properties` I don't 
think we can rely on their presence. Often times, folks upgrade by retaining 
their consisting `conf` directory so we typically try to ensure things still 
work when the properties do not exist. In the System Diagnostics, it probably 
makes sense to simply populate the fields with a message indicating that the 
value isn't set. Additionally, you can style the elements with `unset`. In the 
About dialog is probably makes sense to just not render anything under the 
version. Currently, it just says 'Tagged'.

Thoughts?



---
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-2115) Enhanced About Box Version Information

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2115:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/583
  
Hey @jvwing... I had a chance to check out the update. Everything looks 
good but I do have one other comment that I probably should have noticed 
before. Given the build details ultimately come from `nifi.properties` I don't 
think we can rely on their presence. Often times, folks upgrade by retaining 
their consisting `conf` directory so we typically try to ensure things still 
work when the properties do not exist. In the System Diagnostics, it probably 
makes sense to simply populate the fields with a message indicating that the 
value isn't set. Additionally, you can style the elements with `unset`. In the 
About dialog is probably makes sense to just not render anything under the 
version. Currently, it just says 'Tagged'.

Thoughts?



> Enhanced About Box Version Information
> --
>
> Key: NIFI-2115
> URL: https://issues.apache.org/jira/browse/NIFI-2115
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI, Tools and Build
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Attachments: screenshot-1-of-4-about-expands.png, 
> screenshot-2-of-4-git-build.png, screenshot-3-of-4-release-build.png, 
> screenshot-4-of-4-source-build.png
>
>
> The UI's About dialog and underlying API provide the version of NiFi, like 
> "0.7.0-SNAPSHOT".  For many bug reports and troubleshooting requests, this is 
> not very precise, especially around rapidly changing code or 
> platform-dependent behavior.  It would help if NiFi captured and displayed 
> additional information:  
> * NiFi build commit hash
> * NiFi build branch
> * NiFi build date/time
> * Java Version
> * Java Vendor (Oracle, OpenJDK)
> * OS
> Then a simple copy/paste from the about box would provide very specific 
> information about a particular NiFi installation and which code it was 
> derived from.



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

[jira] [Commented] (NIFI-2943) tls-toolkit pkcs12 truststore 0 entries

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2943:
--

GitHub user brosander opened a pull request:

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

NIFI-2943 - pkcs12 keystore improvements

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [x] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [x] Is your initial contribution a single, squashed commit?

### For code changes:
- [x] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?
- [x] N/A - If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [x] N/A - If applicable, have you updated the LICENSE file, including the 
main LICENSE file under nifi-assembly?
- [x] N/A - If applicable, have you updated the NOTICE file, including the 
main NOTICE file found under nifi-assembly?
- [x] N/A - If adding new Properties, have you added .displayName in 
addition to .name (programmatic access) for each of the new properties?

### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.

1. loading pkcs12 keystores with bouncy castle everywhere
2. tls-toolkit client using jks truststore when keystore type is specified 
differently
3. tests

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

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

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

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


commit ee6d791a87a875319e748a8cab05a0961d1ff561
Author: Bryan Rosander 
Date:   2016-10-27T14:27:06Z

NIFI-2943 - pkcs12 keystore improvements

1. loading pkcs12 keystores with bouncy castle everywhere
2. tls-toolkit client using jks truststore when keystore type is specified 
differently
3. tests




> tls-toolkit pkcs12 truststore 0 entries
> ---
>
> Key: NIFI-2943
> URL: https://issues.apache.org/jira/browse/NIFI-2943
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>Priority: Minor
>
> When pkcs12 is used by the tls-toolkit, the resulting truststore has no 
> entries when inspected by the keytool and the tls-toolkit certificate 
> authority certificate is not trusted by NiFi.
> This seems to be due to the Java pkcs12 provider not supporting certificate 
> entries:
> http://stackoverflow.com/questions/3614239/pkcs12-java-keystore-from-ca-and-user-certificate-in-java#answer-3614405
> The Bouncy Castle provider does seem to support certificates but we may not 
> want to explicitly use that provider from within NiFi.



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

[GitHub] nifi pull request #1165: NIFI-2943 - pkcs12 keystore improvements

[brosander]

GitHub user brosander opened a pull request:

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

NIFI-2943 - pkcs12 keystore improvements

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [x] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [x] Is your initial contribution a single, squashed commit?

### For code changes:
- [x] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?
- [x] N/A - If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [x] N/A - If applicable, have you updated the LICENSE file, including the 
main LICENSE file under nifi-assembly?
- [x] N/A - If applicable, have you updated the NOTICE file, including the 
main NOTICE file found under nifi-assembly?
- [x] N/A - If adding new Properties, have you added .displayName in 
addition to .name (programmatic access) for each of the new properties?

### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.

1. loading pkcs12 keystores with bouncy castle everywhere
2. tls-toolkit client using jks truststore when keystore type is specified 
differently
3. tests

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

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

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

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


commit ee6d791a87a875319e748a8cab05a0961d1ff561
Author: Bryan Rosander 
Date:   2016-10-27T14:27:06Z

NIFI-2943 - pkcs12 keystore improvements

1. loading pkcs12 keystores with bouncy castle everywhere
2. tls-toolkit client using jks truststore when keystore type is specified 
differently
3. tests




---
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 #1165: NIFI-2943 - pkcs12 keystore improvements

[ishiyayu]

Github user ishiyayu commented on the issue:

https://github.com/apache/nifi/pull/1165
  
2016/10/28 午前6:32 "Bryan Rosander" :

> Thank you for submitting a contribution to Apache NiFi.
>
> In order to streamline the review of the contribution we ask you
> to ensure the following steps have been taken:
> For all changes:
>
>-
>
>Is there a JIRA ticket associated with this PR? Is it referenced
>in the commit message?
>-
>
>Does your PR title start with NIFI- where  is the JIRA number
>you are trying to resolve? Pay particular attention to the hyphen "-"
>character.
>-
>
>Has your PR been rebased against the latest commit within the target
>branch (typically master)?
>-
>
>Is your initial contribution a single, squashed commit?
>
> For code changes:
>
>- Have you ensured that the full suite of tests is executed via mvn
>-Pcontrib-check clean install at the root nifi folder?
>- Have you written or updated unit tests to verify your changes?
>- N/A - If adding new dependencies to the code, are these dependencies
>licensed in a way that is compatible for inclusion under ASF 2.0
>?
>- N/A - If applicable, have you updated the LICENSE file, including
>the main LICENSE file under nifi-assembly?
>- N/A - If applicable, have you updated the NOTICE file, including the
>main NOTICE file found under nifi-assembly?
>- N/A - If adding new Properties, have you added .displayName in
>addition to .name (programmatic access) for each of the new properties?
>
> For documentation related changes:
>
>- Have you ensured that format looks appropriate for the output in
>which it is rendered?
>
> Note:
>
> Please ensure that once the PR is submitted, you check travis-ci for build
> issues and submit an update to your PR as soon as possible.
>
>1. loading pkcs12 keystores with bouncy castle everywhere
>2. tls-toolkit client using jks truststore when keystore type is
>specified differently
>3. tests
>
> --
> You can view, comment on, or merge this pull request online at:
>
>   https://github.com/apache/nifi/pull/1165
> Commit Summary
>
>- NIFI-2943 - pkcs12 keystore improvements
>
> File Changes
>
>- *M* nifi-commons/nifi-security-utils/src/main/java/org/
>apache/nifi/security/util/CertificateUtils.java
> (7)
>- *A* nifi-commons/nifi-security-utils/src/main/java/org/
>apache/nifi/security/util/KeyStoreUtils.java
> (62)
>- *M* nifi-commons/nifi-security-utils/src/main/java/org/
>apache/nifi/security/util/SslContextFactory.java
> (8)
>- *M* nifi-commons/nifi-security-utils/src/test/groovy/org/
>apache/nifi/security/util/CertificateUtilsTest.groovy
> (4)
>- *A* nifi-commons/nifi-security-utils/src/test/java/org/
>apache/nifi/security/util/KeyStoreUtilsTest.java
> (139)
>- *M* nifi-commons/nifi-site-to-site-client/src/main/java/org/
>apache/nifi/remote/client/SiteToSiteClient.java
> (5)
>- *M* nifi-commons/nifi-socket-utils/src/main/java/org/
>apache/nifi/io/socket/SSLContextFactory.java
> (5)
>- *M* nifi-docs/src/main/asciidoc/administration-guide.adoc
> (4)
>- *M* nifi-nar-bundles/nifi-framework-bundle/nifi-
>framework/nifi-security/src/main/java/org/apache/nifi/
>framework/security/util/SslContextFactory.java
> (7)
>- *M* nifi-nar-bundles/nifi-framework-bundle/nifi-
>framework/nifi-web/nifi-jetty/src/main/java/org/apache/nifi/
>web/server/JettyServer.java
> (19)
>- *M* nifi-nar-bundles/nifi-framework-bundle/nifi-
>framework/nifi-web/nifi-jetty/src/test/java/org/apache/nifi/
>web/server/JettyServerTest.java
> (62)
>- *M* nifi-nar-bundles/nifi-framework-bundle/nifi-
>framework/nifi-web/nifi-web-security/src/main/java/org/
>apache/nifi/web/security/x509/ocsp/OcspCertificate

[jira] [Created] (NIFI-2961) Create EncryptAttribute processor

[Andy LoPresto (JIRA)]

Andy LoPresto created NIFI-2961:
---

 Summary: Create EncryptAttribute processor
 Key: NIFI-2961
 URL: https://issues.apache.org/jira/browse/NIFI-2961
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Extensions
Affects Versions: 1.0.0
Reporter: Andy LoPresto


Similar to {{EncryptContent}}, the {{EncryptAttribute}} processor would allow 
individual (and multiple) flowfile attributes to be encrypted (either in-place 
or to a new attribute key) with various encryption algorithms (AES, RSA, PBE, 
and PGP). 

Specific compatibility with the {{OpenSSL EVP_BytesToKey}}, {{PBKDF2}}, 
{{scrypt}}, and {{bcrypt}} key derivation functions should be included. 

If [dangerous processor 
annotations|https://cwiki.apache.org/confluence/display/NIFI/Security+Feature+Roadmap]
 are introduced, this processor should be marked as such and the corresponding 
attribute protection (i.e. provenance before/after, etc.) should be applied. 

Originally requested in this [Stack Overflow 
question|https://stackoverflow.com/questions/40294945/nifi-encrypt-json].  



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

[jira] [Updated] (NIFI-2961) Create EncryptAttribute processor

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2961:

Description: 
Similar to {{EncryptContent}}, the {{EncryptAttribute}} processor would allow 
individual (and multiple) flowfile attributes to be encrypted (either in-place 
or to a new attribute key) with various encryption algorithms (AES, RSA, PBE, 
and PGP). 

Specific compatibility with the {{OpenSSL EVP_BytesToKey}}, {{PBKDF2}}, 
{{scrypt}}, and {{bcrypt}} key derivation functions should be included. 

The processor should provide the boolean option to encrypt or decrypt (only one 
operation per instance of the processor). The processor should also allow 
Base64 encoding (aka ASCII armor) for the encrypted attributes to prevent byte 
escaping/data loss. 

If [dangerous processor 
annotations|https://cwiki.apache.org/confluence/display/NIFI/Security+Feature+Roadmap]
 are introduced, this processor should be marked as such and the corresponding 
attribute protection (i.e. provenance before/after, etc.) should be applied. 

Originally requested in this [Stack Overflow 
question|https://stackoverflow.com/questions/40294945/nifi-encrypt-json].  

  was:
Similar to {{EncryptContent}}, the {{EncryptAttribute}} processor would allow 
individual (and multiple) flowfile attributes to be encrypted (either in-place 
or to a new attribute key) with various encryption algorithms (AES, RSA, PBE, 
and PGP). 

Specific compatibility with the {{OpenSSL EVP_BytesToKey}}, {{PBKDF2}}, 
{{scrypt}}, and {{bcrypt}} key derivation functions should be included. 

If [dangerous processor 
annotations|https://cwiki.apache.org/confluence/display/NIFI/Security+Feature+Roadmap]
 are introduced, this processor should be marked as such and the corresponding 
attribute protection (i.e. provenance before/after, etc.) should be applied. 

Originally requested in this [Stack Overflow 
question|https://stackoverflow.com/questions/40294945/nifi-encrypt-json].  


> Create EncryptAttribute processor
> -
>
> Key: NIFI-2961
> URL: https://issues.apache.org/jira/browse/NIFI-2961
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>  Labels: attributes, encryption, security
>
> Similar to {{EncryptContent}}, the {{EncryptAttribute}} processor would allow 
> individual (and multiple) flowfile attributes to be encrypted (either 
> in-place or to a new attribute key) with various encryption algorithms (AES, 
> RSA, PBE, and PGP). 
> Specific compatibility with the {{OpenSSL EVP_BytesToKey}}, {{PBKDF2}}, 
> {{scrypt}}, and {{bcrypt}} key derivation functions should be included. 
> The processor should provide the boolean option to encrypt or decrypt (only 
> one operation per instance of the processor). The processor should also allow 
> Base64 encoding (aka ASCII armor) for the encrypted attributes to prevent 
> byte escaping/data loss. 
> If [dangerous processor 
> annotations|https://cwiki.apache.org/confluence/display/NIFI/Security+Feature+Roadmap]
>  are introduced, this processor should be marked as such and the 
> corresponding attribute protection (i.e. provenance before/after, etc.) 
> should be applied. 
> Originally requested in this [Stack Overflow 
> question|https://stackoverflow.com/questions/40294945/nifi-encrypt-json].  



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

[GitHub] nifi issue #1136: [NIFI-2900] fixes timestamps to be ISO 8601 compliant, as ...

[mike42]

Github user mike42 commented on the issue:

https://github.com/apache/nifi/pull/1136
  
@mcgilman- I would also like to see the REST API change in the next major 
release. Date localisation should be moved to the front-end, as only the 
browser knows the user's locale and timezone.

Noting your comments above, would you be open to reviewing a pull request 
which corrects the API to use ISO timestamps, and also introduces `moment.js` 
in the front end to display localised timestamps?


---
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 #1047: [NIFI-2812] Fix creating NiFi RPM

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1047
  
@fidget83 - thanks for the contribution.

@joaohf - muito obrigadopelo feedback. :wink: 

Notes: created RPM. did diff between LGTM, will merge later today.


---
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-2900) DateTime API Endpoints don't respect RFC 3339

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2900:
--

Github user mike42 commented on the issue:

https://github.com/apache/nifi/pull/1136
  
@mcgilman- I would also like to see the REST API change in the next major 
release. Date localisation should be moved to the front-end, as only the 
browser knows the user's locale and timezone.

Noting your comments above, would you be open to reviewing a pull request 
which corrects the API to use ISO timestamps, and also introduces `moment.js` 
in the front end to display localised timestamps?


> DateTime API Endpoints don't respect RFC 3339
> -
>
> Key: NIFI-2900
> URL: https://issues.apache.org/jira/browse/NIFI-2900
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Stephane Maarek
>
> Hi,
> the endpoint /flow/process-group/id is supposed to return lastRefreshed as 
> part of ProcessGroupFlowDTO as a DateTime, as indicated here:
> lastRefreshed string (date-time)  optionalThe time the flow for 
> the process group was last refreshed.
> as it currently stands, what I am getting doesn't look like a timestamp:
> "lastRefreshed":"14:02:46 AEDT"
> I'm not sure how much of the overall API is affected
> Edit:
> Actually, it seems every date a "date-time" is created we expect the format 
> "HH:mm:ss z".
> As per the OpenAPI specs, if a field is annotated "date-time", it should 
> respect the RFC 3339 convention 
> (https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types).
>  



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

[jira] [Commented] (NIFI-2812) Error when start nifi after installation from rpm

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2812:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1047
  
@fidget83 - thanks for the contribution.

@joaohf - muito obrigadopelo feedback. :wink: 

Notes: created RPM. did diff between LGTM, will merge later today.


> Error when start nifi after installation from rpm
> -
>
> Key: NIFI-2812
> URL: https://issues.apache.org/jira/browse/NIFI-2812
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.1.0
> Environment: Centos 7
>Reporter: Artem Yermakov
>Priority: Critical
> Fix For: 1.1.0
>
>
> 1. Build nifi-assembly with profile rpm (mvn clean install -DskipTests -Prpm)
> 2. Install created rpm on server
> 3. Run NiFi
> Error:
> [username@srv-2162219 bin]# ./nifi.sh start
> ./nifi.sh: line 24: ./nifi-env.sh: No such file or directory
> If copy this file from build manually, we got the next error in nifi-app.log:
> 2016-09-23 11:42:57,482 INFO [main] o.a.nifi.properties.NiFiPropertiesLoader 
> Loaded 117 properties from 
> /opt/nifi/nifi-1.1.0-SNAPSHOT/./conf/nifi.properties
> 2016-09-23 11:42:57,502 ERROR [main] org.apache.nifi.NiFi Failure to launch 
> NiFi due to java.lang.NoClassDefFoundError: 
> org/apache/commons/lang3/StringUtils
> java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils
>   at 
> org.apache.nifi.properties.ProtectedNiFiProperties.getProtectedPropertyKeys(ProtectedNiFiProperties.java:222)
>  ~[nifi-properties-loader-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
>   at 
> org.apache.nifi.properties.ProtectedNiFiProperties.(ProtectedNiFiProperties.java:66)
>  ~[nifi-properties-loader-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
>   at 
> org.apache.nifi.properties.ProtectedNiFiProperties.(ProtectedNiFiProperties.java:75)
>  ~[nifi-properties-loader-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]



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

[jira] [Commented] (NIFI-2812) Error when start nifi after installation from rpm

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2812:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1047
  
Notes: 
* created RPM. 
* did diff between RPM with RPM profile and TGZ without the RPM profile
* installed from the RPM. started NiFi. Connected to it.

LGTM, will merge later today.


> Error when start nifi after installation from rpm
> -
>
> Key: NIFI-2812
> URL: https://issues.apache.org/jira/browse/NIFI-2812
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.1.0
> Environment: Centos 7
>Reporter: Artem Yermakov
>Priority: Critical
> Fix For: 1.1.0
>
>
> 1. Build nifi-assembly with profile rpm (mvn clean install -DskipTests -Prpm)
> 2. Install created rpm on server
> 3. Run NiFi
> Error:
> [username@srv-2162219 bin]# ./nifi.sh start
> ./nifi.sh: line 24: ./nifi-env.sh: No such file or directory
> If copy this file from build manually, we got the next error in nifi-app.log:
> 2016-09-23 11:42:57,482 INFO [main] o.a.nifi.properties.NiFiPropertiesLoader 
> Loaded 117 properties from 
> /opt/nifi/nifi-1.1.0-SNAPSHOT/./conf/nifi.properties
> 2016-09-23 11:42:57,502 ERROR [main] org.apache.nifi.NiFi Failure to launch 
> NiFi due to java.lang.NoClassDefFoundError: 
> org/apache/commons/lang3/StringUtils
> java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils
>   at 
> org.apache.nifi.properties.ProtectedNiFiProperties.getProtectedPropertyKeys(ProtectedNiFiProperties.java:222)
>  ~[nifi-properties-loader-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
>   at 
> org.apache.nifi.properties.ProtectedNiFiProperties.(ProtectedNiFiProperties.java:66)
>  ~[nifi-properties-loader-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
>   at 
> org.apache.nifi.properties.ProtectedNiFiProperties.(ProtectedNiFiProperties.java:75)
>  ~[nifi-properties-loader-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]



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

[GitHub] nifi issue #1047: [NIFI-2812] Fix creating NiFi RPM

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1047
  
Notes: 
* created RPM. 
* did diff between RPM with RPM profile and TGZ without the RPM profile
* installed from the RPM. started NiFi. Connected to it.

LGTM, will merge later today.


---
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-2962) Default conf/logback comment for maxHistory is misleading and incorrect

[Joseph Witt (JIRA)]

Joseph Witt created NIFI-2962:
-

 Summary: Default conf/logback comment for maxHistory is misleading 
and incorrect
 Key: NIFI-2962
 URL: https://issues.apache.org/jira/browse/NIFI-2962
 Project: Apache NiFi
  Issue Type: Bug
  Components: Tools and Build
Reporter: Joseph Witt
Assignee: Joseph Witt
Priority: Minor






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

[jira] [Updated] (NIFI-2962) Default conf/logback comment for maxHistory is misleading and incorrect

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2962:
--
Description: 
Joe Gresock in dev list note on Oct 27, 2016

Ahh, that would explain it!  Maybe we can change the comment in logback.xml

above this element so it's more clear:


30

> Default conf/logback comment for maxHistory is misleading and incorrect
> ---
>
> Key: NIFI-2962
> URL: https://issues.apache.org/jira/browse/NIFI-2962
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Reporter: Joseph Witt
>Assignee: Joseph Witt
>Priority: Minor
>
> Joe Gresock in dev list note on Oct 27, 2016
> Ahh, that would explain it!  Maybe we can change the comment in logback.xml
> 
> above this element so it's more clear:
> 
> 30



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

[GitHub] nifi issue #587: NIFI-2116 Initial Draft for Spanish readme.md

[chagara]

Github user chagara commented on the issue:

https://github.com/apache/nifi/pull/587
  
I'll work on this to update it to the latest.


---
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-2116) Translate Documentation Into Spanish

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2116:
--

Github user chagara commented on the issue:

https://github.com/apache/nifi/pull/587
  
I'll work on this to update it to the latest.


> Translate Documentation Into Spanish
> 
>
> Key: NIFI-2116
> URL: https://issues.apache.org/jira/browse/NIFI-2116
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Documentation & Website
>Reporter: Chagara
>Assignee: Chagara
>Priority: Minor
>
> Create documentation in Spanish to expand NIFI reach.



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

[jira] [Commented] (NIFI-2936) TestExecuteProcess errors in Travis CI environment

[Koji Kawamura (JIRA)]

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

Koji Kawamura commented on NIFI-2936:
-

The root cause of this test failure was the difference of native 
UnixProcess.init method implementation.  This test case uses "cd 
does-not-exist" command to test ExecuteProcess behavior in failure scenario. On 
some environment (e.g. OS X), the command is executed and error stream can be 
read, but on others (e.g. CentOS, Travis CI) the command fails immediately with 
an IOException.

I modified the test so that it can pass on both environments. PR-1162 Travis CI 
build has succeeded.

> TestExecuteProcess errors in Travis CI environment
> --
>
> Key: NIFI-2936
> URL: https://issues.apache.org/jira/browse/NIFI-2936
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Reporter: Aldrin Piri
>Assignee: Koji Kawamura
>Priority: Blocker
> Fix For: 1.1.0
>
>
> The introduction of redirecting error stream and the accompanying tests for 
> TestExecuteProcess [1] are causing Travis to have issues with the build 
> fairly consistently starting with the initial travis build #4109 [2]. 
> [1] 
> https://github.com/apache/nifi/commit/27dba60f27579ca9f33aa1afbf4bb46182d57df4
> [2] https://travis-ci.org/apache/nifi/builds/168776478



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