date:20160804

2016-08-04 Thread ASF subversion and git services (JIRA)


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

ASF GitHub Bot commented on NIFI-2472:
--

Github user asfgit closed the pull request at:

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


> Copy and Pasting groups of components repositions them erratically
> --
>
> Key: NIFI-2472
> URL: https://issues.apache.org/jira/browse/NIFI-2472
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0, 1.0.0-Beta
>
> Attachments: Screen Shot 2016-08-03 at 3.48.42 PM.png, Screen Shot 
> 2016-08-03 at 3.49.01 PM.png
>
>
> Currently when you copy and paste a group of components the components don't 
> paste where you would expect. One thought is that some components in the 
> copy/paste are having the 0.x template scaling logic applied.
> I will attach screenshots to demonstrate.



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

[jira] [Commented] (NIFI-2472) Copy and Pasting groups of components repositions them erratically


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

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

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

NIFI-2472: Normalize coordinates for all components in a snippet, not just 
processors

This closes #786

Signed-off-by: jpercivall 


> Copy and Pasting groups of components repositions them erratically
> --
>
> Key: NIFI-2472
> URL: https://issues.apache.org/jira/browse/NIFI-2472
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0, 1.0.0-Beta
>
> Attachments: Screen Shot 2016-08-03 at 3.48.42 PM.png, Screen Shot 
> 2016-08-03 at 3.49.01 PM.png
>
>
> Currently when you copy and paste a group of components the components don't 
> paste where you would expect. One thought is that some components in the 
> copy/paste are having the 0.x template scaling logic applied.
> I will attach screenshots to demonstrate.



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

[jira] [Updated] (NIFI-2472) Copy and Pasting groups of components repositions them erratically


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

Joseph Percivall updated NIFI-2472:
---
   Resolution: Fixed
Fix Version/s: 1.0.0-Beta
   Status: Resolved  (was: Patch Available)

> Copy and Pasting groups of components repositions them erratically
> --
>
> Key: NIFI-2472
> URL: https://issues.apache.org/jira/browse/NIFI-2472
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0, 1.0.0-Beta
>
> Attachments: Screen Shot 2016-08-03 at 3.48.42 PM.png, Screen Shot 
> 2016-08-03 at 3.49.01 PM.png
>
>
> Currently when you copy and paste a group of components the components don't 
> paste where you would expect. One thought is that some components in the 
> copy/paste are having the 0.x template scaling logic applied.
> I will attach screenshots to demonstrate.



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

[GitHub] nifi pull request #786: NIFI-2472: Normalize coordinates for all components ...

Github user asfgit closed the pull request at:

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


---
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-2472) Copy and Pasting groups of components repositions them erratically


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

ASF GitHub Bot commented on NIFI-2472:
--

Github user JPercivall commented on the issue:

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

Visually verified code and did a contrib check build rebased to latest 
master. In a 3 node cluster and standalone instance verified that each 
component position in a snippet is normalized when used. Thanks @markap14, I 
will merge it in.


> Copy and Pasting groups of components repositions them erratically
> --
>
> Key: NIFI-2472
> URL: https://issues.apache.org/jira/browse/NIFI-2472
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
> Attachments: Screen Shot 2016-08-03 at 3.48.42 PM.png, Screen Shot 
> 2016-08-03 at 3.49.01 PM.png
>
>
> Currently when you copy and paste a group of components the components don't 
> paste where you would expect. One thought is that some components in the 
> copy/paste are having the 0.x template scaling logic applied.
> I will attach screenshots to demonstrate.



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

[GitHub] nifi issue #786: NIFI-2472: Normalize coordinates for all components in a sn...

2016-08-04 Thread JPercivall

Github user JPercivall commented on the issue:

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

Visually verified code and did a contrib check build rebased to latest 
master. In a 3 node cluster and standalone instance verified that each 
component position in a snippet is normalized when used. Thanks @markap14, I 
will merge it in.


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

[jira] [Commented] (NIFI-2472) Copy and Pasting groups of components repositions them erratically


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

ASF GitHub Bot commented on NIFI-2472:
--

Github user JPercivall commented on the issue:

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


> Copy and Pasting groups of components repositions them erratically
> --
>
> Key: NIFI-2472
> URL: https://issues.apache.org/jira/browse/NIFI-2472
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
> Attachments: Screen Shot 2016-08-03 at 3.48.42 PM.png, Screen Shot 
> 2016-08-03 at 3.49.01 PM.png
>
>
> Currently when you copy and paste a group of components the components don't 
> paste where you would expect. One thought is that some components in the 
> copy/paste are having the 0.x template scaling logic applied.
> I will attach screenshots to demonstrate.



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

[GitHub] nifi issue #786: NIFI-2472: Normalize coordinates for all components in a sn...

2016-08-04 Thread JPercivall

Github user JPercivall commented on the issue:

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


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

[jira] [Resolved] (NIFI-2486) Bulletin board needs to take into account component authorization


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

Joseph Percivall resolved NIFI-2486.

   Resolution: Fixed
Fix Version/s: 1.0.0-Beta

> Bulletin board needs to take into account component authorization
> -
>
> Key: NIFI-2486
> URL: https://issues.apache.org/jira/browse/NIFI-2486
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0, 1.0.0-Beta
>
>
> Currently no authorization is being done on bulletins and users could see 
> bulletins for components they don't have access to. Users should only be able 
> to see bulletins for the components they have "View" access for.



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

[GitHub] nifi pull request #792: Authorizing each bulletin returned through the bulle...

2016-08-04 Thread ASF subversion and git services (JIRA)

Github user asfgit closed the pull request at:

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


---
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-2486) Bulletin board needs to take into account component authorization


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

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

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

NIFI-2486: - Authorizing individual bulletins being returned through the 
bulletin board.

This closes #792

Signed-off-by: jpercivall 


> Bulletin board needs to take into account component authorization
> -
>
> Key: NIFI-2486
> URL: https://issues.apache.org/jira/browse/NIFI-2486
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Currently no authorization is being done on bulletins and users could see 
> bulletins for components they don't have access to. Users should only be able 
> to see bulletins for the components they have "View" access for.



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

[jira] [Commented] (NIFI-2486) Bulletin board needs to take into account component authorization


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

ASF GitHub Bot commented on NIFI-2486:
--

Github user asfgit closed the pull request at:

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


> Bulletin board needs to take into account component authorization
> -
>
> Key: NIFI-2486
> URL: https://issues.apache.org/jira/browse/NIFI-2486
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Currently no authorization is being done on bulletins and users could see 
> bulletins for components they don't have access to. Users should only be able 
> to see bulletins for the components they have "View" access for.



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

[jira] [Created] (NIFI-2489) GetFile inability to remove source file results in duplicate files (PutFile) and dataloss (Site2Site)

2016-08-04 Thread Kefevs Pirkibo (JIRA)

Kefevs Pirkibo created NIFI-2489:


 Summary: GetFile inability to remove source file results in 
duplicate files (PutFile) and dataloss (Site2Site)
 Key: NIFI-2489
 URL: https://issues.apache.org/jira/browse/NIFI-2489
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 0.6.1, 0.7.0
 Environment: Tested with CentOS 6 and 7.
Cifs-utils 4.8.1-20.el6 (CentOS 6) and Cifs-utils 6.2-7.el7 (CentOS 7)
Windows Server 2003 and Windows Server 2008 as CIFS sources.
Reporter: Kefevs Pirkibo


If GetFile is unable to remove the sourcefile from the windows cifs mapping 
(file is locked by another application) it also fails to remove other files 
from the same batch. (Unknown why). It then again sources those same file into 
NIFI on the next run, and fails to remove again. If the destination is PutFile 
with Conflict Resulution Strategy set to 'fail' the failure que builds up in a 
alarming rate. 

(0.6.1 and 0.7.0 on CentOS 6) if the destination is not a PutFile, but a 
Site2Site Output port the files can be dropped due to missing content.
Example log extract: http://pastebin.com/dJ8UibwR

Environment
Have replicated the GetFile behaviour on both CentOS 6 and 7 with CIFS mounts 
from a couple different Windows servers afterwards. In the original case 
GetFile ran on CRON to source files from the Windows server folders.  Timer 
driven GetFile is even worse since it builds up duplicates even faster. 

Trying to remove the file manually with rm in bash gives:
rm: cannot remove 'Filename': Text file busy

The most troubling here is that one locked file affects many others, depending 
on batch size. It is not only the locked file that is affected. The first 
occurrence of this with Site2Site dropped 9 files, out of 10, since the last of 
those 10 had a lock.

1) What should the expected behavior of GetFile in a edge case where it is 
unable to remove a source file? (revert?, remember in state file is read?)
2) Why does delete lock on one file prevent other files in the same batch to be 
deleted? (They are loaded into NIFI as flowfiles, but not deleted either.)



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

[jira] [Updated] (NIFI-2488) Flow history does not distinguish between "No value previously set" and unauthorized


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

Joseph Percivall updated NIFI-2488:
---
Attachment: Screen Shot 2016-08-04 at 5.39.26 PM.png

Attached is a screenshot of an example flow history where components are being 
changed that the user does not have access to "view"

> Flow history does not distinguish between "No value previously set" and 
> unauthorized
> 
>
> Key: NIFI-2488
> URL: https://issues.apache.org/jira/browse/NIFI-2488
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
> Fix For: 1.0.0
>
> Attachments: Screen Shot 2016-08-04 at 5.39.26 PM.png
>
>
> When viewing the flow history the events for which a user does not have 
> access to see will still populate the list but instead of seeing 
> "unauthorized" for values they cannot see, they see "No value previously set".
> Flow history should do a better job of distinguishing between the two cases.



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

[jira] [Created] (NIFI-2488) Flow history does not distinguish between "No value previously set" and unauthorized

Joseph Percivall created NIFI-2488:
--

 Summary: Flow history does not distinguish between "No value 
previously set" and unauthorized
 Key: NIFI-2488
 URL: https://issues.apache.org/jira/browse/NIFI-2488
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Joseph Percivall
 Fix For: 1.0.0


When viewing the flow history the events for which a user does not have access 
to see will still populate the list but instead of seeing "unauthorized" for 
values they cannot see, they see "No value previously set".

Flow history should do a better job of distinguishing between the two cases.



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

[jira] [Commented] (NIFI-2476) Further refine tls-toolkit based on feedback gathered during beta

2016-08-04 Thread Andy LoPresto (JIRA)


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

Andy LoPresto commented on NIFI-2476:
-

The {{nifi-toolkit-tls}} and {{nifi-toolkit-assembly}} {{pom.xml}} should have 
all dependency versions removed and put in the {{nifi/pom.xml}} file. 

> Further refine tls-toolkit based on feedback gathered during beta
> -
>
> Key: NIFI-2476
> URL: https://issues.apache.org/jira/browse/NIFI-2476
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> The basic functionality of generating keystores, truststores, 
> nifi.properties, and a configuration json is implemented.
> As people start using this tool to ease the tls setup process in NiFi, 
> shortcomings in the initial implementation will need to be addressed.



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

[jira] [Commented] (NIFI-2458) After canceling provenance query, cannot submit a new one


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

ASF GitHub Bot commented on NIFI-2458:
--

Github user asfgit closed the pull request at:

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


> After canceling provenance query, cannot submit a new one
> -
>
> Key: NIFI-2458
> URL: https://issues.apache.org/jira/browse/NIFI-2458
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Mark Payne
> Fix For: 1.0.0
>
>
> I right-clicked on a Processor and choose to view provenance events. I then 
> clicked Cancel on the progress bar dialog. I then clicked 'search' and added 
> a new parameter to the search (added a value for 'Relationship'). When I 
> click Search, I get an error message: Message body is malformed. Unable to 
> map into expected format.



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

[GitHub] nifi issue #773: Addressing issue when initial Provenance query is cancelled

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/773
  
+1 looks good, merged 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] [Updated] (NIFI-2458) After canceling provenance query, cannot submit a new one

2016-08-04 Thread ASF subversion and git services (JIRA)


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

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

> After canceling provenance query, cannot submit a new one
> -
>
> Key: NIFI-2458
> URL: https://issues.apache.org/jira/browse/NIFI-2458
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Bryan Bende
> Fix For: 1.0.0
>
>
> I right-clicked on a Processor and choose to view provenance events. I then 
> clicked Cancel on the progress bar dialog. I then clicked 'search' and added 
> a new parameter to the search (added a value for 'Relationship'). When I 
> click Search, I get an error message: Message body is malformed. Unable to 
> map into expected format.



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

[jira] [Commented] (NIFI-2458) After canceling provenance query, cannot submit a new one


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

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

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

NIFI-2458: - Fixing issue with timezone when the initial provenance result was 
cancelled.

This closes #773.

Signed-off-by: Bryan Bende 


> After canceling provenance query, cannot submit a new one
> -
>
> Key: NIFI-2458
> URL: https://issues.apache.org/jira/browse/NIFI-2458
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Mark Payne
> Fix For: 1.0.0
>
>
> I right-clicked on a Processor and choose to view provenance events. I then 
> clicked Cancel on the progress bar dialog. I then clicked 'search' and added 
> a new parameter to the search (added a value for 'Relationship'). When I 
> click Search, I get an error message: Message body is malformed. Unable to 
> map into expected format.



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

[GitHub] nifi pull request #773: Addressing issue when initial Provenance query is ca...

2016-08-04 Thread ASF subversion and git services (JIRA)

Github user asfgit closed the pull request at:

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


---
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-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory

2016-08-04 Thread Andy LoPresto (JIRA)


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

Andy LoPresto resolved NIFI-2485.
-
   Resolution: Fixed
Fix Version/s: 1.0.0

> Standalone tool sensible default for nifiProperties, httpsPort, 
> outputDirectory
> ---
>
> Key: NIFI-2485
> URL: https://issues.apache.org/jira/browse/NIFI-2485
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
> Fix For: 1.0.0
>
>
> Standalone tool has no default for:
> -f, --nifiPropertiesFile
> -p, --httpsPort
> Standalone tool default is unclear for:
> -o, --outputDirectory "." can display "current directory" or "../ directory>"



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

[jira] [Commented] (NIFI-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory


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

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

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

NIFI-2485 Added log messages and default values to standalone tool.

NIFI-2485 - Updating standalone success message (+2 squashed commits)
Squashed commits:
[68638bc] NIFI-2485 - Logging successful host processing in standalone
[9b41e0f] NIFI-2485 - Updating standalone defaults, adding logging

This closes #790.

Signed-off-by: Andy LoPresto 


> Standalone tool sensible default for nifiProperties, httpsPort, 
> outputDirectory
> ---
>
> Key: NIFI-2485
> URL: https://issues.apache.org/jira/browse/NIFI-2485
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Standalone tool has no default for:
> -f, --nifiPropertiesFile
> -p, --httpsPort
> Standalone tool default is unclear for:
> -o, --outputDirectory "." can display "current directory" or "../ directory>"



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

[jira] [Commented] (NIFI-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory

2016-08-04 Thread ASF subversion and git services (JIRA)


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

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

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

NIFI-2485 Added log messages and default values to standalone tool.

NIFI-2485 - Updating standalone success message (+2 squashed commits)
Squashed commits:
[68638bc] NIFI-2485 - Logging successful host processing in standalone
[9b41e0f] NIFI-2485 - Updating standalone defaults, adding logging

This closes #790.

Signed-off-by: Andy LoPresto 


> Standalone tool sensible default for nifiProperties, httpsPort, 
> outputDirectory
> ---
>
> Key: NIFI-2485
> URL: https://issues.apache.org/jira/browse/NIFI-2485
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Standalone tool has no default for:
> -f, --nifiPropertiesFile
> -p, --httpsPort
> Standalone tool default is unclear for:
> -o, --outputDirectory "." can display "current directory" or "../ directory>"



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

[jira] [Commented] (NIFI-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory

2016-08-04 Thread ASF subversion and git services (JIRA)


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

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

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

NIFI-2485 Added log messages and default values to standalone tool.

NIFI-2485 - Updating standalone success message (+2 squashed commits)
Squashed commits:
[68638bc] NIFI-2485 - Logging successful host processing in standalone
[9b41e0f] NIFI-2485 - Updating standalone defaults, adding logging

This closes #790.

Signed-off-by: Andy LoPresto 


> Standalone tool sensible default for nifiProperties, httpsPort, 
> outputDirectory
> ---
>
> Key: NIFI-2485
> URL: https://issues.apache.org/jira/browse/NIFI-2485
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Standalone tool has no default for:
> -f, --nifiPropertiesFile
> -p, --httpsPort
> Standalone tool default is unclear for:
> -o, --outputDirectory "." can display "current directory" or "../ directory>"



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

[GitHub] nifi pull request #790: NIFI-2485 - Updating standalone defaults, adding log...

Github user asfgit closed the pull request at:

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


---
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-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory


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

ASF GitHub Bot commented on NIFI-2485:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/790
  
Reviewed. Rebased, squashed, and merging. 


> Standalone tool sensible default for nifiProperties, httpsPort, 
> outputDirectory
> ---
>
> Key: NIFI-2485
> URL: https://issues.apache.org/jira/browse/NIFI-2485
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Standalone tool has no default for:
> -f, --nifiPropertiesFile
> -p, --httpsPort
> Standalone tool default is unclear for:
> -o, --outputDirectory "." can display "current directory" or "../ directory>"



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

[GitHub] nifi issue #773: Addressing issue when initial Provenance query is cancelled

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/773
  
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] [Updated] (NIFI-2471) Multiple Hadoop processors cannot point to different Hadoop clusters


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

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

Resolving since merged already.

> Multiple Hadoop processors cannot point to different Hadoop clusters
> 
>
> Key: NIFI-2471
> URL: https://issues.apache.org/jira/browse/NIFI-2471
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
>Priority: Minor
> Fix For: 1.0.0, 0.8.0
>
>
> Two GetHDFS processors, each with different Hadoop Configuration Resources, 
> will only operate with one Hadoop cluster.  In this specific case, both 
> Hadoop clusters had the same HDFS system name.  The AbstractHadoopProcessor 
> disables caching of Configuration and FileSystem objects but it doesn't 
> appear to be working.
> Also, if I configure a GetHDFS processor to point to one Hadoop cluster, but 
> the processor is invalid because the Directory doesn't exist, the processor 
> doesn't start (that's good).  But if I change the Hadoop Configuration 
> Resources to point to a different Hadoop cluster where the Directory does 
> exist, then GetHDFS continues to talk to the first Hadoop cluster.  It seems 
> like the Configuration and FileSystem objects don't reset when I change the 
> Hadoop Configuration Resources property.



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

[jira] [Commented] (NIFI-2483) Remove "Passthrough" relationship of GetHDFS

2016-08-04 Thread ASF subversion and git services (JIRA)


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

ASF GitHub Bot commented on NIFI-2483:
--

Github user asfgit closed the pull request at:

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


> Remove "Passthrough" relationship of GetHDFS
> 
>
> Key: NIFI-2483
> URL: https://issues.apache.org/jira/browse/NIFI-2483
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Currently, GetHDFS has a "passthrough" relationship that it uses to move any 
> FlowFiles from an input queue. This was done before the @InputRequirement 
> capability existed. This relationship needs to be removed and the 
> InputRequirement changed to INPUT_FORBIDDEN.



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

[jira] [Commented] (NIFI-2483) Remove "Passthrough" relationship of GetHDFS


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

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

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

NIFI-2483: Removed 'passthrough' relationship

This closes #789.

Signed-off-by: Bryan Bende 


> Remove "Passthrough" relationship of GetHDFS
> 
>
> Key: NIFI-2483
> URL: https://issues.apache.org/jira/browse/NIFI-2483
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Currently, GetHDFS has a "passthrough" relationship that it uses to move any 
> FlowFiles from an input queue. This was done before the @InputRequirement 
> capability existed. This relationship needs to be removed and the 
> InputRequirement changed to INPUT_FORBIDDEN.



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

[jira] [Updated] (NIFI-2483) Remove "Passthrough" relationship of GetHDFS


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

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

> Remove "Passthrough" relationship of GetHDFS
> 
>
> Key: NIFI-2483
> URL: https://issues.apache.org/jira/browse/NIFI-2483
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Currently, GetHDFS has a "passthrough" relationship that it uses to move any 
> FlowFiles from an input queue. This was done before the @InputRequirement 
> capability existed. This relationship needs to be removed and the 
> InputRequirement changed to INPUT_FORBIDDEN.



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

[jira] [Commented] (NIFI-2483) Remove "Passthrough" relationship of GetHDFS


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

ASF GitHub Bot commented on NIFI-2483:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/789
  
+1 looks good, will merge to master


> Remove "Passthrough" relationship of GetHDFS
> 
>
> Key: NIFI-2483
> URL: https://issues.apache.org/jira/browse/NIFI-2483
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Currently, GetHDFS has a "passthrough" relationship that it uses to move any 
> FlowFiles from an input queue. This was done before the @InputRequirement 
> capability existed. This relationship needs to be removed and the 
> InputRequirement changed to INPUT_FORBIDDEN.



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

[GitHub] nifi issue #789: NIFI-2483: Removed 'passthrough' relationship

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/789
  
+1 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-2483) Remove "Passthrough" relationship of GetHDFS


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

ASF GitHub Bot commented on NIFI-2483:
--

Github user bbende commented on the issue:

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


> Remove "Passthrough" relationship of GetHDFS
> 
>
> Key: NIFI-2483
> URL: https://issues.apache.org/jira/browse/NIFI-2483
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Currently, GetHDFS has a "passthrough" relationship that it uses to move any 
> FlowFiles from an input queue. This was done before the @InputRequirement 
> capability existed. This relationship needs to be removed and the 
> InputRequirement changed to INPUT_FORBIDDEN.



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

[jira] [Updated] (NIFI-2484) If a Processor's @OnScheduled method throws an Exception, its @OnStopped methods are not called


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

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

> If a Processor's @OnScheduled method throws an Exception, its @OnStopped 
> methods are not called
> ---
>
> Key: NIFI-2484
> URL: https://issues.apache.org/jira/browse/NIFI-2484
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> If a Processor has a method annotated with @OnScheduled and that method 
> throws an Exception, its @OnUnscheduled methods and then @OnStopped methods 
> should be called before calling its @OnScheduled methods again. Currently, 
> only the @OnUnscheduled methods are called.



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

[jira] [Commented] (NIFI-2484) If a Processor's @OnScheduled method throws an Exception, its @OnStopped methods are not called


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

ASF GitHub Bot commented on NIFI-2484:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/791
  
+1 merged to master


> If a Processor's @OnScheduled method throws an Exception, its @OnStopped 
> methods are not called
> ---
>
> Key: NIFI-2484
> URL: https://issues.apache.org/jira/browse/NIFI-2484
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> If a Processor has a method annotated with @OnScheduled and that method 
> throws an Exception, its @OnUnscheduled methods and then @OnStopped methods 
> should be called before calling its @OnScheduled methods again. Currently, 
> only the @OnUnscheduled methods are called.



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

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

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

Andrew Lim commented on NIFI-2477:
--

[~bryanrosan...@gmail.com], I've been working on docs for the 1.0.0 release and
reviewed your rough draft. Here is a version with my edits:

For the Admin guide (seems like it should go in the existing Security
Configuration section):

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:
1. -n (or --hostnames) a comma-separated list of hostnames that you’d like to
generate certificates for
2. -f (or --nifiPropertiesFile) a base nifi.properties file that the tool will
update for each host
3. -o (or --outputDirectory) the directory to use for the resulting Certificate
Authority files and NiFi configurations. A subdirectory will be made for each
host.
4. -p (or --httpsPort) the https port in nifi.properties and enable secure
site-to-site. This is optional and not required if you’ve provided a template
nifi.properties.

Client/Server:

Client/Server mode relies on a long-running Certificate Authority (CA) to issue
certificates. The CA can be stopped when you’re not bringing nodes online.

Server:
The CA server can be invoked by running “tls-toolkit server -h” which will
print the usage information.

The most common options to specify are:
1. -f (or --configJson) the location of the json config (written after first
run)
2. -F (or --useConfigJson) load all relevant configuration from the config json
(configJson is the only other argument necessary)
3. -t (or --token) the token used to prevent man in the middle attacks (this
should be a long, random value and needs to be known when invoking the client)
4. -D (or --dn) the DN for the CA

Client:
The client can be used to request new Certificates from the CA. The client
utility will generate a keypair andCertificate Signing Request (CSR) and send
the CSR to the Certificate Authority. The client can be invoked by running
“tls-toolkit.sh client -h” which will print the usage information.

The most common options to specify are:
1. -f (or --configJson) the json config file
2. -c (or --certificateAuthorityHostname) the hostname of the CA
3. -D (or --DN) the DN for the CSR (and Certificate)
4. -t (or --token) the token used to prevent man in the middle attacks (this
should be a long, random value and needs to be known when invoking the client)
5-T (or --keyStoreType) the type of keystore to create (specify jks for NiFi
nodes, leave default to create client cert)

After running the client you will have the CA’s certificate, a keystore, a
truststore, and a config.json with information about them as well as their
passwords.

If you leave -T (or --keyStoreType) as its default value, PKCS12 will be used
in order to make it easy to import into a browser for client certificates.

For Developer Guide:

NiFi Toolkit

tls-toolkit
-
The Client/Server mode of operation came about from the desire to automatically
generate required TLS configuration artifacts without needing to perform that
generation in a centralized place. This simplifies configuration in a
clustered environment. Since we don’t necessarily have a central place to run
the generation logic or a trusted Certificate Authority, a shared secret is
used to authenticate the clients and server to each other.

The tls-toolkit prevents man in the middle attacks using HMAC verification of
the public keys of the CA server and the CSR the client sends. A shared secret
(the token) is used as the HMAC key.

The basic process goes as follows:
1. The client generates a KeyPair.
2. The client generates a request json payload containing a CSR and an HMAC
with the token as the key and the CSR’s public key fingerprint as the data.
3. The client connects to the CA Hostname at the https port specified and
validates that the CN of the CA’s certificate matches the hostname (NOTE:
because we don’t trust the CA at this point, this adds NO security, it is

[jira] [Updated] (NIFI-2451) Need to update Security Configuration content in Admin & Dev Guides for 1.0 changes


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

Andrew Lim updated NIFI-2451:
-
Description: 
Will need to document changes in Admin Guide for:

NIFI-1831 for Encryption Configuration

  was:
Will need to document changes in Admin Guide for:

NIFI-1831 for Encryption Configuration
NIFI-2193 for tls-toolkit utility

Add toolkit section to Dev Guide for NIFI-2193


> Need to update Security Configuration content in Admin & Dev Guides for 1.0 
> changes
> ---
>
> Key: NIFI-2451
> URL: https://issues.apache.org/jira/browse/NIFI-2451
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> Will need to document changes in Admin Guide for:
> NIFI-1831 for Encryption Configuration



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

[jira] [Updated] (NIFI-2451) Need to update Encryption Configuration content in for 1.0 changes


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

Andrew Lim updated NIFI-2451:
-
Summary: Need to update Encryption Configuration content in for 1.0 changes 
 (was: Need to update Security Configuration content in Admin & Dev Guides for 
1.0 changes)

> Need to update Encryption Configuration content in for 1.0 changes
> --
>
> Key: NIFI-2451
> URL: https://issues.apache.org/jira/browse/NIFI-2451
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> Will need to document changes in Admin Guide for:
> NIFI-1831 for Encryption Configuration



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

[jira] [Commented] (NIFI-2451) Need to update Encryption Configuration content in for 1.0 changes


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

Andrew Lim commented on NIFI-2451:
--

Modified ticket to include NIFI-2193 tls-toolkit doc, but there is a separate 
JIRA for that (NIFI-2477)

> Need to update Encryption Configuration content in for 1.0 changes
> --
>
> Key: NIFI-2451
> URL: https://issues.apache.org/jira/browse/NIFI-2451
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> Will need to document changes in Admin Guide for:
> NIFI-1831 for Encryption Configuration



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

[jira] [Commented] (NIFI-2468) Address inconsistent placement of action buttons above tables; minor style edits


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

ASF GitHub Bot commented on NIFI-2468:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/781
  
@scottyaslan There were a few items that we're not implemented from the 
original JIRA. I am going to take your commit from this PR and include it in a 
subsequent PR that I'll post later. It will incorporate the remainder of 
NIFI-2468. Can we please close this one? Thanks!


> Address inconsistent placement of action buttons above tables; minor style 
> edits
> 
>
> Key: NIFI-2468
> URL: https://issues.apache.org/jira/browse/NIFI-2468
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
>
> Use the current Data Provenance table as a model:
> * The inputs (Filter, filter type combo) sit directly on top of the table 
> header (no space between them and the table)
> * The search button sits 4px above the table
> If there are multiple buttons (e.g., in Flow History shell), separate by 2px 
> like buttons in the Navigate and Operate palettes
> OTHER RELATED NOTES
> Configure Processor > Properties tab – Add button icon sits higher (within 
> the button); it is not vertically centered like others
> Controller Service, Reporting Task Add buttons are above the tabs. They 
> should sit above the corresponding table like all others.
> MISC STYLE EDITS
> .combo-text {
> ADD font-weight: normal;
> #general-process-group-configuration input, 
> #general-process-group-configuration textarea {
> REMOVE font-size: 11px!important;
> REMOVE font-family: Verdana;
> #general-settings input {
> REMOVE font-size: 11px!important;
> REMOVE font-family: Verdana;
> All input 'placeholder's should consistently use color:#728E9B
> #settings-last-refreshed {
> CHANGE font-weight: 500;
> .setting-field {
> ADD font-weight: 500;
> .setting-name
> ADD text-transform: capitalize;
> Still seeing some instances where values (color:#775351) are either normal or 
> bold in weight
> * All values should be font-weight:500;



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

[GitHub] nifi issue #781: [NIFI-2468] addressing some inconsistencies

2016-08-04 Thread mcgilman

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/781
  
@scottyaslan There were a few items that we're not implemented from the 
original JIRA. I am going to take your commit from this PR and include it in a 
subsequent PR that I'll post later. It will incorporate the remainder of 
NIFI-2468. Can we please close this one? 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] [Updated] (NIFI-2451) Need to update Security Configuration content in Admin & Dev Guides for 1.0 changes


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

Andrew Lim updated NIFI-2451:
-
Summary: Need to update Security Configuration content in Admin & Dev 
Guides for 1.0 changes  (was: Need to update Encryption Configuration in Admin 
Guide for 1.0 changes)

> Need to update Security Configuration content in Admin & Dev Guides for 1.0 
> changes
> ---
>
> Key: NIFI-2451
> URL: https://issues.apache.org/jira/browse/NIFI-2451
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> Will need to document changes being made in NIFI-1831



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

[GitHub] nifi issue #779: NIFI-2471 fix Hadoop configuration resources when talking t...

2016-08-04 Thread ASF subversion and git services (JIRA)

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/779
  
OK thanks @mosermw. Looks good. Merged to master & 0.x branches.


---
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-2471) Multiple Hadoop processors cannot point to different Hadoop clusters


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

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

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

NIFI-2471 fix Hadoop configuration resources when talking to multiple Hadoop 
clusters
This closes #779.


> Multiple Hadoop processors cannot point to different Hadoop clusters
> 
>
> Key: NIFI-2471
> URL: https://issues.apache.org/jira/browse/NIFI-2471
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
>Priority: Minor
> Fix For: 1.0.0, 0.8.0
>
>
> Two GetHDFS processors, each with different Hadoop Configuration Resources, 
> will only operate with one Hadoop cluster.  In this specific case, both 
> Hadoop clusters had the same HDFS system name.  The AbstractHadoopProcessor 
> disables caching of Configuration and FileSystem objects but it doesn't 
> appear to be working.
> Also, if I configure a GetHDFS processor to point to one Hadoop cluster, but 
> the processor is invalid because the Directory doesn't exist, the processor 
> doesn't start (that's good).  But if I change the Hadoop Configuration 
> Resources to point to a different Hadoop cluster where the Directory does 
> exist, then GetHDFS continues to talk to the first Hadoop cluster.  It seems 
> like the Configuration and FileSystem objects don't reset when I change the 
> Hadoop Configuration Resources property.



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

[jira] [Commented] (NIFI-2471) Multiple Hadoop processors cannot point to different Hadoop clusters

2016-08-04 Thread ASF subversion and git services (JIRA)


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

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

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

NIFI-2471 fix Hadoop configuration resources when talking to multiple Hadoop 
clusters
This closes #779.


> Multiple Hadoop processors cannot point to different Hadoop clusters
> 
>
> Key: NIFI-2471
> URL: https://issues.apache.org/jira/browse/NIFI-2471
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
>Priority: Minor
> Fix For: 1.0.0, 0.8.0
>
>
> Two GetHDFS processors, each with different Hadoop Configuration Resources, 
> will only operate with one Hadoop cluster.  In this specific case, both 
> Hadoop clusters had the same HDFS system name.  The AbstractHadoopProcessor 
> disables caching of Configuration and FileSystem objects but it doesn't 
> appear to be working.
> Also, if I configure a GetHDFS processor to point to one Hadoop cluster, but 
> the processor is invalid because the Directory doesn't exist, the processor 
> doesn't start (that's good).  But if I change the Hadoop Configuration 
> Resources to point to a different Hadoop cluster where the Directory does 
> exist, then GetHDFS continues to talk to the first Hadoop cluster.  It seems 
> like the Configuration and FileSystem objects don't reset when I change the 
> Hadoop Configuration Resources property.



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

[jira] [Commented] (NIFI-2486) Bulletin board needs to take into account component authorization

2016-08-04 Thread ASF subversion and git services (JIRA)


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

ASF GitHub Bot commented on NIFI-2486:
--

GitHub user mcgilman opened a pull request:

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

Authorizing each bulletin returned through the bulletin board

NIFI-2486:
- Authorizing individual bulletins being returned through the bulletin 
board.

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

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

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

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


commit 31457a2afecb44e593f25a9bd03a4142aa7861e8
Author: Matt Gilman 
Date:   2016-08-04T18:53:02Z

NIFI-2486:
- Authorizing individual bulletins being returned through the bulletin 
board.




> Bulletin board needs to take into account component authorization
> -
>
> Key: NIFI-2486
> URL: https://issues.apache.org/jira/browse/NIFI-2486
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Currently no authorization is being done on bulletins and users could see 
> bulletins for components they don't have access to. Users should only be able 
> to see bulletins for the components they have "View" access for.



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

[GitHub] nifi issue #792: Authorizing each bulletin returned through the bulletin boa...

2016-08-04 Thread JPercivall

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/792
  
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 #792: Authorizing each bulletin returned through the bulle...

2016-08-04 Thread mcgilman

GitHub user mcgilman opened a pull request:

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

Authorizing each bulletin returned through the bulletin board

NIFI-2486:
- Authorizing individual bulletins being returned through the bulletin 
board.

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

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

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

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


commit 31457a2afecb44e593f25a9bd03a4142aa7861e8
Author: Matt Gilman 
Date:   2016-08-04T18:53:02Z

NIFI-2486:
- Authorizing individual bulletins being returned through the bulletin 
board.




---
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-2407) Add EL support to processors/controller services


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

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

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

NIFI-2407: Fixed NPE


> Add EL support to processors/controller services
> 
>
> Key: NIFI-2407
> URL: https://issues.apache.org/jira/browse/NIFI-2407
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Jeff Storck
>Assignee: Jeff Storck
> Fix For: 1.0.0
>
>
> Add support for EL:
> * "Directory" property for GetHDFS and ListHDFS processors
> * "Destination Name" property for ConsumeJMS and PublishJMS processors
> * "MQ ConnectionFactory Implementation", "MQ client library path", "Broker 
> URI" properties for the JMS Connection Factory Provider
> * "Database Connection URL", "Database Driver Class Name", "DB Driver jar 
> url", "DB username", and "DB password" properties for the DBCP Connection Pool



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

[GitHub] nifi pull request #778: NIFI-2407 Implements EL support on some properties o...

Github user asfgit closed the pull request at:

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


---
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-2407) Add EL support to processors/controller services


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

Mark Payne updated NIFI-2407:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add EL support to processors/controller services
> 
>
> Key: NIFI-2407
> URL: https://issues.apache.org/jira/browse/NIFI-2407
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Jeff Storck
>Assignee: Jeff Storck
> Fix For: 1.0.0
>
>
> Add support for EL:
> * "Directory" property for GetHDFS and ListHDFS processors
> * "Destination Name" property for ConsumeJMS and PublishJMS processors
> * "MQ ConnectionFactory Implementation", "MQ client library path", "Broker 
> URI" properties for the JMS Connection Factory Provider
> * "Database Connection URL", "Database Driver Class Name", "DB Driver jar 
> url", "DB username", and "DB password" properties for the DBCP Connection Pool



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

[jira] [Commented] (NIFI-2407) Add EL support to processors/controller services


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

ASF GitHub Bot commented on NIFI-2407:
--

Github user asfgit closed the pull request at:

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


> Add EL support to processors/controller services
> 
>
> Key: NIFI-2407
> URL: https://issues.apache.org/jira/browse/NIFI-2407
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Jeff Storck
>Assignee: Jeff Storck
> Fix For: 1.0.0
>
>
> Add support for EL:
> * "Directory" property for GetHDFS and ListHDFS processors
> * "Destination Name" property for ConsumeJMS and PublishJMS processors
> * "MQ ConnectionFactory Implementation", "MQ client library path", "Broker 
> URI" properties for the JMS Connection Factory Provider
> * "Database Connection URL", "Database Driver Class Name", "DB Driver jar 
> url", "DB username", and "DB password" properties for the DBCP Connection Pool



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

[GitHub] nifi issue #778: NIFI-2407 Implements EL support on some properties of proce...

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/778
  
@jtstorck all looks good now. Thanks for updating those! +1, merged 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-2407) Add EL support to processors/controller services


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

ASF GitHub Bot commented on NIFI-2407:
--

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/778
  
@jtstorck all looks good now. Thanks for updating those! +1, merged to 
master.


> Add EL support to processors/controller services
> 
>
> Key: NIFI-2407
> URL: https://issues.apache.org/jira/browse/NIFI-2407
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Jeff Storck
>Assignee: Jeff Storck
> Fix For: 1.0.0
>
>
> Add support for EL:
> * "Directory" property for GetHDFS and ListHDFS processors
> * "Destination Name" property for ConsumeJMS and PublishJMS processors
> * "MQ ConnectionFactory Implementation", "MQ client library path", "Broker 
> URI" properties for the JMS Connection Factory Provider
> * "Database Connection URL", "Database Driver Class Name", "DB Driver jar 
> url", "DB username", and "DB password" properties for the DBCP Connection Pool



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

[jira] [Commented] (NIFI-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory


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

ASF GitHub Bot commented on NIFI-2485:
--

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/790
  
```
nifi-toolkit-1.0.0-SNAPSHOT brosander$ bin/tls-toolkit.sh standalone -n 
host1,host2 -o tmp
16/08/04 14:19:44 INFO standalone.TlsToolkitStandaloneCommandLine: No 
nifiPropertiesFile specified, using embedded one.
16/08/04 14:19:45 INFO standalone.TlsToolkitStandalone: Running standalone 
certificate generation with output directory tmp and hostnames [host1, host2]
16/08/04 14:19:45 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for host1:10443 in tmp/host1
16/08/04 14:19:45 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for host2:10443 in tmp/host2
16/08/04 14:19:45 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for all hosts
```


> Standalone tool sensible default for nifiProperties, httpsPort, 
> outputDirectory
> ---
>
> Key: NIFI-2485
> URL: https://issues.apache.org/jira/browse/NIFI-2485
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Standalone tool has no default for:
> -f, --nifiPropertiesFile
> -p, --httpsPort
> Standalone tool default is unclear for:
> -o, --outputDirectory "." can display "current directory" or "../ directory>"



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

[GitHub] nifi issue #790: NIFI-2485 - Updating standalone defaults, adding logging

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/790
  
```
nifi-toolkit-1.0.0-SNAPSHOT brosander$ bin/tls-toolkit.sh standalone -n 
host1,host2 -o tmp
16/08/04 14:19:44 INFO standalone.TlsToolkitStandaloneCommandLine: No 
nifiPropertiesFile specified, using embedded one.
16/08/04 14:19:45 INFO standalone.TlsToolkitStandalone: Running standalone 
certificate generation with output directory tmp and hostnames [host1, host2]
16/08/04 14:19:45 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for host1:10443 in tmp/host1
16/08/04 14:19:45 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for host2:10443 in tmp/host2
16/08/04 14:19:45 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for all hosts
```


---
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-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory


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

ASF GitHub Bot commented on NIFI-2485:
--

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/790
  
```
HW13384:nifi-toolkit-1.0.0-SNAPSHOT brosander$ bin/tls-toolkit.sh 
standalone -n host1,host2 -o tmp
16/08/04 14:15:50 INFO standalone.TlsToolkitStandaloneCommandLine: No 
nifiPropertiesFile specified, using embedded one.
16/08/04 14:15:50 INFO standalone.TlsToolkitStandalone: Running standalone 
certificate generation with output directory tmp and hostnames [host1, host2]
16/08/04 14:15:50 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for host1:10443 in tmp/host1
16/08/04 14:15:50 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for host2:10443 in tmp/host2
16/08/04 14:15:50 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration
```


> Standalone tool sensible default for nifiProperties, httpsPort, 
> outputDirectory
> ---
>
> Key: NIFI-2485
> URL: https://issues.apache.org/jira/browse/NIFI-2485
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Standalone tool has no default for:
> -f, --nifiPropertiesFile
> -p, --httpsPort
> Standalone tool default is unclear for:
> -o, --outputDirectory "." can display "current directory" or "../ directory>"



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

[GitHub] nifi issue #790: NIFI-2485 - Updating standalone defaults, adding logging

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/790
  
```
HW13384:nifi-toolkit-1.0.0-SNAPSHOT brosander$ bin/tls-toolkit.sh 
standalone -n host1,host2 -o tmp
16/08/04 14:15:50 INFO standalone.TlsToolkitStandaloneCommandLine: No 
nifiPropertiesFile specified, using embedded one.
16/08/04 14:15:50 INFO standalone.TlsToolkitStandalone: Running standalone 
certificate generation with output directory tmp and hostnames [host1, host2]
16/08/04 14:15:50 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for host1:10443 in tmp/host1
16/08/04 14:15:50 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for host2:10443 in tmp/host2
16/08/04 14:15:50 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration
```


---
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-2406) Rare start-up problems resulting in all nodes disconnected


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

ASF GitHub Bot commented on NIFI-2406:
--

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/729
  
@YolandaMDavis is this cluster running an embedded zookeeper? If so, which 
node(s)?


> Rare start-up problems resulting in all nodes disconnected
> --
>
> Key: NIFI-2406
> URL: https://issues.apache.org/jira/browse/NIFI-2406
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Attachments: logs.tar.gz
>
>
> While testing PR 678[1], I came across a time where all the nodes were in a 
> disconnected state and each were in a weird state of heartbeating but not 
> connected.
> Also in the logs there were ~1000 lines of:
> 2016-07-26 11:38:07,841 INFO [Leader Election Notification Thread-1] 
> o.a.n.c.l.e.CuratorLeaderElectionManager 
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@24fae8c6
>  This node has been elected Leader for Role 'Cluster Coordinator'
> This message only gets called here[2] which is a call back for ZK. Also there 
> were many log messages of:
> 2016-07-26 11:54:07,910 WARN [Clustering Tasks Thread-1] 
> o.a.n.c.c.node.NodeClusterCoordinator Failed to determine which node is 
> elected active Cluster Coordinator: ZooKeeper reports the address as 
> localhost:6001, but there is no node with this address
> I believe this is a problem with ZK/NiFi that existed before this PR and not 
> directly related to the PR being reviewed. I will attach a tar of the 3 
> node's logs.
> [1] https://github.com/apache/nifi/pull/678
> [2] 
> https://github.com/apache/nifi/blame/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/leader/election/CuratorLeaderElectionManager.java#L220-L220



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

[GitHub] nifi issue #729: NIFI-2406: Ensure that hearbeat monitor continues to run wh...

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/729
  
@YolandaMDavis is this cluster running an embedded zookeeper? If so, which 
node(s)?


---
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-2484) If a Processor's @OnScheduled method throws an Exception, its @OnStopped methods are not called


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

ASF GitHub Bot commented on NIFI-2484:
--

Github user bbende commented on the issue:

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


> If a Processor's @OnScheduled method throws an Exception, its @OnStopped 
> methods are not called
> ---
>
> Key: NIFI-2484
> URL: https://issues.apache.org/jira/browse/NIFI-2484
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> If a Processor has a method annotated with @OnScheduled and that method 
> throws an Exception, its @OnUnscheduled methods and then @OnStopped methods 
> should be called before calling its @OnScheduled methods again. Currently, 
> only the @OnUnscheduled methods are called.



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

[jira] [Resolved] (NIFI-2435) GetHDFSSequenceFile sequence reader throwing away authenticated filesystem and creating its own


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

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

Merged to master and 0.x

> GetHDFSSequenceFile sequence reader throwing away authenticated filesystem 
> and creating its own
> ---
>
> Key: NIFI-2435
> URL: https://issues.apache.org/jira/browse/NIFI-2435
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.1
> Environment: Kerberos HDFS
>Reporter: Juan Sequeiros
>Assignee: Bryan Rosander
>  Labels: hdfs, kerberos
> Fix For: 1.0.0, 0.7.1
>
>
> Hadoop Kerberos has a way of accessing things as an authenticated user
> UserGroupInformation.doAs
> NIFI is doing  that to get access to the filesystem in order to basically 
> tell hadoop to use the correct credentials so our processor does that 
> correctly and then passes the results into the sequence reader unfortunately, 
> the sequence reader then throws away our authenticated filesystem and creates 
> its own without wrapping in a UGI.doAs
> More context:
> The constructor used for org.apache.hadoop.io.SequenceFile.Reader in both 
> KeyValueReader and ValueReader is deprecated and has been turned into a 
> callthrough that only uses the passed in FileSystem to get the qualified 
> path[1].  I've modified those classes to do that logic and then wrapped the 
> callsite in the processor in a UGI.doAs if it is configured to use a UGI
> [1]: 
> https://github.com/apache/hadoop/commit/0c462b223f151208ff7bd5148cee0e436c23d795#diff-e70823f17863445da52875999e4b19a2L1592



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

[GitHub] nifi issue #791: NIFI-2484: Ensure that if a Processor throws an Exception f...

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/791
  
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-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory


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

ASF GitHub Bot commented on NIFI-2485:
--

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/790
  
Thanks for the feedback, will make it so


> Standalone tool sensible default for nifiProperties, httpsPort, 
> outputDirectory
> ---
>
> Key: NIFI-2485
> URL: https://issues.apache.org/jira/browse/NIFI-2485
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Standalone tool has no default for:
> -f, --nifiPropertiesFile
> -p, --httpsPort
> Standalone tool default is unclear for:
> -o, --outputDirectory "." can display "current directory" or "../ directory>"



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

[GitHub] nifi issue #790: NIFI-2485 - Updating standalone defaults, adding logging

2016-08-04 Thread ASF subversion and git services (JIRA)

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/790
  
Thanks for the feedback, will make it so


---
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-2435) GetHDFSSequenceFile sequence reader throwing away authenticated filesystem and creating its own


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

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

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

NIFI-2435 - Wrapping reader call in doAs if necessary

This closes #780.

Signed-off-by: Bryan Bende 


> GetHDFSSequenceFile sequence reader throwing away authenticated filesystem 
> and creating its own
> ---
>
> Key: NIFI-2435
> URL: https://issues.apache.org/jira/browse/NIFI-2435
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.1
> Environment: Kerberos HDFS
>Reporter: Juan Sequeiros
>Assignee: Bryan Rosander
>  Labels: hdfs, kerberos
> Fix For: 1.0.0, 0.7.1
>
>
> Hadoop Kerberos has a way of accessing things as an authenticated user
> UserGroupInformation.doAs
> NIFI is doing  that to get access to the filesystem in order to basically 
> tell hadoop to use the correct credentials so our processor does that 
> correctly and then passes the results into the sequence reader unfortunately, 
> the sequence reader then throws away our authenticated filesystem and creates 
> its own without wrapping in a UGI.doAs
> More context:
> The constructor used for org.apache.hadoop.io.SequenceFile.Reader in both 
> KeyValueReader and ValueReader is deprecated and has been turned into a 
> callthrough that only uses the passed in FileSystem to get the qualified 
> path[1].  I've modified those classes to do that logic and then wrapped the 
> callsite in the processor in a UGI.doAs if it is configured to use a UGI
> [1]: 
> https://github.com/apache/hadoop/commit/0c462b223f151208ff7bd5148cee0e436c23d795#diff-e70823f17863445da52875999e4b19a2L1592



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

[jira] [Commented] (NIFI-2435) GetHDFSSequenceFile sequence reader throwing away authenticated filesystem and creating its own

2016-08-04 Thread ASF subversion and git services (JIRA)


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

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

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

NIFI-2435 - Wrapping reader call in doAs if necessary

This closes #780.

Signed-off-by: Bryan Bende 


> GetHDFSSequenceFile sequence reader throwing away authenticated filesystem 
> and creating its own
> ---
>
> Key: NIFI-2435
> URL: https://issues.apache.org/jira/browse/NIFI-2435
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.1
> Environment: Kerberos HDFS
>Reporter: Juan Sequeiros
>Assignee: Bryan Rosander
>  Labels: hdfs, kerberos
> Fix For: 1.0.0, 0.7.1
>
>
> Hadoop Kerberos has a way of accessing things as an authenticated user
> UserGroupInformation.doAs
> NIFI is doing  that to get access to the filesystem in order to basically 
> tell hadoop to use the correct credentials so our processor does that 
> correctly and then passes the results into the sequence reader unfortunately, 
> the sequence reader then throws away our authenticated filesystem and creates 
> its own without wrapping in a UGI.doAs
> More context:
> The constructor used for org.apache.hadoop.io.SequenceFile.Reader in both 
> KeyValueReader and ValueReader is deprecated and has been turned into a 
> callthrough that only uses the passed in FileSystem to get the qualified 
> path[1].  I've modified those classes to do that logic and then wrapped the 
> callsite in the processor in a UGI.doAs if it is configured to use a UGI
> [1]: 
> https://github.com/apache/hadoop/commit/0c462b223f151208ff7bd5148cee0e436c23d795#diff-e70823f17863445da52875999e4b19a2L1592



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

[GitHub] nifi pull request #780: NIFI-2435 - Wrapping reader call in doAs if necessar...

Github user asfgit closed the pull request at:

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


---
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-2435) GetHDFSSequenceFile sequence reader throwing away authenticated filesystem and creating its own


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

ASF GitHub Bot commented on NIFI-2435:
--

Github user asfgit closed the pull request at:

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


> GetHDFSSequenceFile sequence reader throwing away authenticated filesystem 
> and creating its own
> ---
>
> Key: NIFI-2435
> URL: https://issues.apache.org/jira/browse/NIFI-2435
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.1
> Environment: Kerberos HDFS
>Reporter: Juan Sequeiros
>Assignee: Bryan Rosander
>  Labels: hdfs, kerberos
> Fix For: 1.0.0, 0.7.1
>
>
> Hadoop Kerberos has a way of accessing things as an authenticated user
> UserGroupInformation.doAs
> NIFI is doing  that to get access to the filesystem in order to basically 
> tell hadoop to use the correct credentials so our processor does that 
> correctly and then passes the results into the sequence reader unfortunately, 
> the sequence reader then throws away our authenticated filesystem and creates 
> its own without wrapping in a UGI.doAs
> More context:
> The constructor used for org.apache.hadoop.io.SequenceFile.Reader in both 
> KeyValueReader and ValueReader is deprecated and has been turned into a 
> callthrough that only uses the passed in FileSystem to get the qualified 
> path[1].  I've modified those classes to do that logic and then wrapped the 
> callsite in the processor in a UGI.doAs if it is configured to use a UGI
> [1]: 
> https://github.com/apache/hadoop/commit/0c462b223f151208ff7bd5148cee0e436c23d795#diff-e70823f17863445da52875999e4b19a2L1592



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

[jira] [Commented] (NIFI-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory


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

ASF GitHub Bot commented on NIFI-2485:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/790
  
I would like to see the log output contain a line for each host generated, 
specifying the output directory, hostname, and port. 

Example:
```bash

hw12203:...assembly/target/nifi-toolkit-1.0.0-SNAPSHOT-bin/nifi-toolkit-1.0.0-SNAPSHOT
 (pr790) alopresto
 0s @ 10:55:43 $ ./bin/tls-toolkit.sh standalone -n host1,host2
16/08/04 10:56:00 INFO standalone.TlsToolkitStandaloneCommandLine: No 
nifiPropertiesFile specified, using embedded one.
16/08/04 10:56:00 INFO standalone.TlsToolkitStandalone: Running standalone 
certificate generation with output directory ../nifi-toolkit-1.0.0-SNAPSHOT and 
hostnames [host1, host2]
16/08/04 10:56:01 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for "host1:10443" in host1/
16/08/04 10:56:01 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for "host2:10443" in host2/

hw12203:...assembly/target/nifi-toolkit-1.0.0-SNAPSHOT-bin/nifi-toolkit-1.0.0-SNAPSHOT
 (pr790) alopresto
 18s @ 10:56:02 $
```

With only one or two hosts, it's easy to see on one line, but if many are 
provided or the tool errors halfway through, it's nice to have a record of what 
was performed. 


> Standalone tool sensible default for nifiProperties, httpsPort, 
> outputDirectory
> ---
>
> Key: NIFI-2485
> URL: https://issues.apache.org/jira/browse/NIFI-2485
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Standalone tool has no default for:
> -f, --nifiPropertiesFile
> -p, --httpsPort
> Standalone tool default is unclear for:
> -o, --outputDirectory "." can display "current directory" or "../ directory>"



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

[GitHub] nifi issue #790: NIFI-2485 - Updating standalone defaults, adding logging

2016-08-04 Thread alopresto

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/790
  
I would like to see the log output contain a line for each host generated, 
specifying the output directory, hostname, and port. 

Example:
```bash

hw12203:...assembly/target/nifi-toolkit-1.0.0-SNAPSHOT-bin/nifi-toolkit-1.0.0-SNAPSHOT
 (pr790) alopresto
ð 0s @ 10:55:43 $ ./bin/tls-toolkit.sh standalone -n host1,host2
16/08/04 10:56:00 INFO standalone.TlsToolkitStandaloneCommandLine: No 
nifiPropertiesFile specified, using embedded one.
16/08/04 10:56:00 INFO standalone.TlsToolkitStandalone: Running standalone 
certificate generation with output directory ../nifi-toolkit-1.0.0-SNAPSHOT and 
hostnames [host1, host2]
16/08/04 10:56:01 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for "host1:10443" in host1/
16/08/04 10:56:01 INFO standalone.TlsToolkitStandalone: Successfully 
generated TLS configuration for "host2:10443" in host2/

hw12203:...assembly/target/nifi-toolkit-1.0.0-SNAPSHOT-bin/nifi-toolkit-1.0.0-SNAPSHOT
 (pr790) alopresto
ð 18s @ 10:56:02 $
```

With only one or two hosts, it's easy to see on one line, but if many are 
provided or the tool errors halfway through, it's nice to have a record of what 
was performed. 


---
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 #729: NIFI-2406: Ensure that hearbeat monitor continues to run wh...

2016-08-04 Thread YolandaMDavis

Github user YolandaMDavis commented on the issue:

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

@markap14 thanks! have retested tried disconnecting nodes as well as
restarting nodes in cluster. Did see the error logged "This node was elected
Leader for Role 'Cluster Coordinator' but failed to take leadership. Will
relinquish leadership role." on one node with error thrown due to the node not
being part of the cluster. That was also followed up with the logged warning
"Failed to determine which node is elected active Cluster Coordinator:
ZooKeeper reports the address as 127.0.0.1:11001, but there is no node with
this address". This occurred during initial startup and appeared to resolve
once the cluster coodinator (node 2, on port 11001) came online.

I also shutdown node 2 (which was Cluster Coordinator) and noted the
repeated "Failed to send heartbeat due to:
org.apache.nifi.cluster.protocol.ProtocolException: Failed to send message to
Cluster Coordinator due to: java.net.ConnectException: Connection refused"
warning in node 1's log. This was expected based on notes in Jira. Node 1 was
primary node at the time. When node 2 was back online the heartbeat warning no
longer appeared in node 1's log however I could not access node 1's UI (it was
displaying an error demonstrated in the snapshot below).

I've included just the nifi-app logs from both servers since it seemed to
have the most relevant information. Would focus on logs with timestamps
beginning at 13:35 (08-04-2016). Please let me know if you need any additional
information or logs.

https://cloud.githubusercontent.com/assets/1371858/17412342/3f28890a-5a4a-11e6-8ff8-d3acd5a5b0b8.png;>

[logs.zip](https://github.com/apache/nifi/files/402267/logs.zip)

---
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-2406) Rare start-up problems resulting in all nodes disconnected


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

ASF GitHub Bot commented on NIFI-2406:
--

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/729
  
@markap14 thanks! have retested tried disconnecting nodes as well as 
restarting nodes in cluster.  Did see the error logged "This node was elected 
Leader for Role 'Cluster Coordinator' but failed to take leadership. Will 
relinquish leadership role." on one node with error thrown due to the node not 
being part of the cluster.  That was also followed up with the logged warning 
"Failed to determine which node is elected active Cluster Coordinator: 
ZooKeeper reports the address as 127.0.0.1:11001, but there is no node with 
this address".  This occurred during initial startup and appeared to resolve 
once the cluster coodinator (node 2, on port 11001) came online.

I also shutdown node 2 (which was Cluster Coordinator) and noted the 
repeated "Failed to send heartbeat due to: 
org.apache.nifi.cluster.protocol.ProtocolException: Failed to send message to 
Cluster Coordinator due to: java.net.ConnectException: Connection refused" 
warning in node 1's log.  This was expected based on notes in Jira.  Node 1 was 
primary node at the time.  When node 2 was back online the heartbeat warning no 
longer appeared in node 1's log however I could not access node 1's UI (it was 
displaying an error demonstrated in the snapshot below).

I've included just the nifi-app logs from both servers since it seemed to 
have the most relevant information. Would focus on logs with timestamps 
beginning at 13:35 (08-04-2016). Please let me know if you need any additional 
information or logs.


https://cloud.githubusercontent.com/assets/1371858/17412342/3f28890a-5a4a-11e6-8ff8-d3acd5a5b0b8.png;>

[logs.zip](https://github.com/apache/nifi/files/402267/logs.zip)







> Rare start-up problems resulting in all nodes disconnected
> --
>
> Key: NIFI-2406
> URL: https://issues.apache.org/jira/browse/NIFI-2406
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Attachments: logs.tar.gz
>
>
> While testing PR 678[1], I came across a time where all the nodes were in a 
> disconnected state and each were in a weird state of heartbeating but not 
> connected.
> Also in the logs there were ~1000 lines of:
> 2016-07-26 11:38:07,841 INFO [Leader Election Notification Thread-1] 
> o.a.n.c.l.e.CuratorLeaderElectionManager 
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@24fae8c6
>  This node has been elected Leader for Role 'Cluster Coordinator'
> This message only gets called here[2] which is a call back for ZK. Also there 
> were many log messages of:
> 2016-07-26 11:54:07,910 WARN [Clustering Tasks Thread-1] 
> o.a.n.c.c.node.NodeClusterCoordinator Failed to determine which node is 
> elected active Cluster Coordinator: ZooKeeper reports the address as 
> localhost:6001, but there is no node with this address
> I believe this is a problem with ZK/NiFi that existed before this PR and not 
> directly related to the PR being reviewed. I will attach a tar of the 3 
> node's logs.
> [1] https://github.com/apache/nifi/pull/678
> [2] 
> https://github.com/apache/nifi/blame/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/leader/election/CuratorLeaderElectionManager.java#L220-L220



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

[jira] [Updated] (NIFI-2484) If a Processor's @OnScheduled method throws an Exception, its @OnStopped methods are not called


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

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

> If a Processor's @OnScheduled method throws an Exception, its @OnStopped 
> methods are not called
> ---
>
> Key: NIFI-2484
> URL: https://issues.apache.org/jira/browse/NIFI-2484
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> If a Processor has a method annotated with @OnScheduled and that method 
> throws an Exception, its @OnUnscheduled methods and then @OnStopped methods 
> should be called before calling its @OnScheduled methods again. Currently, 
> only the @OnUnscheduled methods are called.



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

[GitHub] nifi pull request #791: NIFI-2484: Ensure that if a Processor throws an Exce...

GitHub user markap14 opened a pull request:

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

NIFI-2484: Ensure that if a Processor throws an Exception from an @Onâ¦

â¦Scheduled method that @OnStopped methods get called

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

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

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

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


commit d3cff21dc464e76c6736109c7c26c12cf418d5a1
Author: Mark Payne 
Date:   2016-08-04T17:05:03Z

NIFI-2484: Ensure that if a Processor throws an Exception from an 
@OnScheduled method that @OnStopped methods get called




---
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-2487) Provenance Repository occasionally reporting that a prov file is "Not in GZIP Format"

Mark Payne created NIFI-2487:


 Summary: Provenance Repository occasionally reporting that a prov 
file is "Not in GZIP Format"
 Key: NIFI-2487
 URL: https://issues.apache.org/jira/browse/NIFI-2487
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Mark Payne
Assignee: Mark Payne
 Fix For: 1.0.0


I occasionally see the following stack trace in my logs:

{code}
2016-08-04 16:24:06,653 ERROR [Timer-Driven Process Thread-11] 
o.a.n.p.PersistentProvenanceRepository Failed to read Provenance Event File 
/nifi/0/repos/prov/1/10585433663.prov.gz due to java.util.zip.ZipException: Not 
in GZIP format
2016-08-04 16:24:06,668 ERROR [Timer-Driven Process Thread-11] 
o.a.n.p.PersistentProvenanceRepository
java.util.zip.ZipException: Not in GZIP format
at java.util.zip.GZIPInputStream.readHeader(GZIPInputStream.java:165) 
~[na:1.8.0_91]
at java.util.zip.GZIPInputStream.(GZIPInputStream.java:79) 
~[na:1.8.0_91]
at java.util.zip.GZIPInputStream.(GZIPInputStream.java:91) 
~[na:1.8.0_91]
at 
org.apache.nifi.provenance.StandardRecordReader.resetStreamForNextBlock(StandardRecordReader.java:151)
 ~[nifi-persistent-provenance-repository-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.provenance.StandardRecordReader.isData(StandardRecordReader.java:438)
 ~[nifi-persistent-provenance-repository-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.provenance.StandardRecordReader.nextRecord(StandardRecordReader.java:273)
 ~[nifi-persistent-provenance-repository-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.provenance.PersistentProvenanceRepository.getEvents(PersistentProvenanceRepository.java:476)
 [nifi-persistent-provenance-repository-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.provenance.PersistentProvenanceRepository.getEvents(PersistentProvenanceRepository.java:448)
 [nifi-persistent-provenance-repository-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.FlowController.getProvenanceEvents(FlowController.java:3984)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.reporting.SiteToSiteProvenanceReportingTask.onTrigger(SiteToSiteProvenanceReportingTask.java:235)
 [nifi-site-to-site-reporting-task-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.tasks.ReportingTaskWrapper.run(ReportingTaskWrapper.java:41)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_91]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_91]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_91]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_91]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_91]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
{code}



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

[jira] [Assigned] (NIFI-2486) Bulletin board needs to take into account component authorization

2016-08-04 Thread Matt Gilman (JIRA)


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

Matt Gilman reassigned NIFI-2486:
-

Assignee: Matt Gilman

> Bulletin board needs to take into account component authorization
> -
>
> Key: NIFI-2486
> URL: https://issues.apache.org/jira/browse/NIFI-2486
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Currently no authorization is being done on bulletins and users could see 
> bulletins for components they don't have access to. Users should only be able 
> to see bulletins for the components they have "View" access for.



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

[jira] [Created] (NIFI-2486) Bulletin board needs to take into account component authorization

Joseph Percivall created NIFI-2486:
--

 Summary: Bulletin board needs to take into account component 
authorization
 Key: NIFI-2486
 URL: https://issues.apache.org/jira/browse/NIFI-2486
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Joseph Percivall
Priority: Blocker
 Fix For: 1.0.0


Currently no authorization is being done on bulletins and users could see 
bulletins for components they don't have access to. Users should only be able 
to see bulletins for the components they have "View" access for.



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

[GitHub] nifi issue #769: how to kafka data to hive

2016-08-04 Thread mattyb149

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/769
  
this looks like a merge between two existing branches (an RC candidate and 
master). Is there a code change you are trying to submit?


---
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-2471) Multiple Hadoop processors cannot point to different Hadoop clusters


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

ASF GitHub Bot commented on NIFI-2471:
--

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

https://github.com/apache/nifi/pull/779#discussion_r73552111
  
--- Diff: 
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/AbstractHadoopProcessor.java
 ---
@@ -177,9 +178,17 @@ protected KerberosProperties getKerberosProperties() {
 return results;
 }
 
+@Override
+public void onPropertyModified(PropertyDescriptor descriptor, String 
oldValue, String newValue) {
--- End diff --

Alrighty, no problem.  I've added a commit to this PR to remove this 
onPropertyModified method.  Hopefully the two commits can be squashed to one.  
Thanks!


> Multiple Hadoop processors cannot point to different Hadoop clusters
> 
>
> Key: NIFI-2471
> URL: https://issues.apache.org/jira/browse/NIFI-2471
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
>Priority: Minor
> Fix For: 1.0.0, 0.8.0
>
>
> Two GetHDFS processors, each with different Hadoop Configuration Resources, 
> will only operate with one Hadoop cluster.  In this specific case, both 
> Hadoop clusters had the same HDFS system name.  The AbstractHadoopProcessor 
> disables caching of Configuration and FileSystem objects but it doesn't 
> appear to be working.
> Also, if I configure a GetHDFS processor to point to one Hadoop cluster, but 
> the processor is invalid because the Directory doesn't exist, the processor 
> doesn't start (that's good).  But if I change the Hadoop Configuration 
> Resources to point to a different Hadoop cluster where the Directory does 
> exist, then GetHDFS continues to talk to the first Hadoop cluster.  It seems 
> like the Configuration and FileSystem objects don't reset when I change the 
> Hadoop Configuration Resources property.



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

[GitHub] nifi issue #778: NIFI-2407 Implements EL support on some properties of proce...

2016-08-04 Thread jtstorck

Github user jtstorck commented on the issue:

https://github.com/apache/nifi/pull/778
  
Updated based on feedback, ready for review.


---
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 #779: NIFI-2471 fix Hadoop configuration resources when ta...

2016-08-04 Thread mosermw

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

https://github.com/apache/nifi/pull/779#discussion_r73552111
  
--- Diff: 
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/AbstractHadoopProcessor.java
 ---
@@ -177,9 +178,17 @@ protected KerberosProperties getKerberosProperties() {
 return results;
 }
 
+@Override
+public void onPropertyModified(PropertyDescriptor descriptor, String 
oldValue, String newValue) {
--- End diff --

Alrighty, no problem.  I've added a commit to this PR to remove this 
onPropertyModified method.  Hopefully the two commits can be squashed to one.  
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-2407) Add EL support to processors/controller services


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

ASF GitHub Bot commented on NIFI-2407:
--

Github user jtstorck commented on the issue:

https://github.com/apache/nifi/pull/778
  
Updated based on feedback, ready for review.


> Add EL support to processors/controller services
> 
>
> Key: NIFI-2407
> URL: https://issues.apache.org/jira/browse/NIFI-2407
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Jeff Storck
>Assignee: Jeff Storck
> Fix For: 1.0.0
>
>
> Add support for EL:
> * "Directory" property for GetHDFS and ListHDFS processors
> * "Destination Name" property for ConsumeJMS and PublishJMS processors
> * "MQ ConnectionFactory Implementation", "MQ client library path", "Broker 
> URI" properties for the JMS Connection Factory Provider
> * "Database Connection URL", "Database Driver Class Name", "DB Driver jar 
> url", "DB username", and "DB password" properties for the DBCP Connection Pool



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

[jira] [Commented] (NIFI-1148) Add processor to GetEmail supporting IMAP and POP3

2016-08-04 Thread Joseph Witt (JIRA)


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

Joseph Witt commented on NIFI-1148:
---

i meant to review but can't dig in today

> Add processor to GetEmail supporting IMAP and POP3
> --
>
> Key: NIFI-1148
> URL: https://issues.apache.org/jira/browse/NIFI-1148
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



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

[jira] [Commented] (NIFI-2458) After canceling provenance query, cannot submit a new one

2016-08-04 Thread Joseph Witt (JIRA)


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

Joseph Witt commented on NIFI-2458:
---

ah sorry - took my name off - not in a good position to dive in today

> After canceling provenance query, cannot submit a new one
> -
>
> Key: NIFI-2458
> URL: https://issues.apache.org/jira/browse/NIFI-2458
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Mark Payne
> Fix For: 1.0.0
>
>
> I right-clicked on a Processor and choose to view provenance events. I then 
> clicked Cancel on the progress bar dialog. I then clicked 'search' and added 
> a new parameter to the search (added a value for 'Relationship'). When I 
> click Search, I get an error message: Message body is malformed. Unable to 
> map into expected format.



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

[jira] [Updated] (NIFI-2458) After canceling provenance query, cannot submit a new one

2016-08-04 Thread Joseph Witt (JIRA)


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

Joseph Witt updated NIFI-2458:
--
Assignee: (was: Joseph Witt)

> After canceling provenance query, cannot submit a new one
> -
>
> Key: NIFI-2458
> URL: https://issues.apache.org/jira/browse/NIFI-2458
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Mark Payne
> Fix For: 1.0.0
>
>
> I right-clicked on a Processor and choose to view provenance events. I then 
> clicked Cancel on the progress bar dialog. I then clicked 'search' and added 
> a new parameter to the search (added a value for 'Relationship'). When I 
> click Search, I get an error message: Message body is malformed. Unable to 
> map into expected format.



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

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


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

Mark Payne updated NIFI-2035:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

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



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

[jira] [Commented] (NIFI-2476) Further refine tls-toolkit based on feedback gathered during beta


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

Bryan Rosander commented on NIFI-2476:
--

Should be addressed by default https port value in NIFI-2485

> Further refine tls-toolkit based on feedback gathered during beta
> -
>
> Key: NIFI-2476
> URL: https://issues.apache.org/jira/browse/NIFI-2476
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> The basic functionality of generating keystores, truststores, 
> nifi.properties, and a configuration json is implemented.
> As people start using this tool to ease the tls setup process in NiFi, 
> shortcomings in the initial implementation will need to be addressed.



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

[jira] [Commented] (NIFI-2476) Further refine tls-toolkit based on feedback gathered during beta


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

Bryan Rosander commented on NIFI-2476:
--

Created NIFI-2485 to address

> Further refine tls-toolkit based on feedback gathered during beta
> -
>
> Key: NIFI-2476
> URL: https://issues.apache.org/jira/browse/NIFI-2476
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> The basic functionality of generating keystores, truststores, 
> nifi.properties, and a configuration json is implemented.
> As people start using this tool to ease the tls setup process in NiFi, 
> shortcomings in the initial implementation will need to be addressed.



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

[jira] [Commented] (NIFI-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory


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

ASF GitHub Bot commented on NIFI-2485:
--

GitHub user brosander opened a pull request:

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

NIFI-2485 - Updating standalone defaults, adding logging



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

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

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

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


commit 9b41e0f9fde39a42e37f14fb2a12d599c6b1242a
Author: Bryan Rosander 
Date:   2016-08-04T15:37:32Z

NIFI-2485 - Updating standalone defaults, adding logging




> Standalone tool sensible default for nifiProperties, httpsPort, 
> outputDirectory
> ---
>
> Key: NIFI-2485
> URL: https://issues.apache.org/jira/browse/NIFI-2485
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Standalone tool has no default for:
> -f, --nifiPropertiesFile
> -p, --httpsPort
> Standalone tool default is unclear for:
> -o, --outputDirectory "." can display "current directory" or "../ directory>"



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

[GitHub] nifi pull request #790: NIFI-2485 - Updating standalone defaults, adding log...

GitHub user brosander opened a pull request:

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

NIFI-2485 - Updating standalone defaults, adding logging



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

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

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

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


commit 9b41e0f9fde39a42e37f14fb2a12d599c6b1242a
Author: Bryan Rosander 
Date:   2016-08-04T15:37:32Z

NIFI-2485 - Updating standalone defaults, adding logging




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

[jira] [Assigned] (NIFI-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory


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

Bryan Rosander reassigned NIFI-2485:


Assignee: Bryan Rosander

> Standalone tool sensible default for nifiProperties, httpsPort, 
> outputDirectory
> ---
>
> Key: NIFI-2485
> URL: https://issues.apache.org/jira/browse/NIFI-2485
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> Standalone tool has no default for:
> -f, --nifiPropertiesFile
> -p, --httpsPort
> Standalone tool default is unclear for:
> -o, --outputDirectory "." can display "current directory" or "../ directory>"



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

[jira] [Created] (NIFI-2485) Standalone tool sensible default for nifiProperties, httpsPort, outputDirectory

Bryan Rosander created NIFI-2485:


 Summary: Standalone tool sensible default for nifiProperties, 
httpsPort, outputDirectory
 Key: NIFI-2485
 URL: https://issues.apache.org/jira/browse/NIFI-2485
 Project: Apache NiFi
  Issue Type: Sub-task
Reporter: Bryan Rosander


Standalone tool has no default for:
-f, --nifiPropertiesFile
-p, --httpsPort
Standalone tool default is unclear for:
-o, --outputDirectory "." can display "current directory" or "../"



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

[jira] [Commented] (NIFI-2471) Multiple Hadoop processors cannot point to different Hadoop clusters


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

ASF GitHub Bot commented on NIFI-2471:
--

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

https://github.com/apache/nifi/pull/779#discussion_r73546113
  
--- Diff: 
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/AbstractHadoopProcessor.java
 ---
@@ -177,9 +178,17 @@ protected KerberosProperties getKerberosProperties() {
 return results;
 }
 
+@Override
+public void onPropertyModified(PropertyDescriptor descriptor, String 
oldValue, String newValue) {
--- End diff --

Looks like you're right - it is not calling @OnStopped methods when 
@OnScheduled throws an Exception. I created a ticket for that - 
https://issues.apache.org/jira/browse/NIFI-2484. I think we should avoid 
working around the bug in this PR though and just address it in the framework.


> Multiple Hadoop processors cannot point to different Hadoop clusters
> 
>
> Key: NIFI-2471
> URL: https://issues.apache.org/jira/browse/NIFI-2471
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
>Priority: Minor
> Fix For: 1.0.0, 0.8.0
>
>
> Two GetHDFS processors, each with different Hadoop Configuration Resources, 
> will only operate with one Hadoop cluster.  In this specific case, both 
> Hadoop clusters had the same HDFS system name.  The AbstractHadoopProcessor 
> disables caching of Configuration and FileSystem objects but it doesn't 
> appear to be working.
> Also, if I configure a GetHDFS processor to point to one Hadoop cluster, but 
> the processor is invalid because the Directory doesn't exist, the processor 
> doesn't start (that's good).  But if I change the Hadoop Configuration 
> Resources to point to a different Hadoop cluster where the Directory does 
> exist, then GetHDFS continues to talk to the first Hadoop cluster.  It seems 
> like the Configuration and FileSystem objects don't reset when I change the 
> Hadoop Configuration Resources property.



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

[GitHub] nifi pull request #779: NIFI-2471 fix Hadoop configuration resources when ta...

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

https://github.com/apache/nifi/pull/779#discussion_r73546113
  
--- Diff: 
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/AbstractHadoopProcessor.java
 ---
@@ -177,9 +178,17 @@ protected KerberosProperties getKerberosProperties() {
 return results;
 }
 
+@Override
+public void onPropertyModified(PropertyDescriptor descriptor, String 
oldValue, String newValue) {
--- End diff --

Looks like you're right - it is not calling @OnStopped methods when 
@OnScheduled throws an Exception. I created a ticket for that - 
https://issues.apache.org/jira/browse/NIFI-2484. I think we should avoid 
working around the bug in this PR though and just address it in the framework.


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

[jira] [Assigned] (NIFI-2476) Further refine tls-toolkit based on feedback gathered during beta


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

Bryan Rosander reassigned NIFI-2476:


Assignee: Bryan Rosander

> Further refine tls-toolkit based on feedback gathered during beta
> -
>
> Key: NIFI-2476
> URL: https://issues.apache.org/jira/browse/NIFI-2476
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> The basic functionality of generating keystores, truststores, 
> nifi.properties, and a configuration json is implemented.
> As people start using this tool to ease the tls setup process in NiFi, 
> shortcomings in the initial implementation will need to be addressed.



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

[jira] [Commented] (NIFI-2435) GetHDFSSequenceFile sequence reader throwing away authenticated filesystem and creating its own


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

ASF GitHub Bot commented on NIFI-2435:
--

Github user bbende commented on the issue:

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


> GetHDFSSequenceFile sequence reader throwing away authenticated filesystem 
> and creating its own
> ---
>
> Key: NIFI-2435
> URL: https://issues.apache.org/jira/browse/NIFI-2435
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.1
> Environment: Kerberos HDFS
>Reporter: Juan Sequeiros
>Assignee: Bryan Rosander
>  Labels: hdfs, kerberos
> Fix For: 1.0.0, 0.7.1
>
>
> Hadoop Kerberos has a way of accessing things as an authenticated user
> UserGroupInformation.doAs
> NIFI is doing  that to get access to the filesystem in order to basically 
> tell hadoop to use the correct credentials so our processor does that 
> correctly and then passes the results into the sequence reader unfortunately, 
> the sequence reader then throws away our authenticated filesystem and creates 
> its own without wrapping in a UGI.doAs
> More context:
> The constructor used for org.apache.hadoop.io.SequenceFile.Reader in both 
> KeyValueReader and ValueReader is deprecated and has been turned into a 
> callthrough that only uses the passed in FileSystem to get the qualified 
> path[1].  I've modified those classes to do that logic and then wrapped the 
> callsite in the processor in a UGI.doAs if it is configured to use a UGI
> [1]: 
> https://github.com/apache/hadoop/commit/0c462b223f151208ff7bd5148cee0e436c23d795#diff-e70823f17863445da52875999e4b19a2L1592



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

[GitHub] nifi issue #780: NIFI-2435 - Wrapping reader call in doAs if necessary