[jira] [Commented] (NIFI-614) Create a JMS ConnectionFactory controller service and refactor JMS processors to use it

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-614 Added initial support for new style JMS

NIFI-614 finalized JMSConnectionFactoryProvider ControllerService

NIFI-614 finalized implementation of both Processors and ControllerService

NIFI-614 added initial documentation

NIFI-614 addressed PR comment with unused import and squashed

NIFI-614 added @OnDisabled method

NIFI-614 changed POMs to 0.6

NIFI-614 removed local .gitignore

NIFI-614 added support for parsing Tibco URL

NIFI-614 removed setting of jms message id

NIFI-614 addressed PR comments, fixed tests

NIFI-614 addressed latest PR comments

NIFI-614 second round of PR comments addressed

NIFI-614 3rd round of PR comments addressed

NIFI-614 finalizing on PR comments

NIFI-614 more PR comments

This closes #222

Signed-off-by: jpercivall 


> Create a JMS ConnectionFactory controller service and refactor JMS processors 
> to use it
> ---
>
> Key: NIFI-614
> URL: https://issues.apache.org/jira/browse/NIFI-614
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.1.0
>Reporter: Michael Moser
>Assignee: Oleg Zhurakousky
>  Labels: JMS
> Fix For: 0.6.0
>
>
> It is difficult to extend the standard JMS processors to use a different JMS 
> provider besides the included ActiveMQ.  Improve the process of adding 
> support for other JMS providers.
> Create a JMS ConnectionFactoryService API in nifi-standard-services.  Create 
> an ActiveMQConnectionFactoryService with the ActiveMQ implementation in 
> nifi-standard-services.  Modify the JMS processors in 
> nifi-standard-processors to use a ConnectionFactoryService to pick the JMS 
> Provider to use.



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

[jira] [Commented] (NIFI-614) Create a JMS ConnectionFactory controller service and refactor JMS processors to use it

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-614 Added initial support for new style JMS

NIFI-614 finalized JMSConnectionFactoryProvider ControllerService

NIFI-614 finalized implementation of both Processors and ControllerService

NIFI-614 added initial documentation

NIFI-614 addressed PR comment with unused import and squashed

NIFI-614 added @OnDisabled method

NIFI-614 changed POMs to 0.6

NIFI-614 removed local .gitignore

NIFI-614 added support for parsing Tibco URL

NIFI-614 removed setting of jms message id

NIFI-614 addressed PR comments, fixed tests

NIFI-614 addressed latest PR comments

NIFI-614 second round of PR comments addressed

NIFI-614 3rd round of PR comments addressed

NIFI-614 finalizing on PR comments

NIFI-614 more PR comments

This closes #222

Signed-off-by: jpercivall 


> Create a JMS ConnectionFactory controller service and refactor JMS processors 
> to use it
> ---
>
> Key: NIFI-614
> URL: https://issues.apache.org/jira/browse/NIFI-614
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.1.0
>Reporter: Michael Moser
>Assignee: Oleg Zhurakousky
>  Labels: JMS
> Fix For: 0.6.0
>
>
> It is difficult to extend the standard JMS processors to use a different JMS 
> provider besides the included ActiveMQ.  Improve the process of adding 
> support for other JMS providers.
> Create a JMS ConnectionFactoryService API in nifi-standard-services.  Create 
> an ActiveMQConnectionFactoryService with the ActiveMQ implementation in 
> nifi-standard-services.  Modify the JMS processors in 
> nifi-standard-processors to use a ConnectionFactoryService to pick the JMS 
> Provider to use.



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

[jira] [Commented] (NIFI-614) Create a JMS ConnectionFactory controller service and refactor JMS processors to use it

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-614 Added initial support for new style JMS

NIFI-614 finalized JMSConnectionFactoryProvider ControllerService

NIFI-614 finalized implementation of both Processors and ControllerService

NIFI-614 added initial documentation

NIFI-614 addressed PR comment with unused import and squashed

NIFI-614 added @OnDisabled method

NIFI-614 changed POMs to 0.6

NIFI-614 removed local .gitignore

NIFI-614 added support for parsing Tibco URL

NIFI-614 removed setting of jms message id

NIFI-614 addressed PR comments, fixed tests

NIFI-614 addressed latest PR comments

NIFI-614 second round of PR comments addressed

NIFI-614 3rd round of PR comments addressed

NIFI-614 finalizing on PR comments

NIFI-614 more PR comments

This closes #222

Signed-off-by: jpercivall 


> Create a JMS ConnectionFactory controller service and refactor JMS processors 
> to use it
> ---
>
> Key: NIFI-614
> URL: https://issues.apache.org/jira/browse/NIFI-614
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.1.0
>Reporter: Michael Moser
>Assignee: Oleg Zhurakousky
>  Labels: JMS
> Fix For: 0.6.0
>
>
> It is difficult to extend the standard JMS processors to use a different JMS 
> provider besides the included ActiveMQ.  Improve the process of adding 
> support for other JMS providers.
> Create a JMS ConnectionFactoryService API in nifi-standard-services.  Create 
> an ActiveMQConnectionFactoryService with the ActiveMQ implementation in 
> nifi-standard-services.  Modify the JMS processors in 
> nifi-standard-processors to use a ConnectionFactoryService to pick the JMS 
> Provider to use.



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

[jira] [Commented] (NIFI-614) Create a JMS ConnectionFactory controller service and refactor JMS processors to use it

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-614 Added initial support for new style JMS

NIFI-614 finalized JMSConnectionFactoryProvider ControllerService

NIFI-614 finalized implementation of both Processors and ControllerService

NIFI-614 added initial documentation

NIFI-614 addressed PR comment with unused import and squashed

NIFI-614 added @OnDisabled method

NIFI-614 changed POMs to 0.6

NIFI-614 removed local .gitignore

NIFI-614 added support for parsing Tibco URL

NIFI-614 removed setting of jms message id

NIFI-614 addressed PR comments, fixed tests

NIFI-614 addressed latest PR comments

NIFI-614 second round of PR comments addressed

NIFI-614 3rd round of PR comments addressed

NIFI-614 finalizing on PR comments

NIFI-614 more PR comments

This closes #222

Signed-off-by: jpercivall 


> Create a JMS ConnectionFactory controller service and refactor JMS processors 
> to use it
> ---
>
> Key: NIFI-614
> URL: https://issues.apache.org/jira/browse/NIFI-614
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.1.0
>Reporter: Michael Moser
>Assignee: Oleg Zhurakousky
>  Labels: JMS
> Fix For: 0.6.0
>
>
> It is difficult to extend the standard JMS processors to use a different JMS 
> provider besides the included ActiveMQ.  Improve the process of adding 
> support for other JMS providers.
> Create a JMS ConnectionFactoryService API in nifi-standard-services.  Create 
> an ActiveMQConnectionFactoryService with the ActiveMQ implementation in 
> nifi-standard-services.  Modify the JMS processors in 
> nifi-standard-processors to use a ConnectionFactoryService to pick the JMS 
> Provider to use.



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

[jira] [Commented] (NIFI-614) Create a JMS ConnectionFactory controller service and refactor JMS processors to use it

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-614 Added initial support for new style JMS

NIFI-614 finalized JMSConnectionFactoryProvider ControllerService

NIFI-614 finalized implementation of both Processors and ControllerService

NIFI-614 added initial documentation

NIFI-614 addressed PR comment with unused import and squashed

NIFI-614 added @OnDisabled method

NIFI-614 changed POMs to 0.6

NIFI-614 removed local .gitignore

NIFI-614 added support for parsing Tibco URL

NIFI-614 removed setting of jms message id

NIFI-614 addressed PR comments, fixed tests

NIFI-614 addressed latest PR comments

NIFI-614 second round of PR comments addressed

NIFI-614 3rd round of PR comments addressed

NIFI-614 finalizing on PR comments

NIFI-614 more PR comments

This closes #222

Signed-off-by: jpercivall 


> Create a JMS ConnectionFactory controller service and refactor JMS processors 
> to use it
> ---
>
> Key: NIFI-614
> URL: https://issues.apache.org/jira/browse/NIFI-614
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.1.0
>Reporter: Michael Moser
>Assignee: Oleg Zhurakousky
>  Labels: JMS
> Fix For: 0.6.0
>
>
> It is difficult to extend the standard JMS processors to use a different JMS 
> provider besides the included ActiveMQ.  Improve the process of adding 
> support for other JMS providers.
> Create a JMS ConnectionFactoryService API in nifi-standard-services.  Create 
> an ActiveMQConnectionFactoryService with the ActiveMQ implementation in 
> nifi-standard-services.  Modify the JMS processors in 
> nifi-standard-processors to use a ConnectionFactoryService to pick the JMS 
> Provider to use.



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

[jira] [Commented] (NIFI-614) Create a JMS ConnectionFactory controller service and refactor JMS processors to use it

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-614 Added initial support for new style JMS

NIFI-614 finalized JMSConnectionFactoryProvider ControllerService

NIFI-614 finalized implementation of both Processors and ControllerService

NIFI-614 added initial documentation

NIFI-614 addressed PR comment with unused import and squashed

NIFI-614 added @OnDisabled method

NIFI-614 changed POMs to 0.6

NIFI-614 removed local .gitignore

NIFI-614 added support for parsing Tibco URL

NIFI-614 removed setting of jms message id

NIFI-614 addressed PR comments, fixed tests

NIFI-614 addressed latest PR comments

NIFI-614 second round of PR comments addressed

NIFI-614 3rd round of PR comments addressed

NIFI-614 finalizing on PR comments

NIFI-614 more PR comments

This closes #222

Signed-off-by: jpercivall 


> Create a JMS ConnectionFactory controller service and refactor JMS processors 
> to use it
> ---
>
> Key: NIFI-614
> URL: https://issues.apache.org/jira/browse/NIFI-614
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.1.0
>Reporter: Michael Moser
>Assignee: Oleg Zhurakousky
>  Labels: JMS
> Fix For: 0.6.0
>
>
> It is difficult to extend the standard JMS processors to use a different JMS 
> provider besides the included ActiveMQ.  Improve the process of adding 
> support for other JMS providers.
> Create a JMS ConnectionFactoryService API in nifi-standard-services.  Create 
> an ActiveMQConnectionFactoryService with the ActiveMQ implementation in 
> nifi-standard-services.  Modify the JMS processors in 
> nifi-standard-processors to use a ConnectionFactoryService to pick the JMS 
> Provider to use.



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

[jira] [Commented] (NIFI-1464) Refactor lifecycle code for Processors and other components

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1464 fixed OnScheduled invocation to pass ProcessContext

NIFI-1464 removed unused imports

Signed-off-by: joewitt 


> Refactor lifecycle code for Processors and other components
> ---
>
> Key: NIFI-1464
> URL: https://issues.apache.org/jira/browse/NIFI-1464
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> Similar lifecycle handling improvements that went in as part of the NIFI-1164 
> for ControllerServices, could/should be applied to other  components (e..g, 
> Processors).
> The improvements may also help to address NIFI-78 (may be without killing the 
> thread).



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

[jira] [Commented] (NIFI-1464) Refactor lifecycle code for Processors and other components

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1464 fixed OnScheduled invocation to pass ProcessContext

NIFI-1464 removed unused imports

Signed-off-by: joewitt 


> Refactor lifecycle code for Processors and other components
> ---
>
> Key: NIFI-1464
> URL: https://issues.apache.org/jira/browse/NIFI-1464
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> Similar lifecycle handling improvements that went in as part of the NIFI-1164 
> for ControllerServices, could/should be applied to other  components (e..g, 
> Processors).
> The improvements may also help to address NIFI-78 (may be without killing the 
> thread).



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

[jira] [Commented] (NIFI-1627) Funnels and Local Ports should not yield

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1627: Do not call context.yield for funnels and local ports; use batch 
size of 100 instead of 10 for local ports and funnels

Signed-off-by: joewitt 


> Funnels and Local Ports should not yield
> 
>
> Key: NIFI-1627
> URL: https://issues.apache.org/jira/browse/NIFI-1627
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-1627-Do-not-call-context.yield-for-funnels-and-.patch, 
> 0001-NIFI-1627-Do-not-call-context.yield-for-funnels-and-.patch
>
>
> Currently, funnels and local ports call context.yield() when they run out of 
> incoming data. However, the framework will already use the 'bored yield 
> duration' to yield as appropriate, so these components should not yield in 
> this case.



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

[jira] [Commented] (NIFI-1519) Upgrade Spark receiver bundle to Spark 1.6

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1519 upgraded to the latest version of Spark 1.6.0

Signed-off-by: Matt Burgess 


> Upgrade Spark receiver bundle to Spark 1.6
> --
>
> Key: NIFI-1519
> URL: https://issues.apache.org/jira/browse/NIFI-1519
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
>Priority: Minor
> Fix For: 0.6.0
>
>




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

[jira] [Commented] (NIFI-1481) NiFi CLI enhancement to get Environment Configurations

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1481 fixed a couple bugs in bash script for cygwin and when JAVA_HOME not 
set

Reviewed by Aldrin Piri (ald...@apache.org). This closes #277


> NiFi CLI enhancement to get Environment Configurations 
> ---
>
> Key: NIFI-1481
> URL: https://issues.apache.org/jira/browse/NIFI-1481
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 0.4.1
>Reporter: Puspendu Banerjee
>Assignee: Tony Kurc
>  Labels: CLI, features
> Fix For: 0.6.0
>
> Attachments: NIFI-1481.001.patch, env-nifi.bat
>
>
> A CLI enhancement is required to support tp gather environment information of 
> a running NiFi configuration.
> As suggested in NiFi-1462 , a preferable command line could be:
> $nifi.sh env



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

[jira] [Commented] (NIFI-1481) NiFi CLI enhancement to get Environment Configurations

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1481 support for dumping environment using nifi.sh env

Reviewed and amended (Amendments reviewed by Aldrin Piri (ald...@apache.org)) 
by Tony Kurc (tk...@apache.org). This closes #218


> NiFi CLI enhancement to get Environment Configurations 
> ---
>
> Key: NIFI-1481
> URL: https://issues.apache.org/jira/browse/NIFI-1481
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 0.4.1
>Reporter: Puspendu Banerjee
>Assignee: Tony Kurc
>  Labels: CLI, features
> Fix For: 0.6.0
>
> Attachments: NIFI-1481.001.patch, env-nifi.bat
>
>
> A CLI enhancement is required to support tp gather environment information of 
> a running NiFi configuration.
> As suggested in NiFi-1462 , a preferable command line could be:
> $nifi.sh env



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

[jira] [Commented] (NIFI-1588) ListHDFS to retaining wrong state in zookeeper

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1588: Reworked how ListHDFS store state so that only 2 timestamps are 
stored and no paths

Signed-off-by: joewitt 


> ListHDFS to retaining wrong state in zookeeper
> --
>
> Key: NIFI-1588
> URL: https://issues.apache.org/jira/browse/NIFI-1588
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 0.4.1
> Environment: latest 0.5.1
>Reporter: Matthew Clarke
>Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-1588-Reworked-how-ListHDFS-store-state-so-that-.patch, 
> 0001-NIFI-1588-Reworked-how-ListHDFS-store-state-so-that-.patch
>
>
> The expected state that should be retained by listHDFS processor is the last 
> modified timestamp.  The processor instead is retaining the filename and path 
> of every file it lists.  This results in excessive disk usage by zookeeper to 
> retain this filename based state.



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

[jira] [Commented] (NIFI-1587) ListHDFS processor does not properly clear state

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1587: Always poll state from State Manager when running ListHDFS instead 
of relying on local state over the cluster state

Signed-off-by: joewitt 


> ListHDFS processor does not properly clear state
> 
>
> Key: NIFI-1587
> URL: https://issues.apache.org/jira/browse/NIFI-1587
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.4.1
> Environment: latest 0.5.1 build
>Reporter: Matthew Clarke
>Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments: NIFI-1587.patch
>
>
> The ListHDFS processor successfully retains state in zookeeper; however, 
> state is not properly cleared.  You can right click, select "view state" , 
> and then "clear state"; however, regardless of what the state window shows 
> state is still retained in zookeeper.  If a new file that was not previously 
> seen before is listed by the ListHDFS processor, all previous state is 
> repopulated in the view state window. Files will not be picked up again 
> unless the ListHDFS processor is replaced by a new one.



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

[jira] [Commented] (NIFI-1606) When a component is removed, its state should be cleared in a background thread

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1606: Run the onComponentRemoved logic of state providers in a background 
thread

Signed-off-by: joewitt 


> When a component is removed, its state should be cleared in a background 
> thread
> ---
>
> Key: NIFI-1606
> URL: https://issues.apache.org/jira/browse/NIFI-1606
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments: NIFI-1606.patch
>
>
> Currently, when a Processor is removed from the graph, the State Manager's 
> onComponentRemoved method is called. This is called in a synchronous/blocking 
> manner. By default, the timeout to communicate with ZooKeeper is 30 seconds. 
> There are cases when the request can time out (for instance, due to improper 
> Kerberos configuration), and with a 30 second timeout, this often results in 
> nodes getting kicked out of the cluster.
> However, if the request fails, we simply log a warning and move on. As a 
> result, this synchronous network call should be moved to a background thread 
> to ensure that it does not interfere with the web request to remove the 
> component.



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

[jira] [Commented] (NIFI-1612) Remote Process Group is not using the configured Communications Timeout

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1612: Found a spot within the site-to-site client where the timeout was 
not utilized properly

Signed-off-by: joewitt 


> Remote Process Group is not using the configured Communications Timeout
> ---
>
> Key: NIFI-1612
> URL: https://issues.apache.org/jira/browse/NIFI-1612
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-1612-Do-not-ignore-Remote-Process-Group-s-timeo.patch, 
> 0002-NIFI-1612-Found-a-spot-within-the-site-to-site-clien.patch
>
>




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

[jira] [Commented] (NIFI-1612) Remote Process Group is not using the configured Communications Timeout

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1612: Do not ignore Remote Process Group's timeout configuration

Signed-off-by: joewitt 


> Remote Process Group is not using the configured Communications Timeout
> ---
>
> Key: NIFI-1612
> URL: https://issues.apache.org/jira/browse/NIFI-1612
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-1612-Do-not-ignore-Remote-Process-Group-s-timeo.patch, 
> 0002-NIFI-1612-Found-a-spot-within-the-site-to-site-clien.patch
>
>




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

[jira] [Commented] (NIFI-627) ControlRate processor does not accurately control the rate

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-627 removed flowfile penalization which could skew behavior when 
processor's Time Duration was less than Penalty Duration, improved over 
throttle penalization NIFI-990 corrected failure path NIFI-1329 refactored 
using FlowFileFilter to avoid repeatedly returning flowfiles to the input 
queue, producing misleading stats and excessive Tasks/Time used

Signed-off-by: joewitt 


> ControlRate processor does not accurately control the rate
> --
>
> Key: NIFI-627
> URL: https://issues.apache.org/jira/browse/NIFI-627
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.1.0
>Reporter: Michael Moser
>Assignee: Michael Moser
>Priority: Minor
> Fix For: 0.6.0
>
>
> Set a ControlRate processor to something like 5 KB per 1 sec.  Generate flow 
> files that are about 300 KB in size and feed a bunch to this processor.  This 
> should allow about 5 files through per 5 minutes.  But it allows a lot more 
> data through than it should.  The difference seems to get worse with really 
> low Time Duration values.  And people tend to think in number of bytes per 
> second so the temptation to set Time Duration to 1 sec is great.
> Also, if ControlRate has multiple input queues, it seems to output even more 
> data than it should.
> This seems to be caused by the code at the beginning of ControlRate 
> onTrigger().  Under some conditions when the number of files that are allowed 
> through per Time Duration is less than 1, the Throttle is being removed from 
> the throttleMap while it actually still should be in use.



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

[jira] [Commented] (NIFI-627) ControlRate processor does not accurately control the rate

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-627 minor formating adjustments and removed exception based handling 
logic. This closes #268.  This closes #274.

Signed-off-by: joewitt 


> ControlRate processor does not accurately control the rate
> --
>
> Key: NIFI-627
> URL: https://issues.apache.org/jira/browse/NIFI-627
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.1.0
>Reporter: Michael Moser
>Assignee: Michael Moser
>Priority: Minor
> Fix For: 0.6.0
>
>
> Set a ControlRate processor to something like 5 KB per 1 sec.  Generate flow 
> files that are about 300 KB in size and feed a bunch to this processor.  This 
> should allow about 5 files through per 5 minutes.  But it allows a lot more 
> data through than it should.  The difference seems to get worse with really 
> low Time Duration values.  And people tend to think in number of bytes per 
> second so the temptation to set Time Duration to 1 sec is great.
> Also, if ControlRate has multiple input queues, it seems to output even more 
> data than it should.
> This seems to be caused by the code at the beginning of ControlRate 
> onTrigger().  Under some conditions when the number of files that are allowed 
> through per Time Duration is less than 1, the Throttle is being removed from 
> the throttleMap while it actually still should be in use.



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

[jira] [Commented] (NIFI-990) ControlRate processor is missing failure relationship

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-627 removed flowfile penalization which could skew behavior when 
processor's Time Duration was less than Penalty Duration, improved over 
throttle penalization NIFI-990 corrected failure path NIFI-1329 refactored 
using FlowFileFilter to avoid repeatedly returning flowfiles to the input 
queue, producing misleading stats and excessive Tasks/Time used

Signed-off-by: joewitt 


> ControlRate processor is missing failure relationship
> -
>
> Key: NIFI-990
> URL: https://issues.apache.org/jira/browse/NIFI-990
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3.0
>Reporter: Michael Moser
>Assignee: Michael Moser
>Priority: Minor
>  Labels: newbie
> Fix For: 0.6.0
>
>
> The "Rate Control Attribute" property description says "The value of the 
> attribute referenced by this property must be a positive long, or the 
> FlowFile will be routed to failure".  The "success" relationship description 
> says "All FlowFiles are transferred to this relationship".  Which is correct?
> The code does try to transfer to a "failure" relationship, which is missing 
> from the getRelationships() Set.  So when the condition happens, the session 
> rolls back with an error that the "failure" relationship doesn't exist.
> Add the "failure" relationship and fix the "success" relationship description.



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

[jira] [Commented] (NIFI-1329) ControlRate processor should not be penalizing FlowFiles

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-627 removed flowfile penalization which could skew behavior when 
processor's Time Duration was less than Penalty Duration, improved over 
throttle penalization NIFI-990 corrected failure path NIFI-1329 refactored 
using FlowFileFilter to avoid repeatedly returning flowfiles to the input 
queue, producing misleading stats and excessive Tasks/Time used

Signed-off-by: joewitt 


> ControlRate processor should not be penalizing FlowFiles
> 
>
> Key: NIFI-1329
> URL: https://issues.apache.org/jira/browse/NIFI-1329
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.4.1
>Reporter: Matthew Clarke
>Assignee: Michael Moser
>Priority: Minor
> Fix For: 0.6.0
>
>
> The controlRate processor currently penalizes all FlowFiles still on input 
> queue if flow rate has been reached.  Those penalized FlowFiles will not be 
> processed by the ControlRate processor again until that penalization has 
> expired causing an impact on the desired controlled throughput of the 
> processor. 
> Example ControlRate processor setup:
> Penalty duration left at default 30 sec
> Strategy set to FlowFile count
> Max rate set at 100 
> time duration set to 1 sec
> Let say the input queue to this processor has 2000 files dumped in it. The 
> ControlRate processor will read all 2000 files, allow 100 through and 
> penalize the other 1900 fro 30 seconds.  Assuming no other files enter queue 
> at this point, after 30 seconds another 100 will pass and 1800 will be 
> penalized again.  This pattern continues
> You can work around this defect by changing the penalization default from 30 
> to say 1 sec.
> Why is the "In" stat reflecting reading all files on input queue when only 
> 100 files are actually passing through processor?  <-- this leads to 
> confusion for the users.
> Why is penalty being applied here?



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

[jira] [Commented] (NIFI-1622) Not using appropriate NAR class loader when calling Processor Lifecycle methods

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1622: Ensure that the Nar Context Class Loader is used when calling 
Processor lifecycle methods

Signed-off-by: joewitt 


> Not using appropriate NAR class loader when calling Processor Lifecycle 
> methods
> ---
>
> Key: NIFI-1622
> URL: https://issues.apache.org/jira/browse/NIFI-1622
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.0
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-1622-Ensure-that-the-Nar-Context-Class-Loader-i.patch
>
>
> Since NIFI-1464 was merged to master, I have seen problems starting the 
> PutKafka processor. It appears that the NAR ClassLoader was not being 
> properly applied, per the stack trace:
> 2016-03-11 14:22:53,967 ERROR [pool-25-thread-5] 
> o.a.n.controller.StandardProcessorNode Failed to invoke @OnScheduled method 
> due to java.lang.RuntimeException: Failed while executing one of processor's 
> lifecycle tasks (OnScheduled or OnUnscheduled).
> java.lang.RuntimeException: Failed while executing one of processor's 
> lifecycle tasks (OnScheduled or OnUnscheduled).
> at 
> org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1398)
>  ~[nifi-framework-core-0.6.0-SNAPSHOT.jar:0.6.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardProcessorNode.access$100(StandardProcessorNode.java:91)
>  ~[nifi-framework-core-0.6.0-SNAPSHOT.jar:0.6.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1.run(StandardProcessorNode.java:1246)
>  ~[nifi-framework-core-0.6.0-SNAPSHOT.jar:0.6.0-SNAPSHOT]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_60]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [na:1.8.0_60]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_60]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>  [na:1.8.0_60]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_60]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
> Caused by: java.util.concurrent.ExecutionException: 
> java.lang.reflect.InvocationTargetException
> at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
> [na:1.8.0_60]
> at java.util.concurrent.FutureTask.get(FutureTask.java:206) 
> [na:1.8.0_60]
> at 
> org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1383)
>  ~[nifi-framework-core-0.6.0-SNAPSHOT.jar:0.6.0-SNAPSHOT]
> ... 9 common frames omitted
> Caused by: java.lang.reflect.InvocationTargetException: null
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_60]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_60]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_60]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_60]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:137)
>  ~[nifi-framework-core-0.6.0-SNAPSHOT.jar:0.6.0-SNAPSHOT]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:125)
>  ~[nifi-framework-core-0.6.0-SNAPSHOT.jar:0.6.0-SNAPSHOT]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:70)
>  ~[nifi-framework-core-0.6.0-SNAPSHOT.jar:0.6.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1250)
>  ~[nifi-framework-core-0.6.0-SNAPSHOT.jar:0.6.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1246)
>  ~[nifi-framework-core-0.6.0-SNAPSHOT.jar:0.6.0-SNAPSHOT]
> ... 6 common frames omitted
> Caused by: java.lang.ExceptionInInitializerError: null
> at 
> 

[jira] [Commented] (NIFI-1464) Refactor lifecycle code for Processors and other components

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1464 addressed latest PR comments

NIFI-1464 polishing


> Refactor lifecycle code for Processors and other components
> ---
>
> Key: NIFI-1464
> URL: https://issues.apache.org/jira/browse/NIFI-1464
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> Similar lifecycle handling improvements that went in as part of the NIFI-1164 
> for ControllerServices, could/should be applied to other  components (e..g, 
> Processors).
> The improvements may also help to address NIFI-78 (may be without killing the 
> thread).



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

[jira] [Commented] (NIFI-1464) Refactor lifecycle code for Processors and other components

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1464 addressed PR comments from @apiri and @markap14


> Refactor lifecycle code for Processors and other components
> ---
>
> Key: NIFI-1464
> URL: https://issues.apache.org/jira/browse/NIFI-1464
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> Similar lifecycle handling improvements that went in as part of the NIFI-1164 
> for ControllerServices, could/should be applied to other  components (e..g, 
> Processors).
> The improvements may also help to address NIFI-78 (may be without killing the 
> thread).



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

[jira] [Commented] (NIFI-1464) Refactor lifecycle code for Processors and other components

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1464 fixed admin guide


> Refactor lifecycle code for Processors and other components
> ---
>
> Key: NIFI-1464
> URL: https://issues.apache.org/jira/browse/NIFI-1464
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> Similar lifecycle handling improvements that went in as part of the NIFI-1164 
> for ControllerServices, could/should be applied to other  components (e..g, 
> Processors).
> The improvements may also help to address NIFI-78 (may be without killing the 
> thread).



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

[jira] [Commented] (NIFI-1464) Refactor lifecycle code for Processors and other components

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1464 ensured that OnUnscheduled is treated the same as OnScheduled

NIFI-1464 polished javadocs, error messages and docs


> Refactor lifecycle code for Processors and other components
> ---
>
> Key: NIFI-1464
> URL: https://issues.apache.org/jira/browse/NIFI-1464
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> Similar lifecycle handling improvements that went in as part of the NIFI-1164 
> for ControllerServices, could/should be applied to other  components (e..g, 
> Processors).
> The improvements may also help to address NIFI-78 (may be without killing the 
> thread).



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

[jira] [Commented] (NIFI-1464) Refactor lifecycle code for Processors and other components

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1464 refactored the latest commit


> Refactor lifecycle code for Processors and other components
> ---
>
> Key: NIFI-1464
> URL: https://issues.apache.org/jira/browse/NIFI-1464
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> Similar lifecycle handling improvements that went in as part of the NIFI-1164 
> for ControllerServices, could/should be applied to other  components (e..g, 
> Processors).
> The improvements may also help to address NIFI-78 (may be without killing the 
> thread).



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

[jira] [Commented] (NIFI-1464) Refactor lifecycle code for Processors and other components

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1464, Refactored Processor's life-cycle operation sequence
* Simplified and cleaned StandardProcessScheduler.start/stopProcessor methods
* Added stop/start operations to ProcessorNode.
* Removed unnecessary synchronization blocks related to ScheduledState in favor 
of enforcing order and idempotency via CAS operations. Those synchronization 
blocks were causing intermittent deadlocks whenever @OnScheduled blocks 
indefinitely.
* Added support for stopping the service when @OnScheduled operation hangs.
* Fixed the order of life-cycle operation invocation ensuring that each 
operation can *only* be invoked at the appropriate time
* Removed unnecessary locks from StandardProcessNode since Atomic variables are 
used.
* Removed calls to @OnStopped from ContinuallyRunningProcessTask while ensuring 
that procesor's full shut down in implementation of 
StandardProcessorNode.stop() method.
* Removed dead code
* Added comprehensive tests suite that covers 95% of Processor's life-cycle 
operations within the scope of FlowController, StandardProcesssScheduler and 
StandardProcessNode
* Improved and added javadocs on covered operations with detailed explanations.


> Refactor lifecycle code for Processors and other components
> ---
>
> Key: NIFI-1464
> URL: https://issues.apache.org/jira/browse/NIFI-1464
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> Similar lifecycle handling improvements that went in as part of the NIFI-1164 
> for ControllerServices, could/should be applied to other  components (e..g, 
> Processors).
> The improvements may also help to address NIFI-78 (may be without killing the 
> thread).



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

[jira] [Commented] (NIFI-1619) PutElasticSearch throws FlowFileHandlingException when id attribute is missing

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1619: Fix Elasticsearch processor bug when flow file missing ID attribute

This closes #269

Signed-off-by: Aldrin Piri 


> PutElasticSearch throws FlowFileHandlingException when id attribute is missing
> --
>
> Key: NIFI-1619
> URL: https://issues.apache.org/jira/browse/NIFI-1619
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.5.1
>Reporter: Jim Wagoner
>Assignee: Matt Burgess
>Priority: Minor
>  Labels: easyfix
> Fix For: 0.6.0
>
>
> When the processor can't find the id_attribute on the FlowFile while trying 
> to be added to the Bulk Request it is transferred to failure relationship. 
> The issue is after this happens the FlowFile is still added to the Bulk 
> Request even though a invalid id will be used during the insert. This will 
> cause the a failure to be returned to the BulkResponse and a attempt to 
> transfer the already transferred FlowFile throws a FlowFileHandlingException .
> Looks like a "continue;" added to line 178 would solve this issue.
> STACK:
> 2016-03-11 07:49:39,053 ERROR [Timer-Driven Process Thread-12] 
> o.a.n.p.elasticsearch.PutElasticsearch 
> PutElasticsearch[id=9a22e93f-03d8-445f-95b8-7979d0016ee7] No value in 
> identifier attribute ${metadataId} for 
> StandardFlowFileRecord[uuid=2fad6fa6-f773-4ac1-b2c3-788e398122a3,claim=StandardContentClaim
>  [resourceClaim=StandardResourceClaim[id=1457700558252-17754, 
> container=default, section=346], offset=648997, 
> length=7283],offset=0,name=ce9f46e6-c89b-46d0-bede-bd111d05380e.xml,size=7283]
> 2016-03-11 07:49:39,081 ERROR [Timer-Driven Process Thread-12] 
> o.a.n.p.elasticsearch.PutElasticsearch 
> PutElasticsearch[id=9a22e93f-03d8-445f-95b8-7979d0016ee7] Failed to insert 
> into Elasticsearch due to 
> StandardFlowFileRecord[uuid=2fad6fa6-f773-4ac1-b2c3-788e398122a3,claim=StandardContentClaim
>  [resourceClaim=StandardResourceClaim[id=1457700558252-17754, 
> container=default, section=346], offset=648997, 
> length=7283],offset=0,name=ce9f46e6-c89b-46d0-bede-bd111d05380e.xml,size=7283]
>  is already marked for transfer: 
> org.apache.nifi.processor.exception.FlowFileHandlingException: 
> StandardFlowFileRecord[uuid=2fad6fa6-f773-4ac1-b2c3-788e398122a3,claim=StandardContentClaim
>  [resourceClaim=StandardResourceClaim[id=1457700558252-17754, 
> container=default, section=346], offset=648997, 
> length=7283],offset=0,name=ce9f46e6-c89b-46d0-bede-bd111d05380e.xml,size=7283]
>  is already marked for transfer
> 2016-03-11 07:49:39,105 ERROR [Timer-Driven Process Thread-12] 
> o.a.n.p.elasticsearch.PutElasticsearch
> org.apache.nifi.processor.exception.FlowFileHandlingException: 
> StandardFlowFileRecord[uuid=2fad6fa6-f773-4ac1-b2c3-788e398122a3,claim=StandardContentClaim
>  [resourceClaim=StandardResourceClaim[id=1457700558252-17754, 
> container=default, section=346], offset=648997, 
> length=7283],offset=0,name=ce9f46e6-c89b-46d0-bede-bd111d05380e.xml,size=7283]
>  is already marked for transfer
> at 
> org.apache.nifi.controller.repository.StandardProcessSession.validateRecordState(StandardProcessSession.java:2369)
>  ~[na:na]
> at 
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1782)
>  ~[na:na]
> at 
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1777)
>  ~[na:na]
> at 
> org.apache.nifi.processors.elasticsearch.PutElasticsearch.onTrigger(PutElasticsearch.java:171)
>  ~[nifi-elasticsearch-processors-0.5.1.jar:0.5.1]
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  [nifi-api-0.5.1.jar:0.5.1]
> at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1139)
>  [nifi-framework-core-0.5.1.jar:0.5.1]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:139)
>  [nifi-framework-core-0.5.1.jar:0.5.1]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:49)
>  [nifi-framework-core-0.5.1.jar:0.5.1]
> at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:124)
>  [nifi-framework-core-0.5.1.jar:0.5.1]
> at 
> 

[jira] [Commented] (NIFI-1511) Incorporate Groovy unit tests as part of the build instead of via profile

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1511 we now ensure groovy eclipse compiler is only used during testCompile 
goal

This closes #270

Signed-off-by: Matt Burgess 


> Incorporate Groovy unit tests as part of the build instead of via profile
> -
>
> Key: NIFI-1511
> URL: https://issues.apache.org/jira/browse/NIFI-1511
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.0
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
> Fix For: 0.6.0
>
>
> From the mailing list:
> {quote}
> Recommend *not* running the groovy tests.  They set the groovy
> dependency to test scope which means groovy ends up not supported in
> the convenience binary.
> # Verify the build works including release audit tool (RAT) checks
>   cd nifi-0.5.0
>   mvn clean install -Pcontrib-check
> We should work to get the groovy stuff into the build without needing
> profile activation if they should be the norm.
> {quote}



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

[jira] [Commented] (NIFI-899) ListenUDP attempts to transfer a FlowFile that is no longer part of the session

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-899 Rewrite of ListenUDP to use new listener framework, includes the 
following changes:
- Adding Network Interface property to AbstractListenEventProcessor and 
ListenSyslog
- Adding sending host and sending port to DatagramChannelDispatcher
- Creation of common base class AbstractListenEventBatchingProcessor
- Refactor of ListenUDP, ListenTCP, and ListenRELP to all extend from 
AbstractListenEventBatchingProcessor
- Changing DatagramChannelDispatcher, socket handlers, and RELP handler to use 
offer() when queueing instead of put(), and log an error if the offer failed

This closes #266


> ListenUDP attempts to transfer a FlowFile that is no longer part of the 
> session
> ---
>
> Key: NIFI-899
> URL: https://issues.apache.org/jira/browse/NIFI-899
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Bende
>Assignee: Bryan Bende
> Fix For: 0.6.0
>
>
> While testing ListenUDP receiving events from syslogd, started and stopped 
> the processor a few times, and eventually got this error:
> {code}
> 2015-08-27 13:26:36,210 ERROR [Timer-Driven Process Thread-2] 
> o.a.nifi.processors.standard.ListenUDP 
> [ListenUDP[id=4ceafe26-5f31-4f94-bf86-1c327db11b7e]] Failed to transfer flow 
> files or commit session...rolled back
> org.apache.nifi.processor.exception.FlowFileHandlingException: 
> StandardFlowFileRecord[uuid=746c09c2-c150-4007-8107-b0b5eb9ecc5b,claim=org.apache.nifi.controller.repository.claim.StandardContentClaim@fb2f16f4,offset=0,name=141981000764924,size=140]
>  is not known to StandardProcessSession[id=4808]
>   at 
> org.apache.nifi.controller.repository.StandardProvenanceReporter.verifyFlowFileKnown(StandardProvenanceReporter.java:97)
>  ~[na:na]
>   at 
> org.apache.nifi.controller.repository.StandardProvenanceReporter.receive(StandardProvenanceReporter.java:123)
>  ~[na:na]
>   at 
> org.apache.nifi.controller.repository.StandardProvenanceReporter.receive(StandardProvenanceReporter.java:118)
>  ~[na:na]
>   at 
> org.apache.nifi.controller.repository.StandardProvenanceReporter.receive(StandardProvenanceReporter.java:113)
>  ~[na:na]
>   at 
> org.apache.nifi.controller.repository.StandardProvenanceReporter.receive(StandardProvenanceReporter.java:103)
>  ~[na:na]
>   at 
> org.apache.nifi.processors.standard.ListenUDP.transferFlowFiles(ListenUDP.java:515)
>  [nifi-standard-processors-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> org.apache.nifi.processors.standard.ListenUDP.onTrigger(ListenUDP.java:497) 
> [nifi-standard-processors-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1077)
>  [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:127)
>  [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:49)
>  [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:119)
>  [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_45]
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_45]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_45]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_45]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_45]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_45]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_45]
> {code}
> The only configuration set on the processor was the Port and FlowFile Per 
> Datagram to true, everything else was defaults.



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

[jira] [Commented] (NIFI-1491) NPE error on startup because of file permission issues

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1491 Deprecated existing method and added new one throwing eception

Reviewed and amended (to add javadoc @deprecation link and to carry forward 
other deprecated methods) by Tony Kurc (tk...@apache.org). This closes #227


> NPE error on startup because of file permission issues
> --
>
> Key: NIFI-1491
> URL: https://issues.apache.org/jira/browse/NIFI-1491
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.4.1, 0.5.1
>Reporter: Matthew Clarke
>Assignee: Tony Kurc
>Priority: Minor
> Fix For: 0.6.0
>
>
>  A node that was part of a NiFi cluster would not start.  It immediately 
> through this error in the app log:
> 2016-02-08 15:26:46,617 DEBUG [main] org.apache.nifi.BootstrapListener 
> Awaiting response from Bootstrap...
> 2016-02-08 15:26:46,629 INFO [main] org.apache.nifi.BootstrapListener 
> Successfully initiated communication with Bootstrap
> 2016-02-08 15:26:46,635 ERROR [main] org.apache.nifi.NiFi Failure to launch 
> NiFi due to java.lang.NullPointerException
> java.lang.NullPointerException: null
> at org.apache.nifi.util.FileUtils.deleteFilesInDir(FileUtils.java:141) 
> ~[nifi-nar-utils-1.1.1.0-12.jar:1.1.1.0-12]
> at org.apache.nifi.NiFi.(NiFi.java:98) 
> ~[nifi-runtime-1.1.1.0-12.jar:1.1.1.0-12]
> at org.apache.nifi.NiFi.main(NiFi.java:227) 
> ~[nifi-runtime-1.1.1.0-12.jar:1.1.1.0-12]
> 2016-02-08 15:26:46,637 INFO [Thread-1] org.apache.nifi.NiFi Initiating 
> shutdown of Jetty web server...
> 2016-02-08 15:26:46,638 INFO [Thread-1] org.apache.nifi.NiFi Jetty web server 
> shutdown completed (nicely or otherwise).
> Turns out the problem was permission related to files in the NiFi work dir.
> NiFi should present a better error to the user.



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

[jira] [Commented] (NIFI-1518) InferAvroSchema does not have option to set CSV delimiter

[ASF subversion and git services (JIRA)]

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

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

Commit 784f2a2c2094ae30b7f07a80cf41b1b548929211 in nifi's branch 
refs/heads/master from [~michal.klempa]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=784f2a2 ]

NIFI-1518 InferAvroSchema note has an option to set CSV delimiter

Reviewed (and amended based on acknowledgement in PR review) by Tony Kurc 
(tk...@apache.org). This closes #235.


> InferAvroSchema does not have option to set CSV delimiter
> -
>
> Key: NIFI-1518
> URL: https://issues.apache.org/jira/browse/NIFI-1518
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.5.0, 0.5.1
>Reporter: Michal Klempa
>Assignee: Tony Kurc
> Fix For: 0.6.0
>
>
> InferAvroSchema processor lacks the property CSV delimiter, effectively 
> limiting CSV header to use ',' as delimiter and limiting CSV to Avro data 
> flow to work only with CSV files with ',' as delimiter (when schema is 
> unknown and should be derived from CSV header).
> This parameter is present at ConvertCSVToAvro processor, so this code should 
> be transliterated.



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

[jira] [Commented] (NIFI-1563) Remove storage of components' stats and bulletins from NCM

[ASF subversion and git services (JIRA)]

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

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

Commit 19e8d7db93f0e3fd3fbcb83e62c564ffe95fba11 in nifi's branch 
refs/heads/NIFI-1563 from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=19e8d7d ]

NIFI-1563:
- Wiring up new endpoints and updated core.
- Code clean up.


> Remove storage of components' stats and bulletins from NCM
> --
>
> Key: NIFI-1563
> URL: https://issues.apache.org/jira/browse/NIFI-1563
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Currently, each node in a cluster sends a period heartbeat that contains the 
> stats for all components in the node. This happens every 5 seconds by 
> default. This results in quite a lot of chatter between the NCM and nodes. It 
> made sense to take this approach when the clustering concept was designed 
> because there were no Process Groups, and we had no notion of merging 
> responses from nodes for a web request.
> However, now we should replicate the request to all nodes and then merge the 
> responses on demand, rather than storing this information on the NCM. This 
> requires far less bandwidth because we only need to pull the stats for a 
> particular Process Group and only on demand instead of every 5 seconds. 
> Additionally, this is laying groundwork for the Zero-Master clustering that 
> we want to have in place for 1.0.0.
> In order to remove the stats from the NCM, we will also need to remove the 
> bulletins and stats history. These requests will all need to be federated and 
> the responses merged on-demand.



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

[jira] [Commented] (NIFI-1003) Ability to auto-terminate relationship connections for a processor

[ASF subversion and git services (JIRA)]

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

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

Commit 73e168e954ad8304bbd7f4a078031c106cf2e8e3 in nifi's branch 
refs/heads/master from Pasqualino Ferrentino
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=73e168e ]

NIFI-1003 A relationship can be auto-terminable. In this case the processor 
will auto-terminate the relationship and allow the user to run it even if he 
does not connect those relationships and does not terminate them.

This closes #217

Signed-off-by: Aldrin Piri 


> Ability to auto-terminate relationship connections for a processor
> --
>
> Key: NIFI-1003
> URL: https://issues.apache.org/jira/browse/NIFI-1003
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Affects Versions: 0.3.0
> Environment: New processor with many dynamically-generated 
> relationships
>Reporter: Rick Braddy
>Priority: Minor
>
> Need a way to auto-terminate relationships without user intervention; that 
> is, change the default behavior of a processor to automatically 
> self-terminate connections for relationships when they are created.  
> Ideally, this would be possible to set at processor init() time, so all 
> relationships on the processor will be auto-terminated by default. Since this 
> primarily applies to relationships added dynamically, it could also be called 
> via the ProcessContext object during onTrigger().
> context.autoTerminateConnections( boolean selfAutoTerminate);
> where calling autoTerminateConnections( true ) would cause future 
> relationships to be auto-terminated by default (instead of the default, which 
> is to require manually setting auto-termination).



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

[jira] [Commented] (NIFI-1488) Add Kerberos Support to HBase processors

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1488 Adjusting unused imports and adding license exclusions to RAT plugin 
for build.


> Add Kerberos Support to HBase processors
> 
>
> Key: NIFI-1488
> URL: https://issues.apache.org/jira/browse/NIFI-1488
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.4.0, 0.4.1
>Reporter: Bryan Bende
>Assignee: Ricky Saltzer
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-1488-Adjusting-unused-imports-and-adding-licens.patch
>
>
> Our current HBase integration does not support communicating with a 
> Kerberized HBase install. We should support this just like we do for the HDFS 
> processors.



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

[jira] [Commented] (NIFI-15) When restoring Swap Files, should detect corrupt swap file (EOFException) and remove it

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-15: Address issue where incomplete swap files can result in continually 
attempting to swap in data without ever being successful

Signed-off-by: Aldrin Piri 


> When restoring Swap Files, should detect corrupt swap file (EOFException) and 
> remove it
> ---
>
> Key: NIFI-15
> URL: https://issues.apache.org/jira/browse/NIFI-15
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-15-Address-issue-where-incomplete-swap-files-ca.patch, 
> 0001-NIFI-15-Address-issue-where-incomplete-swap-files-ca.patch
>
>
> Otherwise, we get errors in the logs and we keep the Content that is 
> referenced by the FlowFiles that we were able to read.



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

[jira] [Commented] (NIFI-1563) Remove storage of components' stats and bulletins from NCM

[ASF subversion and git services (JIRA)]

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

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

Commit 7a6dc4a7ec36025ba4719ec0990ee0d514630d44 in nifi's branch 
refs/heads/NIFI-1563 from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=7a6dc4a ]

NIFI-1563:
- Introducing endpoints for accessing individual component status.


> Remove storage of components' stats and bulletins from NCM
> --
>
> Key: NIFI-1563
> URL: https://issues.apache.org/jira/browse/NIFI-1563
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Currently, each node in a cluster sends a period heartbeat that contains the 
> stats for all components in the node. This happens every 5 seconds by 
> default. This results in quite a lot of chatter between the NCM and nodes. It 
> made sense to take this approach when the clustering concept was designed 
> because there were no Process Groups, and we had no notion of merging 
> responses from nodes for a web request.
> However, now we should replicate the request to all nodes and then merge the 
> responses on demand, rather than storing this information on the NCM. This 
> requires far less bandwidth because we only need to pull the stats for a 
> particular Process Group and only on demand instead of every 5 seconds. 
> Additionally, this is laying groundwork for the Zero-Master clustering that 
> we want to have in place for 1.0.0.
> In order to remove the stats from the NCM, we will also need to remove the 
> bulletins and stats history. These requests will all need to be federated and 
> the responses merged on-demand.



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

[jira] [Commented] (NIFI-1563) Remove storage of components' stats and bulletins from NCM

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1563: Bug fixes; code cleanup; replicate requests to bulletin board 
endpoint


> Remove storage of components' stats and bulletins from NCM
> --
>
> Key: NIFI-1563
> URL: https://issues.apache.org/jira/browse/NIFI-1563
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Currently, each node in a cluster sends a period heartbeat that contains the 
> stats for all components in the node. This happens every 5 seconds by 
> default. This results in quite a lot of chatter between the NCM and nodes. It 
> made sense to take this approach when the clustering concept was designed 
> because there were no Process Groups, and we had no notion of merging 
> responses from nodes for a web request.
> However, now we should replicate the request to all nodes and then merge the 
> responses on demand, rather than storing this information on the NCM. This 
> requires far less bandwidth because we only need to pull the stats for a 
> particular Process Group and only on demand instead of every 5 seconds. 
> Additionally, this is laying groundwork for the Zero-Master clustering that 
> we want to have in place for 1.0.0.
> In order to remove the stats from the NCM, we will also need to remove the 
> bulletins and stats history. These requests will all need to be federated and 
> the responses merged on-demand.



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

[jira] [Commented] (NIFI-1563) Remove storage of components' stats and bulletins from NCM

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1563: Refactored the StatusDTO objects into 
StatusDTO, StatusSnapshotDTO, 
NodeStatusSnapshotDTO objects


> Remove storage of components' stats and bulletins from NCM
> --
>
> Key: NIFI-1563
> URL: https://issues.apache.org/jira/browse/NIFI-1563
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Currently, each node in a cluster sends a period heartbeat that contains the 
> stats for all components in the node. This happens every 5 seconds by 
> default. This results in quite a lot of chatter between the NCM and nodes. It 
> made sense to take this approach when the clustering concept was designed 
> because there were no Process Groups, and we had no notion of merging 
> responses from nodes for a web request.
> However, now we should replicate the request to all nodes and then merge the 
> responses on demand, rather than storing this information on the NCM. This 
> requires far less bandwidth because we only need to pull the stats for a 
> particular Process Group and only on demand instead of every 5 seconds. 
> Additionally, this is laying groundwork for the Zero-Master clustering that 
> we want to have in place for 1.0.0.
> In order to remove the stats from the NCM, we will also need to remove the 
> bulletins and stats history. These requests will all need to be federated and 
> the responses merged on-demand.



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

[jira] [Commented] (NIFI-1573) Allow programmatic to a Processor's name

[ASF subversion and git services (JIRA)]

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

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

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

Merge branch 'NIFI-1573' of https://github.com/rpmiskin/nifi into NIFI-1573


> Allow programmatic to a Processor's name
> 
>
> Key: NIFI-1573
> URL: https://issues.apache.org/jira/browse/NIFI-1573
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Richard Miskin
>Priority: Minor
>
> As discussed on the dev list there are use cases where accessing a 
> Processor's as part of the configuration can be helpful.



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

[jira] [Commented] (NIFI-1573) Allow programmatic to a Processor's name

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1573 Allow programmatic access to a Processor's name


> Allow programmatic to a Processor's name
> 
>
> Key: NIFI-1573
> URL: https://issues.apache.org/jira/browse/NIFI-1573
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Richard Miskin
>Priority: Minor
>
> As discussed on the dev list there are use cases where accessing a 
> Processor's as part of the configuration can be helpful.



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

[jira] [Commented] (NIFI-1509) Support AWS Lambda Processor

[ASF subversion and git services (JIRA)]

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

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

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

Merge branch 'nifi-1509' of https://github.com/mans2singh/nifi into NIFI-1509


> Support AWS Lambda Processor
> 
>
> Key: NIFI-1509
> URL: https://issues.apache.org/jira/browse/NIFI-1509
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: 0.5.0
> Environment: all
>Reporter: Mans Singh
>Assignee: Mans Singh
>Priority: Minor
>  Labels: aws, lambda, streaming
> Fix For: 0.6.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Support aws lambda put processor



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

[jira] [Commented] (NIFI-1600) Unable to connect to Remote Process Group

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1600: Ensure that if we move a RemoteProcessGroup, it also updates the 
Parent Process Group of the ports


> Unable to connect to Remote Process Group
> -
>
> Key: NIFI-1600
> URL: https://issues.apache.org/jira/browse/NIFI-1600
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework, Core UI
>Reporter: Matt Gilman
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-1600-Ensure-that-if-we-move-a-RemoteProcessGrou.patch
>
>
> Unable to connect to a Remote Process Group when it has been moved from a sub 
> Process Group. A error message states:
> {noformat}
> Cannot add Connection to Process Group because its destination does not 
> belong to this Process Group
> {noformat}



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

[jira] [Commented] (NIFI-1534) PutKafka fails with batching and Run Duration > 0

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1534 removed SupportsBatching annotation from PutKafka

Signed-off-by: Matt Burgess 

This closes #249


> PutKafka fails with batching and Run Duration > 0
> -
>
> Key: NIFI-1534
> URL: https://issues.apache.org/jira/browse/NIFI-1534
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> The following error shows up in the bulletin
> {code}
> PutKafka[id=80e8946f-349c-4716-9da9-5e766582f788] Failed to process session 
> due to org.apache.nifi.processor.exception.FlowFileHandlingException: 
> StandardFlowFileRecord[uuid=27030bf8-c217-4b59-a0ba-46f1b30ff093,claim=StandardContentClaim
>  [resourceClaim=StandardResourceClaim[id=1455807429050-246, 
> container=default, section=246], offset=563929, 
> length=431],offset=0,name=hh77.33,size=431] is not known in this session
> {code}
> After some debugging I also see this
> {code}
> ERROR [Timer-Driven Process Thread-14] o.apache.nifi.processors.kafka.PutKafka
> org.apache.nifi.processor.exception.FlowFileHandlingException: 
> StandardFlowFileRecord[uuid=dd373d71-ebd2-432e-bcf5-9980d7df4da4,claim=StandardContentClaim
>  [resourceClaim=StandardResourceClaim[id=1454688235111-5, container=content2, 
> section=5], offset=0, length=4778852],offset=0,name=boo,size=4778852] 
> transfer relationship not specified
> at 
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:210)
>  
> at 
> org.apache.nifi.controller.repository.StandardProcessSession.commit(StandardProcessSession.java:280)
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:179)
> . . . .
> {code}



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

[jira] [Commented] (NIFI-1420) Splunk Processors

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1420 Adding Splunk bundle containing PutSplunk, and GetSplunk, and adding 
a ListenTCP processor to standard processors. Refactored internal code from 
PutSyslog to create a generic AbstractPutEventProcessor which PutSplunk extends 
from.

This closes #233


> Splunk Processors
> -
>
> Key: NIFI-1420
> URL: https://issues.apache.org/jira/browse/NIFI-1420
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 0.6.0
>
>
> To continue improving NiFi's ability to collect logs, a good integration 
> point would be to have a processor that could listen for data from a Splunk 
> forwarder (https://docs.splunk.com/Splexicon:Universalforwarder). Being able 
> to push log messages to Splunk would also be useful.
> Splunk provides an SDK that may be helpful:
> https://github.com/splunk/splunk-sdk-java 



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

[jira] [Commented] (NIFI-1595) ReflectionUtils doesn't take into account "bridge" methods when checking if method is annotated

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1595 fixed ReflectionUtils to honor bridge methods
Refactored and simplified ReflectionUtils while at it
Added ReflectionUtilsTest

This closes #260.

Signed-off-by: Aldrin Piri 
With adjustments to formatting and whitespace.

Signed-off-by: Aldrin Piri 


> ReflectionUtils doesn't take into account "bridge" methods when checking if 
> method is annotated
> ---
>
> Key: NIFI-1595
> URL: https://issues.apache.org/jira/browse/NIFI-1595
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> When extending from parameterized class some times compiler feels there is a 
> need to generate a synthetic “bridge” method modeled after the one in super 
> class. The issue is that annotations (if any) are not propagated to the 
> synthetic method and not visible when reflecting on such method, essentially 
> creating a condition where a standard lifecycle method (e.g., OnStopped) is 
> not executed.



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

[jira] [Commented] (NIFI-1596) ExecuteSQL Error Creating Schema

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1596: ExecuteSQL Error Creating Schema


> ExecuteSQL Error Creating Schema
> 
>
> Key: NIFI-1596
> URL: https://issues.apache.org/jira/browse/NIFI-1596
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Bende
>Assignee: Matt Burgess
> Fix For: 0.6.0
>
>
> It was reported that after upgrading to 0.5.1, ExecuteSQL was no longer 
> working against Oracle and MS SQL, in the same scenario that had previously 
> worked against 0.4.1.
> ERROR [Timer-Driven Process Thread-8] o.a.nifi.processors.standard.ExecuteSQL
> org.apache.avro.SchemaParseException: Empty name
>   at org.apache.avro.Schema.validateName(Schema.java:1076) ~[na:na]
>   at org.apache.avro.Schema.access$200(Schema.java:79) ~[na:na]
>   at org.apache.avro.Schema$Name.(Schema.java:436) ~[na:na]
>   at org.apache.avro.Schema.createRecord(Schema.java:145) ~[na:na]
>   at 
> org.apache.avro.SchemaBuilder$RecordBuilder.fields(SchemaBuilder.java:1732) 
> ~[na:na]
>   at 
> org.apache.nifi.processors.standard.util.JdbcCommon.createSchema(JdbcCommon.java:138)
>  ~[na:na]
>   at 
> org.apache.nifi.processors.standard.util.JdbcCommon.convertToAvroStream(JdbcCommon.java:72)
>  ~[na:na]
>   at 
> org.apache.nifi.processors.standard.ExecuteSQL$1.process(ExecuteSQL.java:158) 
> ~[na:na]
>   at 
> org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:1953)
>  ~[nifi-framework-core-0.5.1.jar:0.5.1]
>   at 
> org.apache.nifi.processors.standard.ExecuteSQL.onTrigger(ExecuteSQL.java:152) 
> ~[na:na]
>   at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  ~[nifi-api-0.5.1.jar:0.5.1]
>   at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1139)
>  [nifi-framework-core-0.5.1.jar:0.5.1]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:139)
>  [nifi-framework-core-0.5.1.jar:0.5.1]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:49)
>  [nifi-framework-core-0.5.1.jar:0.5.1]
>   at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:124)
>  [nifi-framework-core-0.5.1.jar:0.5.1]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
> [na:1.7.0_79]
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) 
> [na:1.7.0_79]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
>  [na:1.7.0_79]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>  [na:1.7.0_79]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  [na:1.7.0_79]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  [na:1.7.0_79]



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

[jira] [Commented] (NIFI-1563) Remove storage of components' stats and bulletins from NCM

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1563:
- Updating UI to support restructured status history DTO.


> Remove storage of components' stats and bulletins from NCM
> --
>
> Key: NIFI-1563
> URL: https://issues.apache.org/jira/browse/NIFI-1563
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Currently, each node in a cluster sends a period heartbeat that contains the 
> stats for all components in the node. This happens every 5 seconds by 
> default. This results in quite a lot of chatter between the NCM and nodes. It 
> made sense to take this approach when the clustering concept was designed 
> because there were no Process Groups, and we had no notion of merging 
> responses from nodes for a web request.
> However, now we should replicate the request to all nodes and then merge the 
> responses on demand, rather than storing this information on the NCM. This 
> requires far less bandwidth because we only need to pull the stats for a 
> particular Process Group and only on demand instead of every 5 seconds. 
> Additionally, this is laying groundwork for the Zero-Master clustering that 
> we want to have in place for 1.0.0.
> In order to remove the stats from the NCM, we will also need to remove the 
> bulletins and stats history. These requests will all need to be federated and 
> the responses merged on-demand.



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

[jira] [Commented] (NIFI-1579) Improve ListenSyslog Performance

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1579 Performance improvements for ListenSyslog which include removing an 
unnecessary yield and exposing a configurable size for the internal queue used 
by the processor, changing ListenSyslog to use a 20ms poll and use a long poll 
when batching, also including same improvements for ListenRELP


> Improve ListenSyslog Performance
> 
>
> Key: NIFI-1579
> URL: https://issues.apache.org/jira/browse/NIFI-1579
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Bende
>Assignee: Bryan Bende
> Fix For: 0.6.0
>
> Attachments: NIFI-1579-ListenSyslog_Performance-Part2.patch, 
> NIFI-1579-ListenSyslog_Performance.patch
>
>
> While testing ListenSyslog at various data rates it was observed that a 
> significant amount of packets were dropped when using UDP.



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

[jira] [Commented] (NIFI-1563) Remove storage of components' stats and bulletins from NCM

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1563: Federate requests and merge responses from nodes instead of storing 
bulletins and stats at NCM


> Remove storage of components' stats and bulletins from NCM
> --
>
> Key: NIFI-1563
> URL: https://issues.apache.org/jira/browse/NIFI-1563
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Currently, each node in a cluster sends a period heartbeat that contains the 
> stats for all components in the node. This happens every 5 seconds by 
> default. This results in quite a lot of chatter between the NCM and nodes. It 
> made sense to take this approach when the clustering concept was designed 
> because there were no Process Groups, and we had no notion of merging 
> responses from nodes for a web request.
> However, now we should replicate the request to all nodes and then merge the 
> responses on demand, rather than storing this information on the NCM. This 
> requires far less bandwidth because we only need to pull the stats for a 
> particular Process Group and only on demand instead of every 5 seconds. 
> Additionally, this is laying groundwork for the Zero-Master clustering that 
> we want to have in place for 1.0.0.
> In order to remove the stats from the NCM, we will also need to remove the 
> bulletins and stats history. These requests will all need to be federated and 
> the responses merged on-demand.



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

[jira] [Commented] (NIFI-1577) NiFi holds open too many files when using a Run Duration > 0 ms and calling session.append

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1577: Close any streams that are left open for 'append' when the session 
is checkpointed, rather than waiting for it to be committed


> NiFi holds open too many files when using a Run Duration > 0 ms and calling 
> session.append
> --
>
> Key: NIFI-1577
> URL: https://issues.apache.org/jira/browse/NIFI-1577
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-1577-Close-any-streams-that-are-left-open-for-a.patch
>
>
> If a Processor calls ProcessSession.append() and has a Run Duration scheduled 
> > 0 ms, we quickly end up with "Too many open files" exceptions.
> This appears to be due to the fact that calling append() holds the content 
> repository's stream open so that the session can keep appending to it, but on 
> checkpoint() the session does not close these streams. It should close these 
> streams on checkpoint, since the Processor is no longer allowed to reference 
> these FlowFiles anyway at that point.



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

[jira] [Commented] (NIFI-1574) Write-Ahead log can become corrupt if NiFi is shutdown while disk is full

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1574: Ensure that we never flush a BufferedOutputStream's buffer on close 
of the write-ahead log


> Write-Ahead log can become corrupt if NiFi is shutdown while disk is full
> -
>
> Key: NIFI-1574
> URL: https://issues.apache.org/jira/browse/NIFI-1574
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-1574-Ensure-that-we-never-flush-a-BufferedOutpu.patch
>
>
> The FlowFile Repository, as well as the Local State Provider can exhibit this 
> problem. We saw the following stack trace when attempting to restart a node 
> while its disk was completely full:
> {code}
> 2016-02-27 06:43:39,249 WARN [main] org.eclipse.jetty.webapp.WebAppContext 
> Failed startup of context 
> o.e.j.w.WebAppContext@8b727cb{/nifi-api,file:/opt/nifi/nifi-0.5.1/work/jetty/nifi-web-api-0.5.1.war/webapp/,STARTING}{./work/nar/framework/nifi-framework-nar-0.5.1.nar-unpacked/META-INF/bundled-dependencies/nifi-web-api-0.5.1.war}
> org.apache.nifi.web.NiFiCoreException: Unable to start Flow Controller.
> at 
> org.apache.nifi.web.contextlistener.ApplicationStartupContextListener.contextInitialized(ApplicationStartupContextListener.java:99)
>  ~[na:na]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
>  ~[jetty-server-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
>  ~[jetty-servlet-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
>  ~[jetty-server-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
>  ~[jetty-servlet-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349) 
> ~[jetty-webapp-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342) 
> ~[jetty-webapp-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
>  ~[jetty-server-9.2.11.v20150529.jar:9.2.11.v20150529]
> at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505) 
> ~[jetty-webapp-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
>  [jetty-util-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
>  [jetty-util-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
>  [jetty-util-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
>  [jetty-server-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
>  [jetty-util-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
>  [jetty-util-9.2.11.v20150529.jar:9.2.11.v20150529]
> at org.eclipse.jetty.server.Server.start(Server.java:387) 
> [jetty-server-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
>  [jetty-util-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
>  [jetty-server-9.2.11.v20150529.jar:9.2.11.v20150529]
> at org.eclipse.jetty.server.Server.doStart(Server.java:354) 
> [jetty-server-9.2.11.v20150529.jar:9.2.11.v20150529]
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
>  [jetty-util-9.2.11.v20150529.jar:9.2.11.v20150529]
> at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:663) 
> [nifi-jetty-0.5.1.jar:0.5.1]
> at org.apache.nifi.NiFi.(NiFi.java:137) [nifi-runtime-0.5.1.jar:0.5.1]
> at org.apache.nifi.NiFi.main(NiFi.java:227) [nifi-runtime-0.5.1.jar:0.5.1]
> Caused by: org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 

[jira] [Commented] (NIFI-1572) Empty Queue sometimes indicates that 0 FlowFiles were dropped, even when queue contains many FlowFiles

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1572: Ensure that if an Exception is thrown when processing a bin, all 
sessions involved are rolled back or otherwise accounted for


> Empty Queue sometimes indicates that 0 FlowFiles were dropped, even when 
> queue contains many FlowFiles
> --
>
> Key: NIFI-1572
> URL: https://issues.apache.org/jira/browse/NIFI-1572
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-1572-Ensure-that-if-an-Exception-is-thrown-when.patch
>
>
> Specifically, we are seeing this with MergeContent as the target of the 
> connection. It has about 1.2 million FlowFiles in its queue. The Processor 
> was stopped. So the session should be rolled back. It is unclear if the 
> problem is with rolling back the sessions or with Clearing the queue.



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

[jira] [Commented] (NIFI-963) Update admin guide to cover the utilization of multiple lib directories

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-963 Update admin guide to cover configuration of multiple lib directories

This closes #250.

Signed-off-by: Aldrin Piri 


> Update admin guide to cover the utilization of multiple lib directories
> ---
>
> Key: NIFI-963
> URL: https://issues.apache.org/jira/browse/NIFI-963
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Reporter: Aldrin Piri
>Priority: Minor
>
> Thanks to NIFI-433 we are able to specify multiple lib directories.  This is 
> particularly handy for users that wish to have a core set of their libraries 
> map into their NiFi installation.  However, this is not currently documented 
> in the Admin Guide.



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

[jira] [Commented] (NIFI-1556) Perform Release Management Functions for 0.5.1

[ASF subversion and git services (JIRA)]

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

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

Commit 1732600 from [~tkurc] in branch 'site/trunk'
[ https://svn.apache.org/r1732600 ]

NIFI-1556: updating nifi-docs for components for 0.5.1

> Perform Release Management Functions for 0.5.1
> --
>
> Key: NIFI-1556
> URL: https://issues.apache.org/jira/browse/NIFI-1556
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.1
>Reporter: Tony Kurc
>Assignee: Tony Kurc
> Fix For: 0.5.1
>
>




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

[jira] [Commented] (NIFI-1556) Perform Release Management Functions for 0.5.1

[ASF subversion and git services (JIRA)]

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

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

Commit 1732599 from [~tkurc] in branch 'site/trunk'
[ https://svn.apache.org/r1732599 ]

NIFI-1556: updating rest-api for 0.5.1

> Perform Release Management Functions for 0.5.1
> --
>
> Key: NIFI-1556
> URL: https://issues.apache.org/jira/browse/NIFI-1556
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.1
>Reporter: Tony Kurc
>Assignee: Tony Kurc
> Fix For: 0.5.1
>
>




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

[jira] [Commented] (NIFI-1556) Perform Release Management Functions for 0.5.1

[ASF subversion and git services (JIRA)]

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

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

Commit 0848855986db53189cf71b9e86fc592ba7867dfc in nifi's branch 
refs/heads/support/nifi-0.5.x from [~trk...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=0848855 ]

NIFI-1556-RC2 prepare for next development iteration


> Perform Release Management Functions for 0.5.1
> --
>
> Key: NIFI-1556
> URL: https://issues.apache.org/jira/browse/NIFI-1556
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.1
>Reporter: Tony Kurc
>Assignee: Tony Kurc
> Fix For: 0.5.1
>
>




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

[jira] [Commented] (NIFI-1556) Perform Release Management Functions for 0.5.1

[ASF subversion and git services (JIRA)]

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

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

Commit 672211b87b4f1e52f8ee5153c26a467b555a331e in nifi's branch 
refs/heads/support/nifi-0.5.x from [~trk...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=672211b ]

NIFI-1556-RC2 prepare release nifi-0.5.1-RC2


> Perform Release Management Functions for 0.5.1
> --
>
> Key: NIFI-1556
> URL: https://issues.apache.org/jira/browse/NIFI-1556
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.1
>Reporter: Tony Kurc
>Assignee: Tony Kurc
> Fix For: 0.5.1
>
>




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

[jira] [Commented] (NIFI-1511) Incorporate Groovy unit tests as part of the build instead of via profile

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1511 Incorporating Groovy unit tests as part of the main build and 
providing explicit compile scope on the Groovy dependency for the scripting 
bundle. This closes #220

Signed-off-by: Matt Gilman 


> Incorporate Groovy unit tests as part of the build instead of via profile
> -
>
> Key: NIFI-1511
> URL: https://issues.apache.org/jira/browse/NIFI-1511
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.0
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
> Fix For: 0.6.0
>
>
> From the mailing list:
> {quote}
> Recommend *not* running the groovy tests.  They set the groovy
> dependency to test scope which means groovy ends up not supported in
> the convenience binary.
> # Verify the build works including release audit tool (RAT) checks
>   cd nifi-0.5.0
>   mvn clean install -Pcontrib-check
> We should work to get the groovy stuff into the build without needing
> profile activation if they should be the norm.
> {quote}



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

[jira] [Commented] (NIFI-1256) Allow RouteText to use Expression Language to route lines

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1256: Added a 'Satisfies Expression' option for Matching Strategy of 
RouteText

Signed-off-by: jpercivall 


> Allow RouteText to use Expression Language to route lines
> -
>
> Key: NIFI-1256
> URL: https://issues.apache.org/jira/browse/NIFI-1256
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments: 
> 0001-NIFI-1256-Added-a-Satisfies-Expression-option-for-Ma.patch, 
> Testing_NIFI-1256.xml
>
>
> As part of NIFI-1249, we made it so that Processors can provide their own 
> 'variables' to be evaluated by the Expression Language. We should update 
> RouteText to add a Matching Strategy of "Satisfies Expression". If this is 
> selected, the values of user-defined properties should be required to be 
> Expression Language Expressions that return BOOLEAN, as with RouteOnAttribute.
> We would add a variable named "line" so that users can route by using an 
> expression like: ${line:toUpper():startsWith("U")}
> This is a much more powerful mechanism than the others, as it allows any and 
> all of the existing strategies to be combined into a single expression and 
> allows users to use different types of comparisons for each property.



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

[jira] [Commented] (NIFI-1513) Fix high impact coverity issues

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1513: fixed some easy to fix errors

Addressing checkstyle issue.

This closes #221

Signed-off-by: Matt Gilman 


> Fix high impact coverity issues
> ---
>
> Key: NIFI-1513
> URL: https://issues.apache.org/jira/browse/NIFI-1513
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.5.0
>Reporter: Tony Kurc
>Assignee: Tony Kurc
>Priority: Minor
>
> Coverity Scan discovered a few issues, this is a ticket to track progress on 
> mitigating them



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

[jira] [Commented] (NIFI-1357) Add Snappy compression to "CompressContent" Processor

[ASF subversion and git services (JIRA)]

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

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

Commit 32f476aaa7040ed4718713f2ed11e11bc7ef4f1c in nifi's branch 
refs/heads/master from [~jeremy.dyer]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=32f476a ]

NIFI-1357 Add Snappy compression to "CompressContent" Processor

This closes #164.

Signed-off-by: Aldrin Piri 


> Add Snappy compression to "CompressContent" Processor
> -
>
> Key: NIFI-1357
> URL: https://issues.apache.org/jira/browse/NIFI-1357
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Jeremy Dyer
>Assignee: Jeremy Dyer
>Priority: Minor
>
> Snappy is a popular compression format within the Hadoop ecosystem. While 
> several existing NiFi processors already have the ability to compress content 
> as Snappy (PutHDFS for example) CompressContent does not have the ability to 
> compress to Snappy directly. This would also allow for writing snappy 
> compressed data to S3 for use with EMR.



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

[jira] [Commented] (NIFI-1539) Add correct parsing of content type in accordance with RFC 2045

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1539: - Comparing octet stream content type by using starts with and 
ignores case.


> Add correct parsing of content type in accordance with RFC 2045
> ---
>
> Key: NIFI-1539
> URL: https://issues.apache.org/jira/browse/NIFI-1539
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.5.0
>Reporter: Sönke Liebau
>Priority: Minor
> Fix For: 0.6.0
>
>
> The content viewer does not display json content when the content-type string 
> does not exactly match "application/json" for example: 
> "application/json;charset=UTF8" or "application/Json" trigger the error 
> message "No viewer is registered for this content type."
> According to [RFC 2045|https://www.ietf.org/rfc/rfc2045.txt] there can be any 
> number of parameters following the type and subtype values, so I believe 
> these should not impact the viewer chosen to display this content.
> Furthermore, the rfc states that type and subtype are to be treated case 
> insensitive, which is also not given as all checks I found in the code are 
> purely against lowercase.
> As far as I can tell this is checked twice, the viewer for the content type 
> is obtained from a Context object, if there is no viewer that matches exactly 
> the error message stated above is shown. 
> After this was successful a string comparison is done in the 
> StandardContentViewerController class:
> {code:title=StandardContentViewerController.java|borderStyle=solid}
> if ("application/json".equals(contentType) || 
> "application/xml".equals(contentType) || "text/plain".equals(contentType) || 
> "text/csv".equals(contentType)) {
> ...
> }
> {code}
> So even if the Viewer was assigned to this content type if would fail here.
> h3. Proposed solution
> - Add code to DownloadableContent.java to parse content type string at 
> creation and store only lowercased type and subtype, which is retrieved by 
> getter method, so no changes are necessary to downstream code
> - Add map to object to store parameters that were contained in the original 
> value
> - Either make the entire parameters map object retrievable or create getter 
> to retrieve parameter from map by parameter name
> - Add method to retrieve original field value, I propose to build the value 
> on request from stored type, subtype and parameters, this way we can 
> implement some light error handling and ensure to always hand out properly 
> formed strings, even if the input value may have had some small error (there 
> is no need to pay attention to parameter order, as per rfc the order 
> shouldn't matter)
> h3. Discussion points
> - Anything that actually relies on access to parameters in the content type 
> would break, this could be avoided by not changing the getType method but 
> instead adding a new method to return type without parameters instead. 
> Drawback to this is that current implementation of ContentViewerController 
> would need to be changed to use this new function. I am unsure which aproach 
> is preferable..
> - If there are classes downstream that access the content type field not via 
> DownloadableContent, this shouldn't break anything, as the status quo is 
> preserved, but there is a small chance that you get two different content 
> types, if you actually use both methods
> I am happy to create a pull request to this effect if open points can be 
> clarified and this is deemed useful.



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

[jira] [Commented] (NIFI-1539) Add correct parsing of content type in accordance with RFC 2045

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1539 - Add normalization of content type for content viewing

Add code to ContentViewerController to strip content type of any trailing 
parameters and lowercase the type and subtype.

Added function to ViewableContent to enable retrieving the original value of 
the content type if needed.

This closes #242

Signed-off-by: Matt Gilman 


> Add correct parsing of content type in accordance with RFC 2045
> ---
>
> Key: NIFI-1539
> URL: https://issues.apache.org/jira/browse/NIFI-1539
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.5.0
>Reporter: Sönke Liebau
>Priority: Minor
> Fix For: 0.6.0
>
>
> The content viewer does not display json content when the content-type string 
> does not exactly match "application/json" for example: 
> "application/json;charset=UTF8" or "application/Json" trigger the error 
> message "No viewer is registered for this content type."
> According to [RFC 2045|https://www.ietf.org/rfc/rfc2045.txt] there can be any 
> number of parameters following the type and subtype values, so I believe 
> these should not impact the viewer chosen to display this content.
> Furthermore, the rfc states that type and subtype are to be treated case 
> insensitive, which is also not given as all checks I found in the code are 
> purely against lowercase.
> As far as I can tell this is checked twice, the viewer for the content type 
> is obtained from a Context object, if there is no viewer that matches exactly 
> the error message stated above is shown. 
> After this was successful a string comparison is done in the 
> StandardContentViewerController class:
> {code:title=StandardContentViewerController.java|borderStyle=solid}
> if ("application/json".equals(contentType) || 
> "application/xml".equals(contentType) || "text/plain".equals(contentType) || 
> "text/csv".equals(contentType)) {
> ...
> }
> {code}
> So even if the Viewer was assigned to this content type if would fail here.
> h3. Proposed solution
> - Add code to DownloadableContent.java to parse content type string at 
> creation and store only lowercased type and subtype, which is retrieved by 
> getter method, so no changes are necessary to downstream code
> - Add map to object to store parameters that were contained in the original 
> value
> - Either make the entire parameters map object retrievable or create getter 
> to retrieve parameter from map by parameter name
> - Add method to retrieve original field value, I propose to build the value 
> on request from stored type, subtype and parameters, this way we can 
> implement some light error handling and ensure to always hand out properly 
> formed strings, even if the input value may have had some small error (there 
> is no need to pay attention to parameter order, as per rfc the order 
> shouldn't matter)
> h3. Discussion points
> - Anything that actually relies on access to parameters in the content type 
> would break, this could be avoided by not changing the getType method but 
> instead adding a new method to return type without parameters instead. 
> Drawback to this is that current implementation of ContentViewerController 
> would need to be changed to use this new function. I am unsure which aproach 
> is preferable..
> - If there are classes downstream that access the content type field not via 
> DownloadableContent, this shouldn't break anything, as the status quo is 
> preserved, but there is a small chance that you get two different content 
> types, if you actually use both methods
> I am happy to create a pull request to this effect if open points can be 
> clarified and this is deemed useful.



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

[jira] [Commented] (NIFI-1556) Perform Release Management Functions for 0.5.1

[ASF subversion and git services (JIRA)]

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

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

Commit 0848855986db53189cf71b9e86fc592ba7867dfc in nifi's branch 
refs/heads/NIFI-1556-RC2 from [~trk...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=0848855 ]

NIFI-1556-RC2 prepare for next development iteration


> Perform Release Management Functions for 0.5.1
> --
>
> Key: NIFI-1556
> URL: https://issues.apache.org/jira/browse/NIFI-1556
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.1
>Reporter: Tony Kurc
>Assignee: Tony Kurc
> Fix For: 0.5.1
>
>




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

[jira] [Commented] (NIFI-1556) Perform Release Management Functions for 0.5.1

[ASF subversion and git services (JIRA)]

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

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

Commit 672211b87b4f1e52f8ee5153c26a467b555a331e in nifi's branch 
refs/heads/NIFI-1556-RC2 from [~trk...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=672211b ]

NIFI-1556-RC2 prepare release nifi-0.5.1-RC2


> Perform Release Management Functions for 0.5.1
> --
>
> Key: NIFI-1556
> URL: https://issues.apache.org/jira/browse/NIFI-1556
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.1
>Reporter: Tony Kurc
>Assignee: Tony Kurc
> Fix For: 0.5.1
>
>




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

[jira] [Commented] (NIFI-1557) Controller Services and Reporting Tasks not properly ordered in fingerprint verification - makes restart/upgrades difficult

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1557: Ensure that Reporting Tasks & controller services are ordered by ID 
before fingerprinting


> Controller Services and Reporting Tasks not properly ordered in fingerprint 
> verification - makes restart/upgrades difficult
> ---
>
> Key: NIFI-1557
> URL: https://issues.apache.org/jira/browse/NIFI-1557
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.3.0, 0.5.0, 0.4.1
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 0.5.1
>
> Attachments: 
> 0001-NIFI-1557-Ensure-that-Reporting-Tasks-controller-ser.patch
>
>
> In upgrading a cluster have found unreliable behavior.  In restarting nodes 
> in a cluster found unreliable behavior.  Turns out it appears we are not 
> ordering the controller services and reporting tasks before doing fingerprint 
> verification.  This causes unreliable restarts/upgrades.
> {quote}
> The NMC says:
> ===
> 2016-02-23 19:42:32,466 INFO [Handle Reconnection Failure Message from 
> [id=61103aa8-1226-44e4-827c-b150ac7d4079, 
> apiAddress=processing-2.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-2.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-2.demo.onyara.com, siteToSitePort=9000]] 
> o.a.n.c.manager.impl.WebClusterManager Node Event: 
> [id=61103aa8-1226-44e4-827c-b150ac7d4079, 
> apiAddress=processing-2.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-2.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-2.demo.onyara.com, siteToSitePort=9000] -- 'Node 
> could not rejoin cluster. Setting node to Disconnected. Node reported the 
> following error: org.apache.nifi.cluster.ConnectionException: Failed to 
> connect node to cluster because local flow is different than cluster flow.'
> 2016-02-23 19:42:32,530 INFO [Process NCM Request-5] 
> o.a.n.c.p.impl.SocketProtocolListener Finished processing request 
> 6d4a5f0e-e4e5-47cf-843a-7194660197c8 (type=RECONNECTION_FAILURE, length=654 
> bytes) in 102 millis
> 2016-02-23 19:42:32,530 INFO [Handle Reconnection Failure Message from 
> [id=e5577bb3-290c-4688-be43-78b0b4af06fb, 
> apiAddress=processing-1.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-1.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-1.demo.onyara.com, siteToSitePort=9000]] 
> o.a.n.c.manager.impl.WebClusterManager Node Event: 
> [id=e5577bb3-290c-4688-be43-78b0b4af06fb, 
> apiAddress=processing-1.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-1.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-1.demo.onyara.com, siteToSitePort=9000] -- 'Node 
> could not rejoin cluster. Setting node to Disconnected. Node reported the 
> following error: org.apache.nifi.cluster.ConnectionException: Failed to 
> connect node to cluster because local flow is different than cluster flow.'
> 2016-02-23 19:42:34,875 INFO [Process NCM Request-6] 
> o.a.n.c.p.impl.SocketProtocolListener Received request 
> 1b681e8d-3f68-4be2-9ab2-7134050cce9d from 172.31.4.123
> 2016-02-23 19:42:34,908 INFO [Process NCM Request-7] 
> o.a.n.c.p.impl.SocketProtocolListener Received request 
> 5008cbb3-5084-4083-9b56-84bd5ad3c55c from 172.31.4.123
> 2016-02-23 19:42:34,994 INFO [Process NCM Request-6] 
> o.a.n.c.p.impl.SocketProtocolListener Finished processing request 
> 1b681e8d-3f68-4be2-9ab2-7134050cce9d (type=BULLETINS, length=1550 bytes) in 
> 118 millis
> 2016-02-23 19:42:35,008 INFO [Process NCM Request-7] 
> o.a.n.c.p.impl.SocketProtocolListener Finished processing request 
> 5008cbb3-5084-4083-9b56-84bd5ad3c55c (type=RECONNECTION_FAILURE, length=654 
> bytes) in 100 millis
> 2016-02-23 19:42:35,009 INFO [Handle Reconnection Failure Message from 
> [id=2240c663-2b20-48dc-936d-078a11812d49, 
> apiAddress=processing-3.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-3.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-3.demo.onyara.com, siteToSitePort=9000]] 
> o.a.n.c.manager.impl.WebClusterManager Node Event: 
> [id=2240c663-2b20-48dc-936d-078a11812d49, 
> apiAddress=processing-3.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-3.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-3.demo.onyara.com, siteToSitePort=9000] -- 'Node 
> could not rejoin cluster. Setting node to Disconnected. Node reported 

[jira] [Commented] (NIFI-1557) Controller Services and Reporting Tasks not properly ordered in fingerprint verification - makes restart/upgrades difficult

[ASF subversion and git services (JIRA)]

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

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

Commit e2005fa059fbe128e2e278cda5ed7a27ab6e1ec3 in nifi's branch 
refs/heads/support/nifi-0.5.x from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=e2005fa ]

NIFI-1557: Ensure that Reporting Tasks & controller services are ordered by ID 
before fingerprinting


> Controller Services and Reporting Tasks not properly ordered in fingerprint 
> verification - makes restart/upgrades difficult
> ---
>
> Key: NIFI-1557
> URL: https://issues.apache.org/jira/browse/NIFI-1557
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.3.0, 0.5.0, 0.4.1
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 0.5.1
>
> Attachments: 
> 0001-NIFI-1557-Ensure-that-Reporting-Tasks-controller-ser.patch
>
>
> In upgrading a cluster have found unreliable behavior.  In restarting nodes 
> in a cluster found unreliable behavior.  Turns out it appears we are not 
> ordering the controller services and reporting tasks before doing fingerprint 
> verification.  This causes unreliable restarts/upgrades.
> {quote}
> The NMC says:
> ===
> 2016-02-23 19:42:32,466 INFO [Handle Reconnection Failure Message from 
> [id=61103aa8-1226-44e4-827c-b150ac7d4079, 
> apiAddress=processing-2.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-2.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-2.demo.onyara.com, siteToSitePort=9000]] 
> o.a.n.c.manager.impl.WebClusterManager Node Event: 
> [id=61103aa8-1226-44e4-827c-b150ac7d4079, 
> apiAddress=processing-2.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-2.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-2.demo.onyara.com, siteToSitePort=9000] -- 'Node 
> could not rejoin cluster. Setting node to Disconnected. Node reported the 
> following error: org.apache.nifi.cluster.ConnectionException: Failed to 
> connect node to cluster because local flow is different than cluster flow.'
> 2016-02-23 19:42:32,530 INFO [Process NCM Request-5] 
> o.a.n.c.p.impl.SocketProtocolListener Finished processing request 
> 6d4a5f0e-e4e5-47cf-843a-7194660197c8 (type=RECONNECTION_FAILURE, length=654 
> bytes) in 102 millis
> 2016-02-23 19:42:32,530 INFO [Handle Reconnection Failure Message from 
> [id=e5577bb3-290c-4688-be43-78b0b4af06fb, 
> apiAddress=processing-1.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-1.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-1.demo.onyara.com, siteToSitePort=9000]] 
> o.a.n.c.manager.impl.WebClusterManager Node Event: 
> [id=e5577bb3-290c-4688-be43-78b0b4af06fb, 
> apiAddress=processing-1.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-1.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-1.demo.onyara.com, siteToSitePort=9000] -- 'Node 
> could not rejoin cluster. Setting node to Disconnected. Node reported the 
> following error: org.apache.nifi.cluster.ConnectionException: Failed to 
> connect node to cluster because local flow is different than cluster flow.'
> 2016-02-23 19:42:34,875 INFO [Process NCM Request-6] 
> o.a.n.c.p.impl.SocketProtocolListener Received request 
> 1b681e8d-3f68-4be2-9ab2-7134050cce9d from 172.31.4.123
> 2016-02-23 19:42:34,908 INFO [Process NCM Request-7] 
> o.a.n.c.p.impl.SocketProtocolListener Received request 
> 5008cbb3-5084-4083-9b56-84bd5ad3c55c from 172.31.4.123
> 2016-02-23 19:42:34,994 INFO [Process NCM Request-6] 
> o.a.n.c.p.impl.SocketProtocolListener Finished processing request 
> 1b681e8d-3f68-4be2-9ab2-7134050cce9d (type=BULLETINS, length=1550 bytes) in 
> 118 millis
> 2016-02-23 19:42:35,008 INFO [Process NCM Request-7] 
> o.a.n.c.p.impl.SocketProtocolListener Finished processing request 
> 5008cbb3-5084-4083-9b56-84bd5ad3c55c (type=RECONNECTION_FAILURE, length=654 
> bytes) in 100 millis
> 2016-02-23 19:42:35,009 INFO [Handle Reconnection Failure Message from 
> [id=2240c663-2b20-48dc-936d-078a11812d49, 
> apiAddress=processing-3.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-3.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-3.demo.onyara.com, siteToSitePort=9000]] 
> o.a.n.c.manager.impl.WebClusterManager Node Event: 
> [id=2240c663-2b20-48dc-936d-078a11812d49, 
> apiAddress=processing-3.demo.onyara.com, apiPort=8443, 
> socketAddress=processing-3.demo.onyara.com, socketPort=6000, 
> siteToSiteAddress=processing-3.demo.onyara.com, siteToSitePort=9000] -- 'Node 
> could not rejoin cluster. Setting node to Disconnected. 

[jira] [Commented] (NIFI-1556) Perform Release Management Functions for 0.5.1

[ASF subversion and git services (JIRA)]

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

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

Commit 1bc7bdb609606b9aa61cebad3ef2e3c87d34ea63 in nifi's branch 
refs/heads/NIFI-1556-RC1 from [~trk...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=1bc7bdb ]

NIFI-1556-RC1 prepare release nifi-0.5.1-RC1


> Perform Release Management Functions for 0.5.1
> --
>
> Key: NIFI-1556
> URL: https://issues.apache.org/jira/browse/NIFI-1556
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.1
>Reporter: Tony Kurc
>Assignee: Tony Kurc
> Fix For: 0.5.1
>
>




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

[jira] [Commented] (NIFI-1556) Perform Release Management Functions for 0.5.1

[ASF subversion and git services (JIRA)]

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

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

Commit 190b94f0d461e590d5e39056b1f325b3f41e73eb in nifi's branch 
refs/heads/NIFI-1556-RC1 from [~trk...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=190b94f ]

NIFI-1556-RC1 prepare for next development iteration


> Perform Release Management Functions for 0.5.1
> --
>
> Key: NIFI-1556
> URL: https://issues.apache.org/jira/browse/NIFI-1556
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.1
>Reporter: Tony Kurc
>Assignee: Tony Kurc
> Fix For: 0.5.1
>
>




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

[jira] [Commented] (NIFI-1514) ExecuteStreamCommand does not split command line arguments by provided separator when these come from expression language evaluation

[ASF subversion and git services (JIRA)]

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

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

Commit 8a074c3777213e38ba622f032bf8d277e1586828 in nifi's branch 
refs/heads/support/nifi-0.5.x from [~michal.klempa]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8a074c3 ]

NIFI-1514 Fixed ExecuteStreamCommand when expressions in command arguments are 
used, contents are not split by command separator

Signed-off-by: Aldrin Piri 


> ExecuteStreamCommand does not split command line arguments by provided 
> separator when these come from expression language evaluation
> 
>
> Key: NIFI-1514
> URL: https://issues.apache.org/jira/browse/NIFI-1514
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.5.0, 0.4.1
>Reporter: Michal Klempa
>Priority: Trivial
> Fix For: 0.6.0, 0.5.1
>
>
> When Comannd Arguments property contains expression to be evaluated, the 
> expression is taken as one command argument instead of being splitted using 
> argument separator.
> To reproduce the problem:
> 1. Create DataFlow
> 2. Add GenerateFlowFile processor, File Size: 10kB
> 3. Connect GenerateFlowFile -> success -> UpdateAttribute processor
> 4. In UpdateAttribute: create attribute optionalArgs with contents: "-c 5"
> 5. Connect UpdateAttribute -> success -> ExecuteStreamCommand
> 6. Configure ExecuteStreamCommand to execute Command Path: "ping", Command 
> Arguments: "${optionalArgs} google.com", Argument Delimiter: " " (spacebar), 
> Ignore STDIN: true, auto terminate: original
> 7. Connect ExecuteStreamCommand -> output stream - > LogAttribute to see some 
> output. LogAttribute auto terminate: success, Log Level: error, Log Payload: 
> true.
> 8. Run the flow.
> Expected output:
> 1. ExecuteStreamCommand issues command ping with args:[ "-c", "5", 
> "google.com"]
> Actual output:
> 1. ExecuteStreamCommand puts the "-c 5" into single arg for ProcessBuilder. 
> args: are ["-c 5", "google.com"]
> This behavior is no problem for ping utility (as it reparses the commandline 
> again to search for argument separator), but there are tools (like snmpwalk 
> in my case), which are dumb enough not to parse command line arguments 
> properly, when they are sent inproperly by ProcessBuilder.
> The problem is apparently in lines: ExecuteStreamCommand.java: 305-306, where 
> arguments splitting on argument separator is done before expression language 
> evaluation. The fix should reverse the operation: first evaluate expression 
> language and the split the arguments by separator.



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

[jira] [Commented] (NIFI-1282) Error message for attempting to disabled port doesn't match error message for processors

[ASF subversion and git services (JIRA)]

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

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

Commit 2a459fe21c708c8316dd255c3dc7f8254e7940f1 in nifi's branch 
refs/heads/support/nifi-0.5.x from [~pvillard]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2a459fe ]

NIFI-1282 This closes #228. Fixed error message when attempting to start a 
disabled port

Fixed error message when attempting to start a disabled port

Signed-off-by: joewitt 


> Error message for attempting to disabled port doesn't match error message for 
> processors
> 
>
> Key: NIFI-1282
> URL: https://issues.apache.org/jira/browse/NIFI-1282
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 0.4.0
>Reporter: Joseph Percivall
>Assignee: Joseph Witt
>Priority: Trivial
> Fix For: 0.6.0, 0.5.1
>
>
> If you attempt to run a processor that is disabled this error message will 
> come back:
> UpdateAttribute[id=f731cf94-d9da-4e2e-872b-a772edb16373] cannot be started 
> because it is disabled
> If you attempt to run an input/output port that is disabled this error 
> message will come back:
> LocalPort[name=input,id=0e0639b5-6037-4f38-9871-4a866bb94d80] is not stopped
> LocalPort[name=output,id=b09322b6-38ad-466c-ad63-ece7e4d4038d] is not stopped
> The error message for ports should be changed to match the processors and 
> which correctly states the issue.



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

[jira] [Commented] (NIFI-1548) Controller Service "Usage" Icon not working

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1548 Fixing Controller Service Usage Button. This closes #245

Signed-off-by: Matt Gilman 


> Controller Service "Usage" Icon not working
> ---
>
> Key: NIFI-1548
> URL: https://issues.apache.org/jira/browse/NIFI-1548
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.5.0
>Reporter: Brandon DeVries
>Priority: Minor
> Fix For: 0.5.1
>
>
> In The settings page on the "Contoller Services" tab, the "Usage" icon next 
> to each service doesn't do anything when clicked.  Tested on FireFox 24.7.0 & 
> 31.5.0 and Chrome 36.0.1985.125.  



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

[jira] [Commented] (NIFI-1548) Controller Service "Usage" Icon not working

[ASF subversion and git services (JIRA)]

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

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

Commit 280714942097b0703a1f8f92913d95159cd89bfa in nifi's branch 
refs/heads/support/nifi-0.5.x from [~jameswing]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2807149 ]

NIFI-1548 Fixing Controller Service Usage Button. This closes #245

Signed-off-by: Matt Gilman 


> Controller Service "Usage" Icon not working
> ---
>
> Key: NIFI-1548
> URL: https://issues.apache.org/jira/browse/NIFI-1548
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.5.0
>Reporter: Brandon DeVries
>Priority: Minor
> Fix For: 0.5.1
>
>
> In The settings page on the "Contoller Services" tab, the "Usage" icon next 
> to each service doesn't do anything when clicked.  Tested on FireFox 24.7.0 & 
> 31.5.0 and Chrome 36.0.1985.125.  



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

[jira] [Commented] (NIFI-1545) Update AWS S3 IT tests for new proxy properties

[ASF subversion and git services (JIRA)]

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

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

Commit f56e1551ebc20495d9bf7cf70814c0e4afba768a in nifi's branch 
refs/heads/support/nifi-0.5.x from [~jskora]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=f56e155 ]

NIFI-1545: Adjust integration tests ITDeleteS3Object, ITFetchS3Object, and 
ITPutS3Object to account for AWS new proxy properties. Correct typo in 
AbstractS3Processor.createClient() log message.

Reviewed by Tony Kurc (tk...@apache.org).


> Update AWS S3 IT tests for new proxy properties
> ---
>
> Key: NIFI-1545
> URL: https://issues.apache.org/jira/browse/NIFI-1545
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.5.1
>Reporter: Joe Skora
>Assignee: Joe Skora
> Fix For: 0.5.1
>
>
> Fix the S3 testGetPropertyDescriptors() tests in ITDeleteS3Object, 
> ITFetchS3Object, and ITPutS3Object for new proxy properties added to 
> AbstractAWSProcessor by 
> [NIFI-1489|https://issues.apache.org/jira/browse/NIFI-1489].



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

[jira] [Commented] (NIFI-1536) multiple putHDFS processors can result in put failures.

[ASF subversion and git services (JIRA)]

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

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

Commit 3a341ff264d7fd4ee9197649db59dc7300c3df68 in nifi's branch 
refs/heads/support/nifi-0.5.x from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=3a341ff ]

NIFI-1536 This closes #241. ensured that UserGroupInformation is re-initialized 
on each call to 'AbstractHadoopProcessor.resetHDFSResources(..)'

Signed-off-by: joewitt 


> multiple putHDFS processors can result in put failures.
> ---
>
> Key: NIFI-1536
> URL: https://issues.apache.org/jira/browse/NIFI-1536
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.5.0
> Environment: Java 1.8.0_60
> OSX Yosemite 10.10.5
>Reporter: Matthew Clarke
>Assignee: Oleg Zhurakousky
> Fix For: 0.6.0, 0.5.1
>
>
> When multiple putHDFS processors exist, the first to run loads some config 
> that is then used by other putHDFS processors that are started. 
> I have two dataflows setup.  One pushes data to a kerberized HDFS cluster 
> while the other pushes data to a totally different non kerberized HDFS 
> cluster.
> Each putHDFS is configured to use its own core-sites.xml.  If I start the 
> putHDFS that sends to the Kerberized HDFS cluster first, the other putHDFS 
> will throw an error when it tries to send data to the non-kerberized HDFS 
> cluster.
> ERROR [Timer-Driven Process Thread-7] o.apache.nifi.processors.hadoop.PutHDFS
> java.io.IOException: Failed on local exception: java.io.IOException: Server 
> asks us to fall back to SIMPLE auth, but this client is configured to only 
> allow secure connections.; Host Details : local host is: " hostname>/"; destination host is: "":
> 
> Caused by: java.io.IOException: Server asks us to fall back to SIMPLE auth, 
> but this client is configured to only allow secure connections.
> Even if i stop the putHDFS that is sending to the kerberized HDFS and/or 
> restart the putHDFS sending to the non kerberized HDFS, the above error 
> persists.
> I need to restart NiFi to clear condition.  After NiFi restart, if i run the 
> putHDFS  that sends to the non-kerberized HDFS first, the putHDFS to the 
> kerberized HDFS will still work.



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

[jira] [Commented] (NIFI-1546) Address cases when data reference query is null

[ASF subversion and git services (JIRA)]

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

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

Commit 054707c493292158b274778b75339862d6fe9728 in nifi's branch 
refs/heads/support/nifi-0.5.x from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=054707c ]

NIFI-1546: - Ensuring that the data reference query is not null before attempt 
to extract a cluster node id from it.

Signed-off-by: joewitt 


> Address cases when data reference query is null
> ---
>
> Key: NIFI-1546
> URL: https://issues.apache.org/jira/browse/NIFI-1546
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI, Extensions
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 0.6.0, 0.5.1
>
> Attachments: 0001-NIFI-1546.patch
>
>




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

[jira] [Commented] (NIFI-1546) Address cases when data reference query is null

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1546: - Ensuring that the data reference query is not null before attempt 
to extract a cluster node id from it.

Signed-off-by: joewitt 


> Address cases when data reference query is null
> ---
>
> Key: NIFI-1546
> URL: https://issues.apache.org/jira/browse/NIFI-1546
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI, Extensions
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 0.6.0, 0.5.1
>
> Attachments: 0001-NIFI-1546.patch
>
>




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

[jira] [Commented] (NIFI-1527) Resource Claim counts not incremented on restart for FlowFiles that are swapped out

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1527: Fixed issue that resulted in resource claims' claimant count getting 
incremented twice on restart

Signed-off-by: joewitt 


> Resource Claim counts not incremented on restart for FlowFiles that are 
> swapped out
> ---
>
> Key: NIFI-1527
> URL: https://issues.apache.org/jira/browse/NIFI-1527
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 0.6.0, 0.5.1
>
> Attachments: 
> 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch, 
> 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch, 
> 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch, 
> 0001-NIFI-1527-Fixed-issue-that-resulted-in-resource-clai.patch
>
>
> When NiFi starts, it tallies the count of how many FlowFiles reference each 
> Resource Claim and then removes or archives any file in the Content 
> Repository for which there is no claim.
> However, the claim counts are not incremented for data that is swapped out. 
> As a result, the content repository could delete or archive data on restart 
> that it should not. This could potentially result in data loss, if NiFi is 
> restarted while both of the following conditions are met:
> * All FlowFiles that reference a Resource Claim are swapped out
> * Content Repository's archive is disabled, or the archival threshold is 
> already exceeded from data outside of the Content Repository



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

[jira] [Commented] (NIFI-1527) Resource Claim counts not incremented on restart for FlowFiles that are swapped out

[ASF subversion and git services (JIRA)]

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

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

Commit 5da9f985bfda7bdcbb102857899fdecb98658e64 in nifi's branch 
refs/heads/support/nifi-0.5.x from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5da9f98 ]

NIFI-1527: Fixed issue that resulted in resource claims' claimant count getting 
incremented twice on restart

Signed-off-by: joewitt 


> Resource Claim counts not incremented on restart for FlowFiles that are 
> swapped out
> ---
>
> Key: NIFI-1527
> URL: https://issues.apache.org/jira/browse/NIFI-1527
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 0.6.0, 0.5.1
>
> Attachments: 
> 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch, 
> 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch, 
> 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch, 
> 0001-NIFI-1527-Fixed-issue-that-resulted-in-resource-clai.patch
>
>
> When NiFi starts, it tallies the count of how many FlowFiles reference each 
> Resource Claim and then removes or archives any file in the Content 
> Repository for which there is no claim.
> However, the claim counts are not incremented for data that is swapped out. 
> As a result, the content repository could delete or archive data on restart 
> that it should not. This could potentially result in data loss, if NiFi is 
> restarted while both of the following conditions are met:
> * All FlowFiles that reference a Resource Claim are swapped out
> * Content Repository's archive is disabled, or the archival threshold is 
> already exceeded from data outside of the Content Repository



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

[jira] [Commented] (NIFI-1542) PutS3Object Processor Logs Errors Without ListBucketMultipartUploads Permission

[ASF subversion and git services (JIRA)]

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

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

Commit e15a2b32db8da1e46cafbab1703cf04b2dffee95 in nifi's branch 
refs/heads/support/nifi-0.5.x from [~jskora]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=e15a2b3 ]

NIFI-1542: Update how PutS3Object handles a 403 AccessDenied response to a S3 
ListMultipartUploads request.

* Change log message from error to warning and added note about S3 permissions.
* Advance the ageoff check time by the check interval as if the request 
succeeded to prevent re-checking on every upload when permission does not exist.

Reviewed by Tony Kurc (tk...@apache.org) (with minor amendments for whitespace 
and error message consistency).


> PutS3Object Processor Logs Errors Without ListBucketMultipartUploads 
> Permission
> ---
>
> Key: NIFI-1542
> URL: https://issues.apache.org/jira/browse/NIFI-1542
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.5.0
> Environment: Linux, Chrome
>Reporter: James Wing
>Assignee: Joe Skora
>Priority: Minor
> Fix For: 0.5.1
>
> Attachments: error-checking-s3-multipart-upload-list.png
>
>
> In 0.5.0, I am seeing an error putting objects to Amazon S3 using the 
> PutS3Object processor.  The *put operation itself succeeds*, but a nasty-gram 
> is displayed in the flow and logged as a side effect.  The error text is 
> "Error checking S3 Multipart Upload list for ", from line 698 
> of PutS3Object.java.  This code was introduced in NIFI-1107, expanding the 
> PutS3Object processor with support for S3 multi-part uploads of larger files.
> Logged in nifi-app.log:
> {code}
> 2016-02-19 20:56:24,312 ERROR [Timer-Driven Process Thread-3] 
> o.a.nifi.processors.aws.s3.PutS3Object PutS
> 3Object[id=47df7533-91b2-4635-b865-45323f73f6c3] Error checking S3 Multipart 
> Upload list for batchiq-scra
> tch: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: 
> AccessDenied; Request ID: 7483E76EA
> 52E33C4)
> 2016-02-19 20:56:24,533 INFO [Timer-Driven Process Thread-3] 
> o.a.nifi.processors.aws.s3.PutS3Object PutS3
> Object[id=47df7533-91b2-4635-b865-45323f73f6c3] Successfully put 
> StandardFlowFileRecord[uuid=a4cc19f5-cd2
> 4-4be7-8157-21f2609fa8cd,claim=StandardContentClaim 
> [resourceClaim=StandardResourceClaim[id=1455912275117-1, container=default, 
> section=1], offset=3072, 
> length=1024],offset=0,name=273670477119454,size=1024] to Amazon S3 in 327 
> milliseconds
> {code}
> The error-but-success behavior appears to happen because the exception is 
> caught, logged, but not re-thrown.  The approximate code path is as follows:
> # PutS3Object::onTrigger method calls ageoffS3Uploads regardless of 
> single-part/multi-part code path
> # ageoffS3Uploads calls getS3AgeoffListAndAgeoffLocalState
> # getS3AgeoffListAndAgeoffLocalState calls s3.listMultipartUploads
> # After the exception, onTrigger proceeds with the single-part upload path
> *Troubleshooting Notes*
> Listing multi-part S3 uploads requires an additional S3 permission, 
> s3:ListBucketMultipartUploads.  I would expect the PutS3Object processor to 
> only require the s3:PutObject permission for single-part uploads.
> I tested that this behavior did not occur in NiFi 0.4.2. I also tested that 
> adding the s3:ListBucketMultipartUploads permission to my AWS credential 
> circumvents the error messages from the S3PutObject processor.



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

[jira] [Commented] (NIFI-1542) PutS3Object Processor Logs Errors Without ListBucketMultipartUploads Permission

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1542: Update how PutS3Object handles a 403 AccessDenied response to a S3 
ListMultipartUploads request.
 * Change log message from error to warning and added note about S3 permissions.
 * Advance the ageoff check time by the check interval as if the request 
succeeded to prevent re-checking on every upload when permission does not exist.

Reviewed by Tony Kurc (tk...@apache.org) (with minor amendments for whitespace 
and error message consistency). This closes #240


> PutS3Object Processor Logs Errors Without ListBucketMultipartUploads 
> Permission
> ---
>
> Key: NIFI-1542
> URL: https://issues.apache.org/jira/browse/NIFI-1542
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.5.0
> Environment: Linux, Chrome
>Reporter: James Wing
>Assignee: Joe Skora
>Priority: Minor
> Fix For: 0.5.1
>
> Attachments: error-checking-s3-multipart-upload-list.png
>
>
> In 0.5.0, I am seeing an error putting objects to Amazon S3 using the 
> PutS3Object processor.  The *put operation itself succeeds*, but a nasty-gram 
> is displayed in the flow and logged as a side effect.  The error text is 
> "Error checking S3 Multipart Upload list for ", from line 698 
> of PutS3Object.java.  This code was introduced in NIFI-1107, expanding the 
> PutS3Object processor with support for S3 multi-part uploads of larger files.
> Logged in nifi-app.log:
> {code}
> 2016-02-19 20:56:24,312 ERROR [Timer-Driven Process Thread-3] 
> o.a.nifi.processors.aws.s3.PutS3Object PutS
> 3Object[id=47df7533-91b2-4635-b865-45323f73f6c3] Error checking S3 Multipart 
> Upload list for batchiq-scra
> tch: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: 
> AccessDenied; Request ID: 7483E76EA
> 52E33C4)
> 2016-02-19 20:56:24,533 INFO [Timer-Driven Process Thread-3] 
> o.a.nifi.processors.aws.s3.PutS3Object PutS3
> Object[id=47df7533-91b2-4635-b865-45323f73f6c3] Successfully put 
> StandardFlowFileRecord[uuid=a4cc19f5-cd2
> 4-4be7-8157-21f2609fa8cd,claim=StandardContentClaim 
> [resourceClaim=StandardResourceClaim[id=1455912275117-1, container=default, 
> section=1], offset=3072, 
> length=1024],offset=0,name=273670477119454,size=1024] to Amazon S3 in 327 
> milliseconds
> {code}
> The error-but-success behavior appears to happen because the exception is 
> caught, logged, but not re-thrown.  The approximate code path is as follows:
> # PutS3Object::onTrigger method calls ageoffS3Uploads regardless of 
> single-part/multi-part code path
> # ageoffS3Uploads calls getS3AgeoffListAndAgeoffLocalState
> # getS3AgeoffListAndAgeoffLocalState calls s3.listMultipartUploads
> # After the exception, onTrigger proceeds with the single-part upload path
> *Troubleshooting Notes*
> Listing multi-part S3 uploads requires an additional S3 permission, 
> s3:ListBucketMultipartUploads.  I would expect the PutS3Object processor to 
> only require the s3:PutObject permission for single-part uploads.
> I tested that this behavior did not occur in NiFi 0.4.2. I also tested that 
> adding the s3:ListBucketMultipartUploads permission to my AWS credential 
> circumvents the error messages from the S3PutObject processor.



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

[jira] [Commented] (NIFI-1529) hadoop-libraries-nar dependency issue for httpclient and httpcore

[ASF subversion and git services (JIRA)]

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

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

Commit a9b34e188dbc73e4a1e7902c7a3c7861a350e971 in nifi's branch 
refs/heads/support/nifi-0.5.x from [~bbende]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=a9b34e1 ]

NIFI-1529 Forcing hadoop-libraries-nar to version 4.2.5 of httpclient and 
httpcore since that is what hadoop-client 2.6.2 normally brings in - Removing 
dependencies from the nar pom that should be transitively brought in by 
hadoop-client - Updating NOTICE files in hadoop-libraries-nar and nifi-assembly 
according to dependency changes

This closes #236


> hadoop-libraries-nar dependency issue for httpclient and httpcore
> -
>
> Key: NIFI-1529
> URL: https://issues.apache.org/jira/browse/NIFI-1529
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.4.0, 0.5.0
>Reporter: Bryan Bende
>Assignee: Bryan Bende
> Fix For: 0.6.0, 0.5.1
>
>
> The following issue was reported:
> 016-02-17 15:23:11,814 ERROR [Timer-Driven Process Thread-7] 
> o.apache.nifi.processors.hadoop.PutHDFS 
> PutHDFS[id=0575cb57-786c-45d9-b9ef-19c15cc01290] Failed to writ
> e to HDFS due to java.lang.NoClassDefFoundError: org/apache/http/Consts
> 2016-02-17 15:23:11,816 ERROR [Timer-Driven Process Thread-7] 
> o.apache.nifi.processors.hadoop.PutHDFS
> java.lang.NoClassDefFoundError: org/apache/http/Consts
>         at 
> org.apache.http.client.utils.URIBuilder.digestURI(URIBuilder.java:181) 
> ~[httpclient-4.4.1.jar:4.4.1]
>         at org.apache.http.client.utils.URIBuilder.(URIBuilder.java:82) 
> ~[httpclient-4.4.1.jar:4.4.1]
>         at 
> org.apache.hadoop.crypto.key.kms.KMSClientProvider.createURL(KMSClientProvider.java:368)
>  ~[hadoop-common-2.6.2.jar:na]
> From looking into this, we have the following transitive dependencies from 
> the hadoop libraries nar:
> - net.java.dev.jets3t:jets3t:jar:0.9.0:compile
> [INFO] |  |  +- org.apache.httpcomponents:httpclient:jar:4.4.1:compile
> [INFO] |  |  +- org.apache.httpcomponents:httpcore:jar:4.1.2:compile
> I believe the 4.4.1 of httpclient is coming from the top level pom which has 
> a dependency management block that forces the client to 4.4.1 and doesn't for 
> core to 4.4.1.
> If we look at httpcore 4.x branch it has the missing Consts class:
> https://github.com/apache/httpcore/tree/4.4.x/httpcore/src/main/java/org/apache/http
> and the 4.1.x branch does not:
> https://github.com/apache/httpcore/tree/4.1.x/httpcore/src/main/java/org/apache/http
> We either need to force both to 4.4.1, or force only the hadoop libraries nar 
> to both be 4.1.2 if that is what it normally brings in.



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

[jira] [Commented] (NIFI-1529) hadoop-libraries-nar dependency issue for httpclient and httpcore

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1529 Forcing hadoop-libraries-nar to version 4.2.5 of httpclient and 
httpcore since that is what hadoop-client 2.6.2 normally brings in - Removing 
dependencies from the nar pom that should be transitively brought in by 
hadoop-client - Updating NOTICE files in hadoop-libraries-nar and nifi-assembly 
according to dependency changes

This closes #236


> hadoop-libraries-nar dependency issue for httpclient and httpcore
> -
>
> Key: NIFI-1529
> URL: https://issues.apache.org/jira/browse/NIFI-1529
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.4.0, 0.5.0
>Reporter: Bryan Bende
>Assignee: Bryan Bende
> Fix For: 0.6.0, 0.5.1
>
>
> The following issue was reported:
> 016-02-17 15:23:11,814 ERROR [Timer-Driven Process Thread-7] 
> o.apache.nifi.processors.hadoop.PutHDFS 
> PutHDFS[id=0575cb57-786c-45d9-b9ef-19c15cc01290] Failed to writ
> e to HDFS due to java.lang.NoClassDefFoundError: org/apache/http/Consts
> 2016-02-17 15:23:11,816 ERROR [Timer-Driven Process Thread-7] 
> o.apache.nifi.processors.hadoop.PutHDFS
> java.lang.NoClassDefFoundError: org/apache/http/Consts
>         at 
> org.apache.http.client.utils.URIBuilder.digestURI(URIBuilder.java:181) 
> ~[httpclient-4.4.1.jar:4.4.1]
>         at org.apache.http.client.utils.URIBuilder.(URIBuilder.java:82) 
> ~[httpclient-4.4.1.jar:4.4.1]
>         at 
> org.apache.hadoop.crypto.key.kms.KMSClientProvider.createURL(KMSClientProvider.java:368)
>  ~[hadoop-common-2.6.2.jar:na]
> From looking into this, we have the following transitive dependencies from 
> the hadoop libraries nar:
> - net.java.dev.jets3t:jets3t:jar:0.9.0:compile
> [INFO] |  |  +- org.apache.httpcomponents:httpclient:jar:4.4.1:compile
> [INFO] |  |  +- org.apache.httpcomponents:httpcore:jar:4.1.2:compile
> I believe the 4.4.1 of httpclient is coming from the top level pom which has 
> a dependency management block that forces the client to 4.4.1 and doesn't for 
> core to 4.4.1.
> If we look at httpcore 4.x branch it has the missing Consts class:
> https://github.com/apache/httpcore/tree/4.4.x/httpcore/src/main/java/org/apache/http
> and the 4.1.x branch does not:
> https://github.com/apache/httpcore/tree/4.1.x/httpcore/src/main/java/org/apache/http
> We either need to force both to 4.4.1, or force only the hadoop libraries nar 
> to both be 4.1.2 if that is what it normally brings in.



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

[jira] [Commented] (NIFI-1497) Access token not included in all requests

[ASF subversion and git services (JIRA)]

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

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

Commit a7195b5fe9f4db7e688761297e47b0cc7612ee3e in nifi's branch 
refs/heads/support/nifi-0.5.x from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=a7195b5 ]

NIFI-1497: - Introducing a one time use password service for use in query 
parameters when accessing UI extensions and downloading resources. - Using one 
time use tokens when accessing ui extensions and downloading resources. - 
Ensuring appropriate roles when accessing component details through the web 
context for custom UIs. - Addressing typo in class name. - Ensuring appropriate 
roles when accessing content through the content access. - Code clean up. - 
Refactoring some basic scripts for accessing JWT tokens so UI extensions can 
reuse common functionality.

Signed-off-by: Bryan Bende 


> Access token not included in all requests
> -
>
> Key: NIFI-1497
> URL: https://issues.apache.org/jira/browse/NIFI-1497
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 0.5.1
>
> Attachments: 0001-NIFI-1497.patch
>
>
> Some requests do not have the access token included with them (specifically 
> custom UIs and view content). Without the access token, the request will fail 
> with Access Denied.



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

[jira] [Commented] (NIFI-1497) Access token not included in all requests

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1497: - Introducing a one time use password service for use in query 
parameters when accessing UI extensions and downloading resources. - Using one 
time use tokens when accessing ui extensions and downloading resources. - 
Ensuring appropriate roles when accessing component details through the web 
context for custom UIs. - Addressing typo in class name. - Ensuring appropriate 
roles when accessing content through the content access. - Code clean up. - 
Refactoring some basic scripts for accessing JWT tokens so UI extensions can 
reuse common functionality.

Signed-off-by: Bryan Bende 


> Access token not included in all requests
> -
>
> Key: NIFI-1497
> URL: https://issues.apache.org/jira/browse/NIFI-1497
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 0.5.1
>
> Attachments: 0001-NIFI-1497.patch
>
>
> Some requests do not have the access token included with them (specifically 
> custom UIs and view content). Without the access token, the request will fail 
> with Access Denied.



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

[jira] [Commented] (NIFI-1527) Resource Claim counts not incremented on restart for FlowFiles that are swapped out

[ASF subversion and git services (JIRA)]

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

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

Commit 773d7fbd189837b1d68ab8f2640a101502198233 in nifi's branch 
refs/heads/support/nifi-0.5.x from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=773d7fb ]

NIFI-1527: Ensure that we increment Claimant Counts for content claims that are 
referenced by Swapped-Out FlowFiles on restart of nifi


> Resource Claim counts not incremented on restart for FlowFiles that are 
> swapped out
> ---
>
> Key: NIFI-1527
> URL: https://issues.apache.org/jira/browse/NIFI-1527
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 0.6.0, 0.5.1
>
> Attachments: 
> 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch, 
> 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch
>
>
> When NiFi starts, it tallies the count of how many FlowFiles reference each 
> Resource Claim and then removes or archives any file in the Content 
> Repository for which there is no claim.
> However, the claim counts are not incremented for data that is swapped out. 
> As a result, the content repository could delete or archive data on restart 
> that it should not. This could potentially result in data loss, if NiFi is 
> restarted while both of the following conditions are met:
> * All FlowFiles that reference a Resource Claim are swapped out
> * Content Repository's archive is disabled, or the archival threshold is 
> already exceeded from data outside of the Content Repository



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

[jira] [Commented] (NIFI-1520) Evaluate/Fix LICENSE/NOTICE entries on Javadoc/Sources bundles

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1520 by default skip javadoc and source jar generation in nars and wars

Reviewed by Tony Kurc (tk...@apache.org). This closes #234


> Evaluate/Fix LICENSE/NOTICE entries on Javadoc/Sources bundles
> --
>
> Key: NIFI-1520
> URL: https://issues.apache.org/jira/browse/NIFI-1520
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 0.5.0
>Reporter: Joseph Witt
>Assignee: Joseph Witt
> Fix For: 0.5.1
>
>
> Sean Busbey NiFi 0.5.0 RC3 finding:
> ---
> * several -source and -javadoc jars contain improper LICENSE/NOTICE files
> (they cover things "in the binary artifact" that are not in the artifact
> containing the LICENSE/NOTICE file)
> ex:
> * -source and -javadoc for war packaging
> * -source for nar packaging
> --



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

[jira] [Commented] (NIFI-1520) Evaluate/Fix LICENSE/NOTICE entries on Javadoc/Sources bundles

[ASF subversion and git services (JIRA)]

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

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

Commit 4d9226c7ef48470a0fd9546fd1197e49d66503ab in nifi's branch 
refs/heads/support/nifi-0.5.x from [~joewitt]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=4d9226c ]

NIFI-1520 by default skip javadoc and source jar generation in nars and wars

reviewed by Tony Kurc (tk...@apache.org)


> Evaluate/Fix LICENSE/NOTICE entries on Javadoc/Sources bundles
> --
>
> Key: NIFI-1520
> URL: https://issues.apache.org/jira/browse/NIFI-1520
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 0.5.0
>Reporter: Joseph Witt
>Assignee: Joseph Witt
> Fix For: 0.5.1
>
>
> Sean Busbey NiFi 0.5.0 RC3 finding:
> ---
> * several -source and -javadoc jars contain improper LICENSE/NOTICE files
> (they cover things "in the binary artifact" that are not in the artifact
> containing the LICENSE/NOTICE file)
> ex:
> * -source and -javadoc for war packaging
> * -source for nar packaging
> --



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

[jira] [Commented] (NIFI-1527) Resource Claim counts not incremented on restart for FlowFiles that are swapped out

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1527: Ensure that we increment Claimant Counts for content claims that are 
referenced by Swapped-Out FlowFiles on restart of nifi


> Resource Claim counts not incremented on restart for FlowFiles that are 
> swapped out
> ---
>
> Key: NIFI-1527
> URL: https://issues.apache.org/jira/browse/NIFI-1527
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 0.5.1
>
> Attachments: 
> 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch, 
> 0001-NIFI-1527-Ensure-that-we-increment-Claimant-Counts-f.patch
>
>
> When NiFi starts, it tallies the count of how many FlowFiles reference each 
> Resource Claim and then removes or archives any file in the Content 
> Repository for which there is no claim.
> However, the claim counts are not incremented for data that is swapped out. 
> As a result, the content repository could delete or archive data on restart 
> that it should not. This could potentially result in data loss, if NiFi is 
> restarted while both of the following conditions are met:
> * All FlowFiles that reference a Resource Claim are swapped out
> * Content Repository's archive is disabled, or the archival threshold is 
> already exceeded from data outside of the Content Repository



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

[jira] [Commented] (NIFI-1501) Test Monitor Activity has spurious failures

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1501 : Test Monitor Activity has spurious failures.

Added Timeout for the test. So, in case something goes South, threshold will 
never be more that that Timeout period.

Reviewed with amendments for whitespace by Tony Kurc (tk...@apache.org). This 
closes #225


> Test Monitor Activity has spurious failures
> ---
>
> Key: NIFI-1501
> URL: https://issues.apache.org/jira/browse/NIFI-1501
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Joseph Witt
> Attachments: 
> 0001-Fix-Nifi-1501-Test-Monitor-Activity-has-spurious-fai.patch, 
> 0002-Added-Timeout-for-the-test-.-So-in-case-something-go.patch
>
>
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.816 sec <<< 
> FAILURE! - in org.apache.nifi.processors.standard.TestMonitorActivity
> testFirstRunNoMessages(org.apache.nifi.processors.standard.TestMonitorActivity)
>   Time elapsed: 1.321 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<0> but was:<1>
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:645)
>   at org.junit.Assert.assertEquals(Assert.java:631)
>   at 
> org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:330)
>   at 
> org.apache.nifi.processors.standard.TestMonitorActivity.testFirstRunNoMessages(TestMonitorActivity.java:204)



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

[jira] [Commented] (NIFI-1063) fix PutHDFS logger message when error is caught

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1063 Fixed exception logging

Fixed logging of an exception in PutHDFS

Reviewed by Tony Kurc (tk...@apache.org). This closes #226


> fix PutHDFS logger message when error is caught
> ---
>
> Key: NIFI-1063
> URL: https://issues.apache.org/jira/browse/NIFI-1063
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3.0
>Reporter: Tony Kurc
>Assignee: Tony Kurc
>Priority: Trivial
>  Labels: beginner, newbie
>
> I don't believe this is the right "format string" for this message:
> {code}
> getLogger().error("Failed to write to HDFS due to {}", t);
> {code}
> This is what is shown in logs:
> {noformat}
> 2015-10-24 22:56:31,004 ERROR [Timer-Driven Process Thread-2] 
> o.apache.nifi.processors.hadoop.PutHDFS 
> [PutHDFS[id=3c30a474-86b4-45fc-b771-95d7a1b5054d]] Failed to write to HDFS 
> due to {}
> {noformat}



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

[jira] [Commented] (NIFI-1514) ExecuteStreamCommand does not split command line arguments by provided separator when these come from expression language evaluation

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1514 Fixed ExecuteStreamCommand when expressions in command arguments are 
used, contents are not split by command separator

This closes #223.

Signed-off-by: Aldrin Piri 


> ExecuteStreamCommand does not split command line arguments by provided 
> separator when these come from expression language evaluation
> 
>
> Key: NIFI-1514
> URL: https://issues.apache.org/jira/browse/NIFI-1514
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.5.0, 0.4.1
>Reporter: Michal Klempa
>Priority: Trivial
>
> When Comannd Arguments property contains expression to be evaluated, the 
> expression is taken as one command argument instead of being splitted using 
> argument separator.
> To reproduce the problem:
> 1. Create DataFlow
> 2. Add GenerateFlowFile processor, File Size: 10kB
> 3. Connect GenerateFlowFile -> success -> UpdateAttribute processor
> 4. In UpdateAttribute: create attribute optionalArgs with contents: "-c 5"
> 5. Connect UpdateAttribute -> success -> ExecuteStreamCommand
> 6. Configure ExecuteStreamCommand to execute Command Path: "ping", Command 
> Arguments: "${optionalArgs} google.com", Argument Delimiter: " " (spacebar), 
> Ignore STDIN: true, auto terminate: original
> 7. Connect ExecuteStreamCommand -> output stream - > LogAttribute to see some 
> output. LogAttribute auto terminate: success, Log Level: error, Log Payload: 
> true.
> 8. Run the flow.
> Expected output:
> 1. ExecuteStreamCommand issues command ping with args:[ "-c", "5", 
> "google.com"]
> Actual output:
> 1. ExecuteStreamCommand puts the "-c 5" into single arg for ProcessBuilder. 
> args: are ["-c 5", "google.com"]
> This behavior is no problem for ping utility (as it reparses the commandline 
> again to search for argument separator), but there are tools (like snmpwalk 
> in my case), which are dumb enough not to parse command line arguments 
> properly, when they are sent inproperly by ProcessBuilder.
> The problem is apparently in lines: ExecuteStreamCommand.java: 305-306, where 
> arguments splitting on argument separator is done before expression language 
> evaluation. The fix should reverse the operation: first evaluate expression 
> language and the split the arguments by separator.



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

[jira] [Commented] (NIFI-1379) Perform Release Management Functions for 0.5.0

[ASF subversion and git services (JIRA)]

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

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

Commit 1730778 from [~tkurc] in branch 'site/trunk'
[ https://svn.apache.org/r1730778 ]

NIFI-1379: updating index.html doc

> Perform Release Management Functions for 0.5.0
> --
>
> Key: NIFI-1379
> URL: https://issues.apache.org/jira/browse/NIFI-1379
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.0
>Reporter: Joseph Witt
>Assignee: Tony Kurc
> Fix For: 0.5.0
>
> Attachments: NIFI-1379.000.patch
>
>
> Need to migrate all poms to 0.5.0
> {code}
> mvn versions:set
> mvn versions:commit
> {code}



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

[jira] [Commented] (NIFI-1379) Perform Release Management Functions for 0.5.0

[ASF subversion and git services (JIRA)]

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

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

Commit 1730777 from [~tkurc] in branch 'site/trunk'
[ https://svn.apache.org/r1730777 ]

NIFI-1379: Updating components doc

> Perform Release Management Functions for 0.5.0
> --
>
> Key: NIFI-1379
> URL: https://issues.apache.org/jira/browse/NIFI-1379
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.0
>Reporter: Joseph Witt
>Assignee: Tony Kurc
> Fix For: 0.5.0
>
> Attachments: NIFI-1379.000.patch
>
>
> Need to migrate all poms to 0.5.0
> {code}
> mvn versions:set
> mvn versions:commit
> {code}



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

[jira] [Commented] (NIFI-1379) Perform Release Management Functions for 0.5.0

[ASF subversion and git services (JIRA)]

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

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

Commit 1730776 from [~tkurc] in branch 'site/trunk'
[ https://svn.apache.org/r1730776 ]

NIFI-1379: Update rest-api

> Perform Release Management Functions for 0.5.0
> --
>
> Key: NIFI-1379
> URL: https://issues.apache.org/jira/browse/NIFI-1379
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.0
>Reporter: Joseph Witt
>Assignee: Tony Kurc
> Fix For: 0.5.0
>
> Attachments: NIFI-1379.000.patch
>
>
> Need to migrate all poms to 0.5.0
> {code}
> mvn versions:set
> mvn versions:commit
> {code}



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

[jira] [Commented] (NIFI-1379) Perform Release Management Functions for 0.5.0

[ASF subversion and git services (JIRA)]

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

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

Commit 1730775 from [~tkurc] in branch 'site/trunk'
[ https://svn.apache.org/r1730775 ]

NIFI-1379: Updating docs

> Perform Release Management Functions for 0.5.0
> --
>
> Key: NIFI-1379
> URL: https://issues.apache.org/jira/browse/NIFI-1379
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.0
>Reporter: Joseph Witt
>Assignee: Tony Kurc
> Fix For: 0.5.0
>
> Attachments: NIFI-1379.000.patch
>
>
> Need to migrate all poms to 0.5.0
> {code}
> mvn versions:set
> mvn versions:commit
> {code}



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

[jira] [Commented] (NIFI-1379) Perform Release Management Functions for 0.5.0

[ASF subversion and git services (JIRA)]

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

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

Commit 1730774 from [~tkurc] in branch 'site/trunk'
[ https://svn.apache.org/r1730774 ]

NIFI-1379: Update download page (and typo on release guide)

> Perform Release Management Functions for 0.5.0
> --
>
> Key: NIFI-1379
> URL: https://issues.apache.org/jira/browse/NIFI-1379
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.0
>Reporter: Joseph Witt
>Assignee: Tony Kurc
> Fix For: 0.5.0
>
> Attachments: NIFI-1379.000.patch
>
>
> Need to migrate all poms to 0.5.0
> {code}
> mvn versions:set
> mvn versions:commit
> {code}



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

[jira] [Commented] (NIFI-1379) Perform Release Management Functions for 0.5.0

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1379-RC3 prepare for next development iteration


> Perform Release Management Functions for 0.5.0
> --
>
> Key: NIFI-1379
> URL: https://issues.apache.org/jira/browse/NIFI-1379
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Tools and Build
>Affects Versions: 0.5.0
>Reporter: Joseph Witt
>Assignee: Tony Kurc
> Fix For: 0.5.0
>
> Attachments: NIFI-1379.000.patch
>
>
> Need to migrate all poms to 0.5.0
> {code}
> mvn versions:set
> mvn versions:commit
> {code}



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