[jira] [Created] (NIFI-3602) GetFile NullPointerException on 1.1.1

[Mahfuzul Amin (JIRA)]

Mahfuzul Amin created NIFI-3602:
---

 Summary: GetFile NullPointerException on 1.1.1
 Key: NIFI-3602
 URL: https://issues.apache.org/jira/browse/NIFI-3602
 Project: Apache NiFi
  Issue Type: Bug
Affects Versions: 1.1.1
 Environment: API version is 0.6.1 and deployed on 1.1.1
Reporter: Mahfuzul Amin


GetFile processor throws NullPointerException randomly on 1.1.1. Sometime it 
throws error and sometime it works. Recently we have installed the version 
1.1.1. We have another server where nifi version 0.6.1 is running. According to 
our observation GetFile works fine on version 0.6.1. The stacktarce is given 
below:

2017-03-15 12:59:46,886 ERROR [Timer-Driven Process Thread-4] 
o.a.nifi.processors.standard.GetFile 
GetFile[id=015a107a-9d19-1370-9b86-0816f7e1f7f2] Failed to retrieve files due 
to org.apache.nifi.processor.exception.FlowFileAccessException: Failed to 
import data from /var/opt/wdp/nifi-1.1.1/deploy/flow.xml.gz for 
StandardFlowFileRecord[uuid=6c4b21f3-6105-480f-a1bb-d955a40d416b,claim=,offset=0,name=4327546774486623,size=0]
 due to java.lang.NullPointerException
2017-03-15 12:59:46,900 ERROR [Timer-Driven Process Thread-4] 
o.a.nifi.processors.standard.GetFile
org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import 
data from /var/opt/wdp/nifi-1.1.1/deploy/flow.xml.gz for 
StandardFlowFileRecord[uuid=6c4b21f3-6105-480f-a1bb-d955a40d416b,claim=,offset=0,name=4327546774486623,size=0]
 due to java.lang.NullPointerException
at 
org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:2649)
 ~[na:na]
at 
org.apache.nifi.processors.standard.GetFile.onTrigger(GetFile.java:432) 
~[nifi-standard-processors-1.1.1.jar:1.1.1]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 [nifi-api-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_111]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_111]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_111]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_111]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_111]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_111]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
Caused by: java.lang.NullPointerException: null



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3596) GenerateTableFetch - Add attributes to generated flow files to ease SQL query overwrite

[Pierre Villard (JIRA)]

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

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

> GenerateTableFetch - Add attributes to generated flow files to ease SQL query 
> overwrite
> ---
>
> Key: NIFI-3596
> URL: https://issues.apache.org/jira/browse/NIFI-3596
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Trivial
> Fix For: 1.2.0
>
>
> The GenerateTableFetch processor will generate a SQL query based on the 
> provided parameters but, if the specific DB adapter is not available, it 
> might be necessary to overwrite the SQL query in the ExecuteSQL processor. To 
> do that it would be nice to have each part of the query as attributes to take 
> advantage of expression language.
> Current workaround (when using GenerateTableFetch against a DB2 database for 
> example) is to have an intermediary ExtractText processor and have a regex 
> extracting each part of the generated query.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3596) GenerateTableFetch - Add attributes to generated flow files to ease SQL query overwrite

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3596:
--

GitHub user pvillard31 opened a pull request:

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

NIFI-3596 - added attributes to GenerateTableFetch processor

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [X] Have you written or updated unit tests to verify your changes?

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

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


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

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

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

https://github.com/apache/nifi/pull/1596.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1596


commit 6367110cf620ac765ba5f556e6f11fbe0545e639
Author: Pierre Villard 
Date:   2017-03-14T22:19:05Z

NIFI-3596 - added attributes to GenerateTableFetch processor




> GenerateTableFetch - Add attributes to generated flow files to ease SQL query 
> overwrite
> ---
>
> Key: NIFI-3596
> URL: https://issues.apache.org/jira/browse/NIFI-3596
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Trivial
>
> The GenerateTableFetch processor will generate a SQL query based on the 
> provided parameters but, if the specific DB adapter is not available, it 
> might be necessary to overwrite the SQL query in the ExecuteSQL processor. To 
> do that it would be nice to have each part of the query as attributes to take 
> advantage of expression language.
> Current workaround (when using GenerateTableFetch against a DB2 database for 
> example) is to have an intermediary ExtractText processor and have a regex 
> extracting each part of the generated query.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1596: NIFI-3596 - added attributes to GenerateTableFetch ...

[pvillard31]

GitHub user pvillard31 opened a pull request:

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

NIFI-3596 - added attributes to GenerateTableFetch processor

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [X] Have you written or updated unit tests to verify your changes?

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

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


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

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

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

https://github.com/apache/nifi/pull/1596.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1596


commit 6367110cf620ac765ba5f556e6f11fbe0545e639
Author: Pierre Villard 
Date:   2017-03-14T22:19:05Z

NIFI-3596 - added attributes to GenerateTableFetch processor




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

[jira] [Commented] (NIFI-3570) Add Registry page to nifi-site

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3570:
--

GitHub user andrewmlim opened a pull request:

https://github.com/apache/nifi-site/pull/15

NIFI-3570 Add Registry page to nifi-site

Replaced MiNiFi link in topbar with a Subprojects drop-down that contains 
MiNiFI and Registry.  Also corrected Contribution Guide link in topbar files so 
it would be considered an external link.

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

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

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

https://github.com/apache/nifi-site/pull/15.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15


commit 8710dafe41f0a0a07ca8fc62aa71ae5a073c3d6e
Author: Andrew Lim 
Date:   2017-03-14T20:48:50Z

NIFI-3570 Add Registry page to nifi-site




> Add Registry page to nifi-site
> --
>
> Key: NIFI-3570
> URL: https://issues.apache.org/jira/browse/NIFI-3570
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> Create an initial landing page to provide access to Registry subproject info 
> and links such as:
> *Feature Proposal*
> https://cwiki.apache.org/confluence/display/NIFI/Configuration+Management+of+Flows
> *Git*
> https://github.com/apache/nifi-registry
> git://git.apache.org/nifi-registry.git
> *JIRA*
> https://issues.apache.org/jira/browse/NIFIREG
> Will ultimately want to integrate more web content similar to what is 
> available for the MiNiFi subproject, but most of that content does not exist 
> yet (Downloads, Release Notes, Documentation, etc.).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi-site pull request #15: NIFI-3570 Add Registry page to nifi-site

[andrewmlim]

GitHub user andrewmlim opened a pull request:

https://github.com/apache/nifi-site/pull/15

NIFI-3570 Add Registry page to nifi-site

Replaced MiNiFi link in topbar with a Subprojects drop-down that contains 
MiNiFI and Registry.  Also corrected Contribution Guide link in topbar files so 
it would be considered an external link.

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

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

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

https://github.com/apache/nifi-site/pull/15.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15


commit 8710dafe41f0a0a07ca8fc62aa71ae5a073c3d6e
Author: Andrew Lim 
Date:   2017-03-14T20:48:50Z

NIFI-3570 Add Registry page to nifi-site




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

[jira] [Assigned] (NIFI-2697) UI - Revert RemoteProcessGroup Port configuration on failed update request

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2697:
-

Assignee: Scott Aslan

> UI - Revert RemoteProcessGroup Port configuration on failed update request
> --
>
> Key: NIFI-2697
> URL: https://issues.apache.org/jira/browse/NIFI-2697
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
>Priority: Minor
>
> Another follow up to NIFI-2687 [1] is that when the request to update a 
> RemoteProcessGroup Port fails, the values in the UI do not revert to their 
> previously configured values. Another option (for the configuration dialog) 
> may be to keep the dialog open until there is a successful response.
> [1] https://issues.apache.org/jira/browse/NIFI-2687



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFIREG-1) Create Initial Project Structure

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFIREG-1:
--
Fix Version/s: 0.0.1

> Create Initial Project Structure
> 
>
> Key: NIFIREG-1
> URL: https://issues.apache.org/jira/browse/NIFIREG-1
> Project: NiFi Registry
>  Issue Type: New Feature
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 0.0.1
>
>
> Create an initial project structure similar to NiFi with an assembly that 
> produces a binary artifact (tar/zip) to run the application. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFIREG-1) Create Initial Project Structure

[Bryan Bende (JIRA)]

Bryan Bende created NIFIREG-1:
-

 Summary: Create Initial Project Structure
 Key: NIFIREG-1
 URL: https://issues.apache.org/jira/browse/NIFIREG-1
 Project: NiFi Registry
  Issue Type: New Feature
Reporter: Bryan Bende
Assignee: Bryan Bende
Priority: Minor


Create an initial project structure similar to NiFi with an assembly that 
produces a binary artifact (tar/zip) to run the application. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-3601) Add attribute specifying the number of rows that were inserted as the result of running PutSQL

[Jeremy Dyer (JIRA)]

Jeremy Dyer created NIFI-3601:
-

 Summary: Add attribute specifying the number of rows that were 
inserted as the result of running PutSQL
 Key: NIFI-3601
 URL: https://issues.apache.org/jira/browse/NIFI-3601
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Jeremy Dyer
Assignee: Jeremy Dyer


Adding an attribute to PutSQL success relationship that would specify the 
number of rows that were inserted as the result of an insert sql statement so 
that downstream processors can examine how many rows were successfully inserted 
into the table



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi-minifi-cpp issue #66: MINIFI-215: IOS port, add OPENSSL_SUPPORT/YAML_SU...

[benqiu2016]

Github user benqiu2016 commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/66
  
i think we may need to revisit the way to do MARCO in the later stage.


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

[GitHub] nifi-minifi-cpp pull request #66: MINIFI-215: IOS port, add OPENSSL_SUPPORT/...

[benqiu2016]

Github user benqiu2016 closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/66


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

[GitHub] nifi-minifi-cpp issue #66: MINIFI-215: IOS port, add OPENSSL_SUPPORT/YAML_SU...

[bqiust]

Github user bqiust commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/66
  
@apiri @phrocker any feedback? i updated the above comments. Thanks. Bin



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

[jira] [Commented] (NIFI-3586) Nifi is not returning PID in Windows

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3586:
--

Github user PuspenduBanerjee commented on the issue:

https://github.com/apache/nifi/pull/1586
  
@mosermw here goes one more Windows specific issue.


> Nifi is not returning PID in Windows
> 
>
> Key: NIFI-3586
> URL: https://issues.apache.org/jira/browse/NIFI-3586
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0, 0.5.0, 0.6.0, 0.7.0, 1.2.0, 1.1.1, 1.0.1
> Environment: Java <=8, Windows
>Reporter: Puspendu Banerjee
>Priority: Minor
>
> Nifi PID is unavailable during startup under Windows



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1586: NIFI-3586: Fix for retrieving ProcessID for NiFi under win...

[PuspenduBanerjee]

Github user PuspenduBanerjee commented on the issue:

https://github.com/apache/nifi/pull/1586
  
@mosermw here goes one more Windows specific issue.


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

[jira] [Resolved] (NIFI-3128) UI - Improve Controller Service UX

[Scott Aslan (JIRA)]

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

Scott Aslan resolved NIFI-3128.
---
Resolution: Fixed

> UI - Improve Controller Service UX
> --
>
> Key: NIFI-3128
> URL: https://issues.apache.org/jira/browse/NIFI-3128
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.2.0
>
>
> Need to improve the experience around Controller Service management.
> - Accessing Controller Services according to their scope.
> - Showing where a Controller Services is defined. Especially when permissions 
> to the service are not granted. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (NIFI-3128) UI - Improve Controller Service UX

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-3128:
-

Assignee: Scott Aslan

> UI - Improve Controller Service UX
> --
>
> Key: NIFI-3128
> URL: https://issues.apache.org/jira/browse/NIFI-3128
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.2.0
>
>
> Need to improve the experience around Controller Service management.
> - Accessing Controller Services according to their scope.
> - Showing where a Controller Services is defined. Especially when permissions 
> to the service are not granted. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3246) UI - Prevent editing of inherited Controller Services

[Scott Aslan (JIRA)]

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

Scott Aslan updated NIFI-3246:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> UI - Prevent editing of inherited Controller Services
> -
>
> Key: NIFI-3246
> URL: https://issues.apache.org/jira/browse/NIFI-3246
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
>
> The Process Group configuration dialog shows all available Controller 
> Services. However, services that are not defined in the current Process Group 
> should not be editable in place. We should support a go-to link that allows 
> the user to jump to where that service is defined. This will help 
> differentiate the services that are defined locally with those that are 
> inherited and is more consistent with other inheritance like policy 
> management.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3246) UI - Prevent editing of inherited Controller Services

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3246:
--

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1594
  
Thanks @mcgilman this has been merged to master.


> UI - Prevent editing of inherited Controller Services
> -
>
> Key: NIFI-3246
> URL: https://issues.apache.org/jira/browse/NIFI-3246
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
>
> The Process Group configuration dialog shows all available Controller 
> Services. However, services that are not defined in the current Process Group 
> should not be editable in place. We should support a go-to link that allows 
> the user to jump to where that service is defined. This will help 
> differentiate the services that are defined locally with those that are 
> inherited and is more consistent with other inheritance like policy 
> management.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3246) UI - Prevent editing of inherited Controller Services

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3246:
--

Github user asfgit closed the pull request at:

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


> UI - Prevent editing of inherited Controller Services
> -
>
> Key: NIFI-3246
> URL: https://issues.apache.org/jira/browse/NIFI-3246
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
>
> The Process Group configuration dialog shows all available Controller 
> Services. However, services that are not defined in the current Process Group 
> should not be editable in place. We should support a go-to link that allows 
> the user to jump to where that service is defined. This will help 
> differentiate the services that are defined locally with those that are 
> inherited and is more consistent with other inheritance like policy 
> management.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3246) UI - Prevent editing of inherited Controller Services

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3246:
- Preventing the editing of controller services that are defined in an ancestor 
process group.
- Adding a go to link for users to easily navigate to where services are 
actually defined.

This closes #1594

Signed-off-by: Scott Aslan 


> UI - Prevent editing of inherited Controller Services
> -
>
> Key: NIFI-3246
> URL: https://issues.apache.org/jira/browse/NIFI-3246
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
>
> The Process Group configuration dialog shows all available Controller 
> Services. However, services that are not defined in the current Process Group 
> should not be editable in place. We should support a go-to link that allows 
> the user to jump to where that service is defined. This will help 
> differentiate the services that are defined locally with those that are 
> inherited and is more consistent with other inheritance like policy 
> management.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1594: NIFI-3246: Prevent editing of inherited Controller Service...

[scottyaslan]

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1594
  
Thanks @mcgilman this has been merged to master.


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

[GitHub] nifi pull request #1594: NIFI-3246: Prevent editing of inherited Controller ...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[jira] [Commented] (NIFI-3600) Improve logging and relationship routing for failures in DeleteHDFS

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3600:
--

GitHub user jdye64 opened a pull request:

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

NIFI-3600 Improve logging and relationship routing for failures in De…

…leteHDFS

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

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

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

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


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

$ git pull https://github.com/jdye64/nifi NIFI-3600

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

https://github.com/apache/nifi/pull/1595.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1595






> Improve logging and relationship routing for failures in DeleteHDFS
> ---
>
> Key: NIFI-3600
> URL: https://issues.apache.org/jira/browse/NIFI-3600
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Jeremy Dyer
>Assignee: Jeremy Dyer
>
> Currently if DeleteHDFS attempts to delete a file and does not have 
> permissions to delete that file the flowfile session is rolled back and 
> penalized. This causes the incoming connection into DeleteHDFS to build up 
> over time and not process at all.
> This enhancement would add a new relationship to DeleteHDFS where files 
> failures to delete a file strictly tied to invalid permissions would be 
> routed given the end user the opportunity to react to those invalid 
> permissions through another approach.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3600) Improve logging and relationship routing for failures in DeleteHDFS

[Jeremy Dyer (JIRA)]

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

Jeremy Dyer updated NIFI-3600:
--
Status: Patch Available  (was: Open)

> Improve logging and relationship routing for failures in DeleteHDFS
> ---
>
> Key: NIFI-3600
> URL: https://issues.apache.org/jira/browse/NIFI-3600
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Jeremy Dyer
>Assignee: Jeremy Dyer
>
> Currently if DeleteHDFS attempts to delete a file and does not have 
> permissions to delete that file the flowfile session is rolled back and 
> penalized. This causes the incoming connection into DeleteHDFS to build up 
> over time and not process at all.
> This enhancement would add a new relationship to DeleteHDFS where files 
> failures to delete a file strictly tied to invalid permissions would be 
> routed given the end user the opportunity to react to those invalid 
> permissions through another approach.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1595: NIFI-3600 Improve logging and relationship routing ...

[jdye64]

GitHub user jdye64 opened a pull request:

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

NIFI-3600 Improve logging and relationship routing for failures in De…

…leteHDFS

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

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

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

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


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

$ git pull https://github.com/jdye64/nifi NIFI-3600

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

https://github.com/apache/nifi/pull/1595.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1595






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

[jira] [Updated] (NIFI-3579) Nifi Failed to Start: nio Files.getFileStore(Path) is buggy in Windows

[Michael Moser (JIRA)]

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

Michael Moser updated NIFI-3579:

   Resolution: Fixed
Fix Version/s: 1.2.0
   Status: Resolved  (was: Patch Available)

> Nifi Failed to Start: nio Files.getFileStore(Path) is buggy in Windows
> --
>
> Key: NIFI-3579
> URL: https://issues.apache.org/jira/browse/NIFI-3579
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0, 1.1.1
> Environment: Win 10 with Oracle JDK 1.8.0_121 on NTFS
>Reporter: Puspendu Banerjee
>Assignee: Puspendu Banerjee
>Priority: Critical
>  Labels: windows
> Fix For: 1.2.0
>
> Attachments: nifi-app.log
>
>
> Nifi is failing to start due to IOException originating from 
> FileSystemRepository during calls to {code:java}
> Files.getFileStore(path).getTotalSpace();
> Files.getFileStore(path).getUsableSpace();
>  {code} with a read-access denied status.
> It looks like a buggy JDK implementation as on the other hand the following 
> code is yielding result:
> {code:java}
> path.toFile().getTotalSpace();
> path.toFile().getUsableSpace();
> {code}
> Interestingly, the both of the codes are yielding same results for C:\ or 
> System Drive.
> *sample*
> {code:java}
> import java.io.File;
> import java.io.IOException;
> import java.nio.file.Files;
> import java.nio.file.Path;
> import java.nio.file.Paths;
> import java.util.Arrays;
> import static java.lang.System.out;
> public class Blah {
> public static void main(String [] args) throws IOException{
> String [] _paths= {"D:\\workspace\\nifi", "c:\\Program Files"};
> final float divisor=1024 * 1024 * 1024f;
> for(String _path : _paths) {
> try {
> Path path = Paths.get(_path);
> out.println(path.toFile().getTotalSpace() /divisor  + "GB");
> out.println(Files.getFileStore(path).getTotalSpace()/divisor 
> +"GB");
> }catch (Exception ex){
> ex.printStackTrace();
> }
> }
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3579) Nifi Failed to Start: nio Files.getFileStore(Path) is buggy in Windows

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3579:
--

Github user asfgit closed the pull request at:

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


> Nifi Failed to Start: nio Files.getFileStore(Path) is buggy in Windows
> --
>
> Key: NIFI-3579
> URL: https://issues.apache.org/jira/browse/NIFI-3579
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0, 1.1.1
> Environment: Win 10 with Oracle JDK 1.8.0_121 on NTFS
>Reporter: Puspendu Banerjee
>Assignee: Puspendu Banerjee
>Priority: Critical
>  Labels: windows
> Attachments: nifi-app.log
>
>
> Nifi is failing to start due to IOException originating from 
> FileSystemRepository during calls to {code:java}
> Files.getFileStore(path).getTotalSpace();
> Files.getFileStore(path).getUsableSpace();
>  {code} with a read-access denied status.
> It looks like a buggy JDK implementation as on the other hand the following 
> code is yielding result:
> {code:java}
> path.toFile().getTotalSpace();
> path.toFile().getUsableSpace();
> {code}
> Interestingly, the both of the codes are yielding same results for C:\ or 
> System Drive.
> *sample*
> {code:java}
> import java.io.File;
> import java.io.IOException;
> import java.nio.file.Files;
> import java.nio.file.Path;
> import java.nio.file.Paths;
> import java.util.Arrays;
> import static java.lang.System.out;
> public class Blah {
> public static void main(String [] args) throws IOException{
> String [] _paths= {"D:\\workspace\\nifi", "c:\\Program Files"};
> final float divisor=1024 * 1024 * 1024f;
> for(String _path : _paths) {
> try {
> Path path = Paths.get(_path);
> out.println(path.toFile().getTotalSpace() /divisor  + "GB");
> out.println(Files.getFileStore(path).getTotalSpace()/divisor 
> +"GB");
> }catch (Exception ex){
> ex.printStackTrace();
> }
> }
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3579) Nifi Failed to Start: nio Files.getFileStore(Path) is buggy in Windows

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3579 Fix for Windows FileStore issue

Signed-off-by: Mike Moser 

This closes #1580


> Nifi Failed to Start: nio Files.getFileStore(Path) is buggy in Windows
> --
>
> Key: NIFI-3579
> URL: https://issues.apache.org/jira/browse/NIFI-3579
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0, 1.1.1
> Environment: Win 10 with Oracle JDK 1.8.0_121 on NTFS
>Reporter: Puspendu Banerjee
>Assignee: Puspendu Banerjee
>Priority: Critical
>  Labels: windows
> Attachments: nifi-app.log
>
>
> Nifi is failing to start due to IOException originating from 
> FileSystemRepository during calls to {code:java}
> Files.getFileStore(path).getTotalSpace();
> Files.getFileStore(path).getUsableSpace();
>  {code} with a read-access denied status.
> It looks like a buggy JDK implementation as on the other hand the following 
> code is yielding result:
> {code:java}
> path.toFile().getTotalSpace();
> path.toFile().getUsableSpace();
> {code}
> Interestingly, the both of the codes are yielding same results for C:\ or 
> System Drive.
> *sample*
> {code:java}
> import java.io.File;
> import java.io.IOException;
> import java.nio.file.Files;
> import java.nio.file.Path;
> import java.nio.file.Paths;
> import java.util.Arrays;
> import static java.lang.System.out;
> public class Blah {
> public static void main(String [] args) throws IOException{
> String [] _paths= {"D:\\workspace\\nifi", "c:\\Program Files"};
> final float divisor=1024 * 1024 * 1024f;
> for(String _path : _paths) {
> try {
> Path path = Paths.get(_path);
> out.println(path.toFile().getTotalSpace() /divisor  + "GB");
> out.println(Files.getFileStore(path).getTotalSpace()/divisor 
> +"GB");
> }catch (Exception ex){
> ex.printStackTrace();
> }
> }
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1580: Fix for Windows FileStore issue NIFI-3579

[asfgit]

Github user asfgit closed the pull request at:

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


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

[jira] [Commented] (NIFI-3579) Nifi Failed to Start: nio Files.getFileStore(Path) is buggy in Windows

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3579:
--

Github user mosermw commented on the issue:

https://github.com/apache/nifi/pull/1580
  
+1 looks good, passes checkstyle, runs in NiFi on Windows when creating 
content_repository on startup and when it already exists.  I will squash and 
merge to master.  Thanks @PuspenduBanerjee 


> Nifi Failed to Start: nio Files.getFileStore(Path) is buggy in Windows
> --
>
> Key: NIFI-3579
> URL: https://issues.apache.org/jira/browse/NIFI-3579
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0, 1.1.1
> Environment: Win 10 with Oracle JDK 1.8.0_121 on NTFS
>Reporter: Puspendu Banerjee
>Assignee: Puspendu Banerjee
>Priority: Critical
>  Labels: windows
> Attachments: nifi-app.log
>
>
> Nifi is failing to start due to IOException originating from 
> FileSystemRepository during calls to {code:java}
> Files.getFileStore(path).getTotalSpace();
> Files.getFileStore(path).getUsableSpace();
>  {code} with a read-access denied status.
> It looks like a buggy JDK implementation as on the other hand the following 
> code is yielding result:
> {code:java}
> path.toFile().getTotalSpace();
> path.toFile().getUsableSpace();
> {code}
> Interestingly, the both of the codes are yielding same results for C:\ or 
> System Drive.
> *sample*
> {code:java}
> import java.io.File;
> import java.io.IOException;
> import java.nio.file.Files;
> import java.nio.file.Path;
> import java.nio.file.Paths;
> import java.util.Arrays;
> import static java.lang.System.out;
> public class Blah {
> public static void main(String [] args) throws IOException{
> String [] _paths= {"D:\\workspace\\nifi", "c:\\Program Files"};
> final float divisor=1024 * 1024 * 1024f;
> for(String _path : _paths) {
> try {
> Path path = Paths.get(_path);
> out.println(path.toFile().getTotalSpace() /divisor  + "GB");
> out.println(Files.getFileStore(path).getTotalSpace()/divisor 
> +"GB");
> }catch (Exception ex){
> ex.printStackTrace();
> }
> }
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1580: Fix for Windows FileStore issue NIFI-3579

[mosermw]

Github user mosermw commented on the issue:

https://github.com/apache/nifi/pull/1580
  
+1 looks good, passes checkstyle, runs in NiFi on Windows when creating 
content_repository on startup and when it already exists.  I will squash and 
merge to master.  Thanks @PuspenduBanerjee 


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

[jira] [Created] (NIFI-3600) Improve logging and relationship routing for failures in DeleteHDFS

[Jeremy Dyer (JIRA)]

Jeremy Dyer created NIFI-3600:
-

 Summary: Improve logging and relationship routing for failures in 
DeleteHDFS
 Key: NIFI-3600
 URL: https://issues.apache.org/jira/browse/NIFI-3600
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Jeremy Dyer
Assignee: Jeremy Dyer


Currently if DeleteHDFS attempts to delete a file and does not have permissions 
to delete that file the flowfile session is rolled back and penalized. This 
causes the incoming connection into DeleteHDFS to build up over time and not 
process at all.

This enhancement would add a new relationship to DeleteHDFS where files 
failures to delete a file strictly tied to invalid permissions would be routed 
given the end user the opportunity to react to those invalid permissions 
through another approach.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3246) UI - Prevent editing of inherited Controller Services

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3246:
--

Github user scottyaslan commented on the issue:

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


> UI - Prevent editing of inherited Controller Services
> -
>
> Key: NIFI-3246
> URL: https://issues.apache.org/jira/browse/NIFI-3246
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
>
> The Process Group configuration dialog shows all available Controller 
> Services. However, services that are not defined in the current Process Group 
> should not be editable in place. We should support a go-to link that allows 
> the user to jump to where that service is defined. This will help 
> differentiate the services that are defined locally with those that are 
> inherited and is more consistent with other inheritance like policy 
> management.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1594: NIFI-3246: Prevent editing of inherited Controller Service...

[scottyaslan]

Github user scottyaslan commented on the issue:

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


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

[GitHub] nifi pull request #1585: NIFI-3380 Support Multiple Versions of the Same Com...

[mcgilman]

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

https://github.com/apache/nifi/pull/1585#discussion_r105980001
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/jquery/propertytable/jquery.propertytable.js
 ---
@@ -939,27 +939,30 @@
 /**
  * Gets the available controller services that implement the specified 
type and
  * prompts the user to create one.
--- End diff --

Yeah, werid... Will restore.


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

[jira] [Created] (NIFI-3599) Add nifi.properties value to globally set the default backpressure size threshold for each connection

[Jeremy Dyer (JIRA)]

Jeremy Dyer created NIFI-3599:
-

 Summary: Add nifi.properties value to globally set the default 
backpressure size threshold for each connection
 Key: NIFI-3599
 URL: https://issues.apache.org/jira/browse/NIFI-3599
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Configuration
Reporter: Jeremy Dyer
Assignee: Jeremy Dyer


By default each new connection added to the workflow canvas will have a default 
backpressure size threshold of 10,000 objects. While the threshold can be 
changed on a connection level it would be convenient to have a global mechanism 
for setting that value to something other than 10,000. This enhancement would 
add a property to nifi.properties that would allow for this threshold to be set 
globally unless otherwise overridden at the connection level.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3380) Multiple Versions of the Same Component

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3380:
--

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

https://github.com/apache/nifi/pull/1585#discussion_r105980001
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/jquery/propertytable/jquery.propertytable.js
 ---
@@ -939,27 +939,30 @@
 /**
  * Gets the available controller services that implement the specified 
type and
  * prompts the user to create one.
--- End diff --

Yeah, werid... Will restore.


> Multiple Versions of the Same Component
> ---
>
> Key: NIFI-3380
> URL: https://issues.apache.org/jira/browse/NIFI-3380
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Bryan Bende
>Assignee: Bryan Bende
> Fix For: 1.2.0
>
>
> This ticket is to track the work for supporting multiple versions of the same 
> component within NiFi. The overall design for this feature is described in 
> detail at the following wiki page:
> https://cwiki.apache.org/confluence/display/NIFI/Multiple+Versions+of+the+Same+Extension
> This ticket will track only the core NiFi work, and a separate ticket will be 
> created to track enhancements for the NAR Maven Plugin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3380) Multiple Versions of the Same Component

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3380:
--

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

https://github.com/apache/nifi/pull/1585#discussion_r105980032
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/resources/filters/canvas.properties
 ---
@@ -28,6 +28,7 @@ nf.canvas.script.tags=\n\
 \n\
 \n\
+\n\
--- End diff --

Yup.


> Multiple Versions of the Same Component
> ---
>
> Key: NIFI-3380
> URL: https://issues.apache.org/jira/browse/NIFI-3380
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Bryan Bende
>Assignee: Bryan Bende
> Fix For: 1.2.0
>
>
> This ticket is to track the work for supporting multiple versions of the same 
> component within NiFi. The overall design for this feature is described in 
> detail at the following wiki page:
> https://cwiki.apache.org/confluence/display/NIFI/Multiple+Versions+of+the+Same+Extension
> This ticket will track only the core NiFi work, and a separate ticket will be 
> created to track enhancements for the NAR Maven Plugin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1585: NIFI-3380 Support Multiple Versions of the Same Com...

[mcgilman]

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

https://github.com/apache/nifi/pull/1585#discussion_r105980032
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/resources/filters/canvas.properties
 ---
@@ -28,6 +28,7 @@ nf.canvas.script.tags=\n\
 \n\
 \n\
+\n\
--- End diff --

Yup.


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

[jira] [Commented] (NIFI-3380) Multiple Versions of the Same Component

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3380:
--

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

https://github.com/apache/nifi/pull/1585#discussion_r105977072
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/jquery/propertytable/jquery.propertytable.js
 ---
@@ -939,27 +939,30 @@
 /**
  * Gets the available controller services that implement the specified 
type and
  * prompts the user to create one.
--- End diff --

Why did you delete the param docs?


> Multiple Versions of the Same Component
> ---
>
> Key: NIFI-3380
> URL: https://issues.apache.org/jira/browse/NIFI-3380
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Bryan Bende
>Assignee: Bryan Bende
> Fix For: 1.2.0
>
>
> This ticket is to track the work for supporting multiple versions of the same 
> component within NiFi. The overall design for this feature is described in 
> detail at the following wiki page:
> https://cwiki.apache.org/confluence/display/NIFI/Multiple+Versions+of+the+Same+Extension
> This ticket will track only the core NiFi work, and a separate ticket will be 
> created to track enhancements for the NAR Maven Plugin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1585: NIFI-3380 Support Multiple Versions of the Same Com...

[scottyaslan]

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

https://github.com/apache/nifi/pull/1585#discussion_r105977072
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/jquery/propertytable/jquery.propertytable.js
 ---
@@ -939,27 +939,30 @@
 /**
  * Gets the available controller services that implement the specified 
type and
  * prompts the user to create one.
--- End diff --

Why did you delete the param docs?


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

[jira] [Commented] (NIFI-3534) Add support for impersonating a user with HDFS processors

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3534:
--

Github user apsaltis commented on the issue:

https://github.com/apache/nifi/pull/1581
  
@bbende and @trixpan -- I believe my most recent commit addresses both of 
your comments / concerns. Please let me know if I missed something or there is 
anything else you feel needs modification. Thanks again for the feedback.


> Add support for impersonating a user with HDFS processors 
> --
>
> Key: NIFI-3534
> URL: https://issues.apache.org/jira/browse/NIFI-3534
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Andrew Psaltis
>Assignee: Andrew Psaltis
>
> When using the HDFS processors, specifically PutHDFS there are times when a 
> user wants to impersonate a user so that the files written to HDFS are done 
> as the remote user. In cases where Kerberos is not used, this is not 
> possible. Currently there is the ability for NiFi to change the permissions 
> using the Remote Owner and Remote Group, however, this only works if NiFi is 
> running as a user that has HDFS super user privilege. By providing the 
> ability to set a Remote User, NiFi can then impersonate the user and the 
> permission checks will be done in Hadoop land. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1581: NIFI-3534 Add support for impersonating a user with HDFS p...

[apsaltis]

Github user apsaltis commented on the issue:

https://github.com/apache/nifi/pull/1581
  
@bbende and @trixpan -- I believe my most recent commit addresses both of 
your comments / concerns. Please let me know if I missed something or there is 
anything else you feel needs modification. Thanks again for the feedback.


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

[jira] [Commented] (NIFI-3380) Multiple Versions of the Same Component

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3380:
--

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

https://github.com/apache/nifi/pull/1585#discussion_r105973908
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/resources/filters/canvas.properties
 ---
@@ -28,6 +28,7 @@ nf.canvas.script.tags=\n\
 \n\
 \n\
+\n\
--- End diff --

Will need to update the load order here as well...


> Multiple Versions of the Same Component
> ---
>
> Key: NIFI-3380
> URL: https://issues.apache.org/jira/browse/NIFI-3380
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Bryan Bende
>Assignee: Bryan Bende
> Fix For: 1.2.0
>
>
> This ticket is to track the work for supporting multiple versions of the same 
> component within NiFi. The overall design for this feature is described in 
> detail at the following wiki page:
> https://cwiki.apache.org/confluence/display/NIFI/Multiple+Versions+of+the+Same+Extension
> This ticket will track only the core NiFi work, and a separate ticket will be 
> created to track enhancements for the NAR Maven Plugin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1585: NIFI-3380 Support Multiple Versions of the Same Com...

[scottyaslan]

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

https://github.com/apache/nifi/pull/1585#discussion_r105973908
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/resources/filters/canvas.properties
 ---
@@ -28,6 +28,7 @@ nf.canvas.script.tags=\n\
 \n\
 \n\
+\n\
--- End diff --

Will need to update the load order here as well...


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

[GitHub] nifi-minifi-cpp issue #63: MINIFI-217: Implement namespaces.

[phrocker]

Github user phrocker commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/63
  
Also added a fix for MINIFI-236 since that impeded my testing. 


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

[jira] [Updated] (NIFI-3246) UI - Prevent editing of inherited Controller Services

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-3246:
--
Affects Version/s: 1.1.1
   Status: Patch Available  (was: In Progress)

> UI - Prevent editing of inherited Controller Services
> -
>
> Key: NIFI-3246
> URL: https://issues.apache.org/jira/browse/NIFI-3246
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
>
> The Process Group configuration dialog shows all available Controller 
> Services. However, services that are not defined in the current Process Group 
> should not be editable in place. We should support a go-to link that allows 
> the user to jump to where that service is defined. This will help 
> differentiate the services that are defined locally with those that are 
> inherited and is more consistent with other inheritance like policy 
> management.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3246) UI - Prevent editing of inherited Controller Services

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3246:
--

GitHub user mcgilman opened a pull request:

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

NIFI-3246: Prevent editing of inherited Controller Services

NIFI-3246:
- Preventing the editing of controller services that are defined in an 
ancestor process group.
- Adding a go to link for users to easily navigate to where services are 
actually defined.

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

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

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

https://github.com/apache/nifi/pull/1594.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1594


commit c06a082ec9d2a6da95a16d36c021611438ef8485
Author: Matt Gilman 
Date:   2017-03-14T15:08:24Z

NIFI-3246:
- Preventing the editing of controller services that are defined in an 
ancestor process group.
- Adding a go to link for users to easily navigate to where services are 
actually defined.




> UI - Prevent editing of inherited Controller Services
> -
>
> Key: NIFI-3246
> URL: https://issues.apache.org/jira/browse/NIFI-3246
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
>
> The Process Group configuration dialog shows all available Controller 
> Services. However, services that are not defined in the current Process Group 
> should not be editable in place. We should support a go-to link that allows 
> the user to jump to where that service is defined. This will help 
> differentiate the services that are defined locally with those that are 
> inherited and is more consistent with other inheritance like policy 
> management.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1594: NIFI-3246: Prevent editing of inherited Controller ...

[mcgilman]

GitHub user mcgilman opened a pull request:

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

NIFI-3246: Prevent editing of inherited Controller Services

NIFI-3246:
- Preventing the editing of controller services that are defined in an 
ancestor process group.
- Adding a go to link for users to easily navigate to where services are 
actually defined.

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

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

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

https://github.com/apache/nifi/pull/1594.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1594


commit c06a082ec9d2a6da95a16d36c021611438ef8485
Author: Matt Gilman 
Date:   2017-03-14T15:08:24Z

NIFI-3246:
- Preventing the editing of controller services that are defined in an 
ancestor process group.
- Adding a go to link for users to easily navigate to where services are 
actually defined.




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

[jira] [Created] (NIFI-3598) NiFi "Search" will not find any controller service or reporting tasks for name or UUID.

[Matthew Clarke (JIRA)]

Matthew Clarke created NIFI-3598:


 Summary: NiFi "Search" will not find any controller service or 
reporting tasks for name or UUID.
 Key: NIFI-3598
 URL: https://issues.apache.org/jira/browse/NIFI-3598
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Affects Versions: 1.1.0
Reporter: Matthew Clarke


NiFi "Search" will not find any controller service or reporting tasks for name 
or UUID.  This makes it difficult to locate a controller service when you have 
a lot of process groups on your canvas.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-3597) Perform Release of NAR Maven Plugin 1.2.0

[Bryan Bende (JIRA)]

Bryan Bende created NIFI-3597:
-

 Summary: Perform Release of NAR Maven Plugin 1.2.0
 Key: NIFI-3597
 URL: https://issues.apache.org/jira/browse/NIFI-3597
 Project: Apache NiFi
  Issue Type: Task
Reporter: Bryan Bende
Assignee: Bryan Bende
Priority: Minor
 Fix For: nifi-nar-maven-plugin-1.2.0


Perform release manager duties for NAR Maven plugin 1.2.0.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3590) FetchSFTP Move Completion Strategy Remote Host Properties

[Marek Kovar (JIRA)]

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

Marek Kovar commented on NIFI-3590:
---

Maybe I should add that the processor start to work as expected as soon as I've 
replaced the host, port and username values by static values. 

> FetchSFTP Move Completion Strategy Remote Host Properties
> -
>
> Key: NIFI-3590
> URL: https://issues.apache.org/jira/browse/NIFI-3590
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.1
> Environment: Debian Wheezy, jdk1.8
>Reporter: Marek Kovar
>  Labels: newbie
> Attachments: BulletinBoard.png, FlowDefinition.png, InputFlowfile 
> Attributes.png, Processor Properties.png
>
>
> There is an problem to use Move Completion strategy with remote host defined 
> using Expression Language.
> Eg. Port number defined using Expression language (${sftp.remote.port}) is 
> fine for the fetch itself, but for the file renaming it's causing following 
> error:
> {quote}
> 2017-03-13 15:58:06,181 ERROR [Timer-Driven Process Thread-6] 
> o.a.nifi.processors.standard.FetchSFTP
> java.lang.NumberFormatException: For input string: ""
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) 
> ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:592) ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:615) ~[na:1.8.0_111]
> at 
> org.apache.nifi.attribute.expression.language.StandardPropertyValue.asInteger(StandardPropertyValue.java:78)
>  ~[nifi-expression-language-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.getChannel(SFTPTransfer.java:400)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.rename(SFTPTransfer.java:608)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.FetchFileTransfer.onTrigger(FetchFileTransfer.java:316)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  ~[nifi-api-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_111]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_111]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-3596) GenerateTableFetch - Add attributes to generated flow files to ease SQL query overwrite

[Pierre Villard (JIRA)]

Pierre Villard created NIFI-3596:


 Summary: GenerateTableFetch - Add attributes to generated flow 
files to ease SQL query overwrite
 Key: NIFI-3596
 URL: https://issues.apache.org/jira/browse/NIFI-3596
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Extensions
Reporter: Pierre Villard
Assignee: Pierre Villard
Priority: Trivial


The GenerateTableFetch processor will generate a SQL query based on the 
provided parameters but, if the specific DB adapter is not available, it might 
be necessary to overwrite the SQL query in the ExecuteSQL processor. To do that 
it would be nice to have each part of the query as attributes to take advantage 
of expression language.

Current workaround (when using GenerateTableFetch against a DB2 database for 
example) is to have an intermediary ExtractText processor and have a regex 
extracting each part of the generated query.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3590) FetchSFTP Move Completion Strategy Remote Host Properties

[Marek Kovar (JIRA)]

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

Marek Kovar commented on NIFI-3590:
---

Hi. I've uploaded few screenshots. (btw thank you for your effort)

> FetchSFTP Move Completion Strategy Remote Host Properties
> -
>
> Key: NIFI-3590
> URL: https://issues.apache.org/jira/browse/NIFI-3590
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.1
> Environment: Debian Wheezy, jdk1.8
>Reporter: Marek Kovar
>  Labels: newbie
> Attachments: BulletinBoard.png, FlowDefinition.png, InputFlowfile 
> Attributes.png, Processor Properties.png
>
>
> There is an problem to use Move Completion strategy with remote host defined 
> using Expression Language.
> Eg. Port number defined using Expression language (${sftp.remote.port}) is 
> fine for the fetch itself, but for the file renaming it's causing following 
> error:
> {quote}
> 2017-03-13 15:58:06,181 ERROR [Timer-Driven Process Thread-6] 
> o.a.nifi.processors.standard.FetchSFTP
> java.lang.NumberFormatException: For input string: ""
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) 
> ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:592) ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:615) ~[na:1.8.0_111]
> at 
> org.apache.nifi.attribute.expression.language.StandardPropertyValue.asInteger(StandardPropertyValue.java:78)
>  ~[nifi-expression-language-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.getChannel(SFTPTransfer.java:400)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.rename(SFTPTransfer.java:608)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.FetchFileTransfer.onTrigger(FetchFileTransfer.java:316)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  ~[nifi-api-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_111]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_111]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3590) FetchSFTP Move Completion Strategy Remote Host Properties

[Marek Kovar (JIRA)]

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

Marek Kovar updated NIFI-3590:
--
Attachment: BulletinBoard.png

> FetchSFTP Move Completion Strategy Remote Host Properties
> -
>
> Key: NIFI-3590
> URL: https://issues.apache.org/jira/browse/NIFI-3590
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.1
> Environment: Debian Wheezy, jdk1.8
>Reporter: Marek Kovar
>  Labels: newbie
> Attachments: BulletinBoard.png, FlowDefinition.png, InputFlowfile 
> Attributes.png, Processor Properties.png
>
>
> There is an problem to use Move Completion strategy with remote host defined 
> using Expression Language.
> Eg. Port number defined using Expression language (${sftp.remote.port}) is 
> fine for the fetch itself, but for the file renaming it's causing following 
> error:
> {quote}
> 2017-03-13 15:58:06,181 ERROR [Timer-Driven Process Thread-6] 
> o.a.nifi.processors.standard.FetchSFTP
> java.lang.NumberFormatException: For input string: ""
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) 
> ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:592) ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:615) ~[na:1.8.0_111]
> at 
> org.apache.nifi.attribute.expression.language.StandardPropertyValue.asInteger(StandardPropertyValue.java:78)
>  ~[nifi-expression-language-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.getChannel(SFTPTransfer.java:400)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.rename(SFTPTransfer.java:608)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.FetchFileTransfer.onTrigger(FetchFileTransfer.java:316)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  ~[nifi-api-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_111]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_111]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3590) FetchSFTP Move Completion Strategy Remote Host Properties

[Marek Kovar (JIRA)]

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

Marek Kovar updated NIFI-3590:
--
Attachment: Processor Properties.png

> FetchSFTP Move Completion Strategy Remote Host Properties
> -
>
> Key: NIFI-3590
> URL: https://issues.apache.org/jira/browse/NIFI-3590
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.1
> Environment: Debian Wheezy, jdk1.8
>Reporter: Marek Kovar
>  Labels: newbie
> Attachments: FlowDefinition.png, InputFlowfile Attributes.png, 
> Processor Properties.png
>
>
> There is an problem to use Move Completion strategy with remote host defined 
> using Expression Language.
> Eg. Port number defined using Expression language (${sftp.remote.port}) is 
> fine for the fetch itself, but for the file renaming it's causing following 
> error:
> {quote}
> 2017-03-13 15:58:06,181 ERROR [Timer-Driven Process Thread-6] 
> o.a.nifi.processors.standard.FetchSFTP
> java.lang.NumberFormatException: For input string: ""
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) 
> ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:592) ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:615) ~[na:1.8.0_111]
> at 
> org.apache.nifi.attribute.expression.language.StandardPropertyValue.asInteger(StandardPropertyValue.java:78)
>  ~[nifi-expression-language-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.getChannel(SFTPTransfer.java:400)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.rename(SFTPTransfer.java:608)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.FetchFileTransfer.onTrigger(FetchFileTransfer.java:316)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  ~[nifi-api-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_111]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_111]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3590) FetchSFTP Move Completion Strategy Remote Host Properties

[Marek Kovar (JIRA)]

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

Marek Kovar updated NIFI-3590:
--
Attachment: InputFlowfile Attributes.png

> FetchSFTP Move Completion Strategy Remote Host Properties
> -
>
> Key: NIFI-3590
> URL: https://issues.apache.org/jira/browse/NIFI-3590
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.1
> Environment: Debian Wheezy, jdk1.8
>Reporter: Marek Kovar
>  Labels: newbie
> Attachments: FlowDefinition.png, InputFlowfile Attributes.png, 
> Processor Properties.png
>
>
> There is an problem to use Move Completion strategy with remote host defined 
> using Expression Language.
> Eg. Port number defined using Expression language (${sftp.remote.port}) is 
> fine for the fetch itself, but for the file renaming it's causing following 
> error:
> {quote}
> 2017-03-13 15:58:06,181 ERROR [Timer-Driven Process Thread-6] 
> o.a.nifi.processors.standard.FetchSFTP
> java.lang.NumberFormatException: For input string: ""
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) 
> ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:592) ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:615) ~[na:1.8.0_111]
> at 
> org.apache.nifi.attribute.expression.language.StandardPropertyValue.asInteger(StandardPropertyValue.java:78)
>  ~[nifi-expression-language-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.getChannel(SFTPTransfer.java:400)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.rename(SFTPTransfer.java:608)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.FetchFileTransfer.onTrigger(FetchFileTransfer.java:316)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  ~[nifi-api-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_111]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_111]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3590) FetchSFTP Move Completion Strategy Remote Host Properties

[Marek Kovar (JIRA)]

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

Marek Kovar updated NIFI-3590:
--
Attachment: FlowDefinition.png

> FetchSFTP Move Completion Strategy Remote Host Properties
> -
>
> Key: NIFI-3590
> URL: https://issues.apache.org/jira/browse/NIFI-3590
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.1
> Environment: Debian Wheezy, jdk1.8
>Reporter: Marek Kovar
>  Labels: newbie
> Attachments: FlowDefinition.png
>
>
> There is an problem to use Move Completion strategy with remote host defined 
> using Expression Language.
> Eg. Port number defined using Expression language (${sftp.remote.port}) is 
> fine for the fetch itself, but for the file renaming it's causing following 
> error:
> {quote}
> 2017-03-13 15:58:06,181 ERROR [Timer-Driven Process Thread-6] 
> o.a.nifi.processors.standard.FetchSFTP
> java.lang.NumberFormatException: For input string: ""
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) 
> ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:592) ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:615) ~[na:1.8.0_111]
> at 
> org.apache.nifi.attribute.expression.language.StandardPropertyValue.asInteger(StandardPropertyValue.java:78)
>  ~[nifi-expression-language-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.getChannel(SFTPTransfer.java:400)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.rename(SFTPTransfer.java:608)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.FetchFileTransfer.onTrigger(FetchFileTransfer.java:316)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  ~[nifi-api-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_111]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_111]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3590) FetchSFTP Move Completion Strategy Remote Host Properties

[Puspendu Banerjee (JIRA)]

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

Puspendu Banerjee commented on NIFI-3590:
-

please attach a couple of screenshot of your processor to depict the 
configuration.

> FetchSFTP Move Completion Strategy Remote Host Properties
> -
>
> Key: NIFI-3590
> URL: https://issues.apache.org/jira/browse/NIFI-3590
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.1
> Environment: Debian Wheezy, jdk1.8
>Reporter: Marek Kovar
>  Labels: newbie
>
> There is an problem to use Move Completion strategy with remote host defined 
> using Expression Language.
> Eg. Port number defined using Expression language (${sftp.remote.port}) is 
> fine for the fetch itself, but for the file renaming it's causing following 
> error:
> {quote}
> 2017-03-13 15:58:06,181 ERROR [Timer-Driven Process Thread-6] 
> o.a.nifi.processors.standard.FetchSFTP
> java.lang.NumberFormatException: For input string: ""
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) 
> ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:592) ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:615) ~[na:1.8.0_111]
> at 
> org.apache.nifi.attribute.expression.language.StandardPropertyValue.asInteger(StandardPropertyValue.java:78)
>  ~[nifi-expression-language-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.getChannel(SFTPTransfer.java:400)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.rename(SFTPTransfer.java:608)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.FetchFileTransfer.onTrigger(FetchFileTransfer.java:316)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  ~[nifi-api-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_111]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_111]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3590) FetchSFTP Move Completion Strategy Remote Host Properties

[Marek Kovar (JIRA)]

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

Marek Kovar commented on NIFI-3590:
---

I don't know the cause, but the function SFTPTransfer.getChannel is called by 
SFTPTransfer.rename is not able to fetch the Hostname property correctly ant 
therefore it's trying to create a new session.

> FetchSFTP Move Completion Strategy Remote Host Properties
> -
>
> Key: NIFI-3590
> URL: https://issues.apache.org/jira/browse/NIFI-3590
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.1
> Environment: Debian Wheezy, jdk1.8
>Reporter: Marek Kovar
>  Labels: newbie
>
> There is an problem to use Move Completion strategy with remote host defined 
> using Expression Language.
> Eg. Port number defined using Expression language (${sftp.remote.port}) is 
> fine for the fetch itself, but for the file renaming it's causing following 
> error:
> {quote}
> 2017-03-13 15:58:06,181 ERROR [Timer-Driven Process Thread-6] 
> o.a.nifi.processors.standard.FetchSFTP
> java.lang.NumberFormatException: For input string: ""
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) 
> ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:592) ~[na:1.8.0_111]
> at java.lang.Integer.parseInt(Integer.java:615) ~[na:1.8.0_111]
> at 
> org.apache.nifi.attribute.expression.language.StandardPropertyValue.asInteger(StandardPropertyValue.java:78)
>  ~[nifi-expression-language-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.getChannel(SFTPTransfer.java:400)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.util.SFTPTransfer.rename(SFTPTransfer.java:608)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processors.standard.FetchFileTransfer.onTrigger(FetchFileTransfer.java:316)
>  ~[nifi-standard-processors-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  ~[nifi-api-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
>  [nifi-framework-core-1.1.2.jar:1.1.2]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_111]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_111]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_111]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3595) GetFTP NullPointerException on 1.1.1

[Mahfuzul Amin (JIRA)]

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

Mahfuzul Amin updated NIFI-3595:

Description: 
GetFTP processor throws NullPointerException randomly on 1.1.1. Recently we 
have installed the version 1.1.1. We have another server where nifi version 
0.6.1 is running. According to our observation GetFTP works fine on version 
0.6.1. To replicate the flows we have copied the flow.xml.gz file from nifi 
0.6.1 to 1.1.1.Our custom processors are using the API version 0.6.1 in the 
project. The stacktarce is given below:

2017-03-09 02:00:02,467 ERROR [Timer-Driven Process Thread-8] 
o.apache.nifi.processors.standard.GetFTP 
GetFTP[id=1485b432-05c4-463d-a5f2-6ef76840ca6b] Unable to retrieve file 
/FTP_SERVER/agcd/precip/data/IDCKZRDAT0_precip_total_r005_20160806_20160806.nc 
due to java.lang.NullPointerException: 
org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import 
data from org.apache.commons.net.io.SocketInputStream@7ab15a34 for 
StandardFlowFileRecord[uuid=0d0f68e0-cb9f-4c77-8a9a-c0c47a0198a0,claim=,offset=0,name=3769562285059775,size=0]
 due to java.lang.NullPointerException
2017-03-09 02:00:02,471 ERROR [Timer-Driven Process Thread-8] 
o.apache.nifi.processors.standard.GetFTP
org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import 
data from org.apache.commons.net.io.SocketInputStream@7ab15a34 for 
StandardFlowFileRecord[uuid=0d0f68e0-cb9f-4c77-8a9a-c0c47a0198a0,claim=,offset=0,name=3769562285059775,size=0]
 due to java.lang.NullPointerException
at 
org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:2690)
 ~[na:na]
at 
org.apache.nifi.processors.standard.GetFileTransfer.onTrigger(GetFileTransfer.java:194)
 ~[nifi-standard-processors-1.1.1.jar:1.1.1]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 [nifi-api-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.scheduling.QuartzSchedulingAgent$2.run(QuartzSchedulingAgent.java:165)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_111]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_111]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_111]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 [na:1.8.0_111]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_111]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_111]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
Caused by: java.lang.NullPointerException: null

  was:
GetFTP processor throws NullPointerException randomly on 1.1.1. Recently we 
have installed the version 1.1.1. We have another server where nifi version 
0.6.1 is running. According to our observation GetFTP works fine on version 
0.6.1. To replicate the flows we have copied the flow.xml.gz file from nifi 
0.6.1 to 1.1.1.Our custom processors are using the API version 0.6.1 in the 
project. The stacktarce is given below:

2017-03-09 02:00:02,467 ERROR [Timer-Driven Process Thread-8] 
o.apache.nifi.processors.standard.GetFTP 
GetFTP[id=1485b432-05c4-463d-a5f2-6ef76840ca6b] Unable to retrieve file 
/{FTP_SERVER}/agcd/precip/data/IDCKZRDAT0_precip_total_r005_20160806_20160806.nc
 due to java.lang.NullPointerException: 
org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import 
data from org.apache.commons.net.io.SocketInputStream@7ab15a34 for 
StandardFlowFileRecord[uuid=0d0f68e0-cb9f-4c77-8a9a-c0c47a0198a0,claim=,offset=0,name=3769562285059775,size=0]
 due to java.lang.NullPointerException
2017-03-09 02:00:02,471 ERROR [Timer-Driven Process Thread-8] 
o.apache.nifi.processors.standard.GetFTP
org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import 
data from org.apache.commons.net.io.SocketInputStream@7ab15a34 for 
StandardFlowFileRecord[uuid=0d0f68e0-cb9f-4c77-8a9a-c0c47a0198a0,claim=,offset=0,name=3769562285059775,size=0]
 due to java.lang.NullPointerException
at 
org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:2690)
 ~[na:na]
at 

[jira] [Created] (NIFI-3595) GetFTP NullPointerException on 1.1.1

[Mahfuzul Amin (JIRA)]

Mahfuzul Amin created NIFI-3595:
---

 Summary: GetFTP NullPointerException on 1.1.1
 Key: NIFI-3595
 URL: https://issues.apache.org/jira/browse/NIFI-3595
 Project: Apache NiFi
  Issue Type: Bug
Affects Versions: 1.1.1
 Environment: API version is 0.6.1 and deployed on 1.1.1
Reporter: Mahfuzul Amin


GetFTP processor throws NullPointerException randomly on 1.1.1. Recently we 
have installed the version 1.1.1. We have another server where nifi version 
0.6.1 is running. According to our observation GetFTP works fine on version 
0.6.1. To replicate the flows we have copied the flow.xml.gz file from nifi 
0.6.1 to 1.1.1.Our custom processors are using the API version 0.6.1 in the 
project. The stacktarce is given below:

2017-03-09 02:00:02,467 ERROR [Timer-Driven Process Thread-8] 
o.apache.nifi.processors.standard.GetFTP 
GetFTP[id=1485b432-05c4-463d-a5f2-6ef76840ca6b] Unable to retrieve file 
/{FTP_SERVER}/agcd/precip/data/IDCKZRDAT0_precip_total_r005_20160806_20160806.nc
 due to java.lang.NullPointerException: 
org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import 
data from org.apache.commons.net.io.SocketInputStream@7ab15a34 for 
StandardFlowFileRecord[uuid=0d0f68e0-cb9f-4c77-8a9a-c0c47a0198a0,claim=,offset=0,name=3769562285059775,size=0]
 due to java.lang.NullPointerException
2017-03-09 02:00:02,471 ERROR [Timer-Driven Process Thread-8] 
o.apache.nifi.processors.standard.GetFTP
org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import 
data from org.apache.commons.net.io.SocketInputStream@7ab15a34 for 
StandardFlowFileRecord[uuid=0d0f68e0-cb9f-4c77-8a9a-c0c47a0198a0,claim=,offset=0,name=3769562285059775,size=0]
 due to java.lang.NullPointerException
at 
org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:2690)
 ~[na:na]
at 
org.apache.nifi.processors.standard.GetFileTransfer.onTrigger(GetFileTransfer.java:194)
 ~[nifi-standard-processors-1.1.1.jar:1.1.1]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 [nifi-api-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.scheduling.QuartzSchedulingAgent$2.run(QuartzSchedulingAgent.java:165)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_111]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_111]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_111]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 [na:1.8.0_111]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_111]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_111]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
Caused by: java.lang.NullPointerException: null



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)