[jira] [Assigned] (NIFI-3131) run-nifi.bat file fails if run from another directory

[Bryan Rosander (JIRA)]

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

Bryan Rosander reassigned NIFI-3131:


Assignee: Bryan Rosander

> run-nifi.bat file fails if run from another directory
> -
>
> Key: NIFI-3131
> URL: https://issues.apache.org/jira/browse/NIFI-3131
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>Priority: Minor
>
> Attempting to run run-nifi.bat from a different directory (I tried the parent 
> dir) results in problems resolving relative paths and the failure to properly 
> call the nifi-env.bat.
> {code}
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0>bin\run-nifi.bat
> 'nifi-env.bat' is not recognized as an internal or external command,
> operable program or batch file.
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could 
> NOT find resource [logback.groovy]
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could 
> NOT find resource [logback-test.xml]
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found 
> resource [logback.xml] at 
> [file:/C:/Users/bryan/Downloads/nifi-1.1.0-bin/nifi-1.1.0/conf/logback.xml]
> 12:28:57,970 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not 
> set
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - Setting 
> ReconfigureOnChangeFilter scanning period to 30 seconds
> 12:28:57,985 |-INFO in ReconfigureOnChangeFilter{invocationCounter=0} - Will 
> scan for changes in 
> [[C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\conf\logback.xml]] every 
> 30 seconds.
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - Adding 
> ReconfigureOnChangeFilter as a turbo filter
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding 
> LoggerContextListener of type 
> [ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack
> 12:28:58,017 |-INFO in 
> ch.qos.logback.classic.jul.LevelChangePropagator@6debcae2 - Propagating DEBUG 
> level on Logger[ROOT] onto the JUL framework
> 12:28:58,017 |-INFO in 
> ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Starting 
> LoggerContextListener
> 12:28:58,017 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
> About to instantiate appender of type 
> [ch.qos.logback.core.rolling.RollingFileAppender]
> 12:28:58,017 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
> Naming appender as [APP_FILE]
> 12:28:58,126 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No 
> compression will be used
> 12:28:58,126 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use 
> the pattern /nifi-app_%d{-MM-dd_HH}.%i.log for the active file
> 12:28:58,126 |-INFO in 
> ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5ba23b66 - The date pattern 
> is '-MM-dd_HH' from file name pattern 
> '/nifi-app_%d{-MM-dd_HH}.%i.log'.
> 12:28:58,126 |-INFO in 
> ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5ba23b66 - Roll-over at the 
> top of every hour.
> 12:28:58,126 |-INFO in 
> ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5ba23b66 - Setting initial 
> period to Wed Nov 30 12:28:58 EST 2016
> 12:28:58,173 |-INFO in 
> ch.qos.logback.core.rolling.RollingFileAppender[APP_FILE] - Active log file 
> name: /nifi-app.log
> 12:28:58,173 |-INFO in 
> ch.qos.logback.core.rolling.RollingFileAppender[APP_FILE] - File property is 
> set to [/nifi-app.log]
> 12:28:58,173 |-ERROR in 
> ch.qos.logback.core.rolling.RollingFileAppender[APP_FILE] - 
> openFile(/nifi-app.log,true) call failed. java.io.FileNotFoundException: 
> \nifi-app.log (Access is denied)
> at java.io.FileNotFoundException: \nifi-app.log (Access is denied)
> at  at java.io.FileOutputStream.open0(Native Method)
> at  at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at  at java.io.FileOutputStream.(FileOutputStream.java:213)
> at  at 
> ch.qos.logback.core.recovery.ResilientFileOutputStream.(ResilientFileOutputStream.java:28)
> at  at 
> ch.qos.logback.core.FileAppender.openFile(FileAppender.java:148)
> at  at 
> ch.qos.logback.core.FileAppender.start(FileAppender.java:108)
> at  at 
> ch.qos.logback.core.rolling.RollingFileAppender.start(RollingFileAppender.java:86)
> at  at 
> ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
> at  at 
> ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:317)
> at  at 
> ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:196)
> at  

[GitHub] nifi pull request #1293: NIFI-3131 - Qualifying nifi-env in nifi bat scripts...

[brosander]

GitHub user brosander opened a pull request:

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

NIFI-3131 - Qualifying nifi-env in nifi bat scripts, removing popd fr…

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] - N/A - Have you written or updated unit tests to verify your changes?
- [x] - N/A - If adding new dependencies to the code, are these 
dependencies licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [x] - N/A - If applicable, have you updated the LICENSE file, including 
the main LICENSE file under nifi-assembly?
- [x] - N/A - If applicable, have you updated the NOTICE file, including 
the main NOTICE file found under nifi-assembly?
- [x] - N/A - If adding new Properties, have you added .displayName in 
addition to .name (programmatic access) for each of the new properties?

### For documentation related changes:
- [x] - N/A - 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.

…om toolkit bat scripts

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

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

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

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


commit 683c8dde9544acc9de0b4842e44df8a91778c7b2
Author: Bryan Rosander 
Date:   2016-12-02T22:12:44Z

NIFI-3131 - Qualifying nifi-env in nifi bat scripts, removing popd from 
toolkit bat scripts




---
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-3131) run-nifi.bat file fails if run from another directory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3131:
--

GitHub user brosander opened a pull request:

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

NIFI-3131 - Qualifying nifi-env in nifi bat scripts, removing popd fr…

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] - N/A - Have you written or updated unit tests to verify your changes?
- [x] - N/A - If adding new dependencies to the code, are these 
dependencies licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [x] - N/A - If applicable, have you updated the LICENSE file, including 
the main LICENSE file under nifi-assembly?
- [x] - N/A - If applicable, have you updated the NOTICE file, including 
the main NOTICE file found under nifi-assembly?
- [x] - N/A - If adding new Properties, have you added .displayName in 
addition to .name (programmatic access) for each of the new properties?

### For documentation related changes:
- [x] - N/A - 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.

…om toolkit bat scripts

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

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

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

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


commit 683c8dde9544acc9de0b4842e44df8a91778c7b2
Author: Bryan Rosander 
Date:   2016-12-02T22:12:44Z

NIFI-3131 - Qualifying nifi-env in nifi bat scripts, removing popd from 
toolkit bat scripts




> run-nifi.bat file fails if run from another directory
> -
>
> Key: NIFI-3131
> URL: https://issues.apache.org/jira/browse/NIFI-3131
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bryan Rosander
>Priority: Minor
>
> Attempting to run run-nifi.bat from a different directory (I tried the parent 
> dir) results in problems resolving relative paths and the failure to properly 
> call the nifi-env.bat.
> {code}
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0>bin\run-nifi.bat
> 'nifi-env.bat' is not recognized as an internal or external command,
> operable program or batch file.
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could 
> NOT find resource [logback.groovy]
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could 
> NOT find resource [logback-test.xml]
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found 
> resource [logback.xml] at 
> [file:/C:/Users/bryan/Downloads/nifi-1.1.0-bin/nifi-1.1.0/conf/logback.xml]
> 12:28:57,970 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not 
> set
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - Setting 
> ReconfigureOnChangeFilter scanning period to 30 seconds
> 12:28:57,985 |-INFO in ReconfigureOnChangeFilter{invocationCounter=0} - Will 
> scan for changes in 
> [[C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\conf\logback.xml]] every 
> 30 seconds.
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - Adding 
> ReconfigureOnChangeFilter as a turbo filter
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding 
> LoggerContextListener of type 
> [ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack
> 12:28:58,017 |-INFO in 
> ch.qos.logback.classic.jul.LevelChangePropagator@6debcae2 - Propagating DEBUG 
> 

[jira] [Commented] (NIFI-3131) run-nifi.bat file fails if run from another directory

[Bryan Rosander (JIRA)]

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

Bryan Rosander commented on NIFI-3131:
--

affects other status scripts, additionally toolkit bat scripts use popd when 
they haven't done a pushd, resulting in an unintended directory change

> run-nifi.bat file fails if run from another directory
> -
>
> Key: NIFI-3131
> URL: https://issues.apache.org/jira/browse/NIFI-3131
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bryan Rosander
>Priority: Minor
>
> Attempting to run run-nifi.bat from a different directory (I tried the parent 
> dir) results in problems resolving relative paths and the failure to properly 
> call the nifi-env.bat.
> {code}
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0>bin\run-nifi.bat
> 'nifi-env.bat' is not recognized as an internal or external command,
> operable program or batch file.
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could 
> NOT find resource [logback.groovy]
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could 
> NOT find resource [logback-test.xml]
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found 
> resource [logback.xml] at 
> [file:/C:/Users/bryan/Downloads/nifi-1.1.0-bin/nifi-1.1.0/conf/logback.xml]
> 12:28:57,970 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not 
> set
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - Setting 
> ReconfigureOnChangeFilter scanning period to 30 seconds
> 12:28:57,985 |-INFO in ReconfigureOnChangeFilter{invocationCounter=0} - Will 
> scan for changes in 
> [[C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\conf\logback.xml]] every 
> 30 seconds.
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - Adding 
> ReconfigureOnChangeFilter as a turbo filter
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding 
> LoggerContextListener of type 
> [ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack
> 12:28:58,017 |-INFO in 
> ch.qos.logback.classic.jul.LevelChangePropagator@6debcae2 - Propagating DEBUG 
> level on Logger[ROOT] onto the JUL framework
> 12:28:58,017 |-INFO in 
> ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Starting 
> LoggerContextListener
> 12:28:58,017 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
> About to instantiate appender of type 
> [ch.qos.logback.core.rolling.RollingFileAppender]
> 12:28:58,017 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
> Naming appender as [APP_FILE]
> 12:28:58,126 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No 
> compression will be used
> 12:28:58,126 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use 
> the pattern /nifi-app_%d{-MM-dd_HH}.%i.log for the active file
> 12:28:58,126 |-INFO in 
> ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5ba23b66 - The date pattern 
> is '-MM-dd_HH' from file name pattern 
> '/nifi-app_%d{-MM-dd_HH}.%i.log'.
> 12:28:58,126 |-INFO in 
> ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5ba23b66 - Roll-over at the 
> top of every hour.
> 12:28:58,126 |-INFO in 
> ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5ba23b66 - Setting initial 
> period to Wed Nov 30 12:28:58 EST 2016
> 12:28:58,173 |-INFO in 
> ch.qos.logback.core.rolling.RollingFileAppender[APP_FILE] - Active log file 
> name: /nifi-app.log
> 12:28:58,173 |-INFO in 
> ch.qos.logback.core.rolling.RollingFileAppender[APP_FILE] - File property is 
> set to [/nifi-app.log]
> 12:28:58,173 |-ERROR in 
> ch.qos.logback.core.rolling.RollingFileAppender[APP_FILE] - 
> openFile(/nifi-app.log,true) call failed. java.io.FileNotFoundException: 
> \nifi-app.log (Access is denied)
> at java.io.FileNotFoundException: \nifi-app.log (Access is denied)
> at  at java.io.FileOutputStream.open0(Native Method)
> at  at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at  at java.io.FileOutputStream.(FileOutputStream.java:213)
> at  at 
> ch.qos.logback.core.recovery.ResilientFileOutputStream.(ResilientFileOutputStream.java:28)
> at  at 
> ch.qos.logback.core.FileAppender.openFile(FileAppender.java:148)
> at  at 
> ch.qos.logback.core.FileAppender.start(FileAppender.java:108)
> at  at 
> ch.qos.logback.core.rolling.RollingFileAppender.start(RollingFileAppender.java:86)
> at  at 
> ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:96)
> at  at 
> ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:317)

[jira] [Comment Edited] (NIFI-3131) run-nifi.bat file fails if run from another directory

[Bryan Rosander (JIRA)]

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

Bryan Rosander edited comment on NIFI-3131 at 12/2/16 10:10 PM:


affects other nifi bat scripts, additionally toolkit bat scripts use popd when 
they haven't done a pushd, resulting in an unintended directory change


was (Author: bryanrosan...@gmail.com):
affects other status scripts, additionally toolkit bat scripts use popd when 
they haven't done a pushd, resulting in an unintended directory change

> run-nifi.bat file fails if run from another directory
> -
>
> Key: NIFI-3131
> URL: https://issues.apache.org/jira/browse/NIFI-3131
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bryan Rosander
>Priority: Minor
>
> Attempting to run run-nifi.bat from a different directory (I tried the parent 
> dir) results in problems resolving relative paths and the failure to properly 
> call the nifi-env.bat.
> {code}
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0>bin\run-nifi.bat
> 'nifi-env.bat' is not recognized as an internal or external command,
> operable program or batch file.
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could 
> NOT find resource [logback.groovy]
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could 
> NOT find resource [logback-test.xml]
> 12:28:57,861 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found 
> resource [logback.xml] at 
> [file:/C:/Users/bryan/Downloads/nifi-1.1.0-bin/nifi-1.1.0/conf/logback.xml]
> 12:28:57,970 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not 
> set
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - Setting 
> ReconfigureOnChangeFilter scanning period to 30 seconds
> 12:28:57,985 |-INFO in ReconfigureOnChangeFilter{invocationCounter=0} - Will 
> scan for changes in 
> [[C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\conf\logback.xml]] every 
> 30 seconds.
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.ConfigurationAction - Adding 
> ReconfigureOnChangeFilter as a turbo filter
> 12:28:57,985 |-INFO in 
> ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding 
> LoggerContextListener of type 
> [ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack
> 12:28:58,017 |-INFO in 
> ch.qos.logback.classic.jul.LevelChangePropagator@6debcae2 - Propagating DEBUG 
> level on Logger[ROOT] onto the JUL framework
> 12:28:58,017 |-INFO in 
> ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Starting 
> LoggerContextListener
> 12:28:58,017 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
> About to instantiate appender of type 
> [ch.qos.logback.core.rolling.RollingFileAppender]
> 12:28:58,017 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
> Naming appender as [APP_FILE]
> 12:28:58,126 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No 
> compression will be used
> 12:28:58,126 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use 
> the pattern /nifi-app_%d{-MM-dd_HH}.%i.log for the active file
> 12:28:58,126 |-INFO in 
> ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5ba23b66 - The date pattern 
> is '-MM-dd_HH' from file name pattern 
> '/nifi-app_%d{-MM-dd_HH}.%i.log'.
> 12:28:58,126 |-INFO in 
> ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5ba23b66 - Roll-over at the 
> top of every hour.
> 12:28:58,126 |-INFO in 
> ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@5ba23b66 - Setting initial 
> period to Wed Nov 30 12:28:58 EST 2016
> 12:28:58,173 |-INFO in 
> ch.qos.logback.core.rolling.RollingFileAppender[APP_FILE] - Active log file 
> name: /nifi-app.log
> 12:28:58,173 |-INFO in 
> ch.qos.logback.core.rolling.RollingFileAppender[APP_FILE] - File property is 
> set to [/nifi-app.log]
> 12:28:58,173 |-ERROR in 
> ch.qos.logback.core.rolling.RollingFileAppender[APP_FILE] - 
> openFile(/nifi-app.log,true) call failed. java.io.FileNotFoundException: 
> \nifi-app.log (Access is denied)
> at java.io.FileNotFoundException: \nifi-app.log (Access is denied)
> at  at java.io.FileOutputStream.open0(Native Method)
> at  at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at  at java.io.FileOutputStream.(FileOutputStream.java:213)
> at  at 
> ch.qos.logback.core.recovery.ResilientFileOutputStream.(ResilientFileOutputStream.java:28)
> at  at 
> ch.qos.logback.core.FileAppender.openFile(FileAppender.java:148)
> at  at 
> ch.qos.logback.core.FileAppender.start(FileAppender.java:108)
> at  at 
> 

[jira] [Commented] (NIFI-3143) User Guide corrections needed for screenshots and text

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3143:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1291
  
+1, merged. 


> User Guide corrections needed for screenshots and text
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.2.0
>
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there are still some screenshots that need to be added and there 
> were also a couple screenshots that were updated unintentionally.
> Lastly, also noticed some areas to update/fix in the doc.  Most notably:  the 
> addition of the upstream/downstream connections for component context menus 
> and references to "Stats" instead of "Status History".



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

[jira] [Updated] (NIFI-3143) User Guide corrections needed for screenshots and text

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-3143:

Fix Version/s: 1.2.0

> User Guide corrections needed for screenshots and text
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.2.0
>
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there are still some screenshots that need to be added and there 
> were also a couple screenshots that were updated unintentionally.
> Lastly, also noticed some areas to update/fix in the doc.  Most notably:  the 
> addition of the upstream/downstream connections for component context menus 
> and references to "Stats" instead of "Status History".



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

[jira] [Resolved] (NIFI-3143) User Guide corrections needed for screenshots and text

[Andy LoPresto (JIRA)]

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

Andy LoPresto resolved NIFI-3143.
-
Resolution: Fixed

> User Guide corrections needed for screenshots and text
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.2.0
>
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there are still some screenshots that need to be added and there 
> were also a couple screenshots that were updated unintentionally.
> Lastly, also noticed some areas to update/fix in the doc.  Most notably:  the 
> addition of the upstream/downstream connections for component context menus 
> and references to "Stats" instead of "Status History".



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

[jira] [Commented] (NIFI-3143) User Guide corrections needed for screenshots and text

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3143:
--

Github user asfgit closed the pull request at:

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


> User Guide corrections needed for screenshots and text
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there are still some screenshots that need to be added and there 
> were also a couple screenshots that were updated unintentionally.
> Lastly, also noticed some areas to update/fix in the doc.  Most notably:  the 
> addition of the upstream/downstream connections for component context menus 
> and references to "Stats" instead of "Status History".



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

[jira] [Commented] (NIFI-3143) User Guide corrections needed for screenshots and text

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3143 User Guide corrections needed for screenshots and text

This closes #1291.

Signed-off-by: Andy LoPresto 


> User Guide corrections needed for screenshots and text
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there are still some screenshots that need to be added and there 
> were also a couple screenshots that were updated unintentionally.
> Lastly, also noticed some areas to update/fix in the doc.  Most notably:  the 
> addition of the upstream/downstream connections for component context menus 
> and references to "Stats" instead of "Status History".



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

[GitHub] nifi issue #1291: NIFI-3143 User Guide corrections needed for screenshots an...

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1291
  
+1, merged. 


---
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 #1291: NIFI-3143 User Guide corrections needed for screens...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2325) Add support for LDAPS in authentication provider

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2325:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add support for LDAPS in authentication provider
> 
>
> Key: NIFI-2325
> URL: https://issues.apache.org/jira/browse/NIFI-2325
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Joseph Witt
>Assignee: Matt Gilman
> Fix For: 1.2.0
>
>
> [~mcgilman] [~alopresto] please add thoughts if you have them.
> I propose we add support for LDAPS despite StartTLS being the now preferred 
> approach.  This offers more flexibility for use with many of the long 
> standing LDAP environments out there.



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

[jira] [Commented] (NIFI-2325) Add support for LDAPS in authentication provider

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2325:
- Adding support for LDAPS.

This closes #1275.

Signed-off-by: Andy LoPresto 


> Add support for LDAPS in authentication provider
> 
>
> Key: NIFI-2325
> URL: https://issues.apache.org/jira/browse/NIFI-2325
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Joseph Witt
>Assignee: Matt Gilman
> Fix For: 1.2.0
>
>
> [~mcgilman] [~alopresto] please add thoughts if you have them.
> I propose we add support for LDAPS despite StartTLS being the now preferred 
> approach.  This offers more flexibility for use with many of the long 
> standing LDAP environments out there.



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

[jira] [Commented] (NIFI-2325) Add support for LDAPS in authentication provider

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2325:
--

Github user asfgit closed the pull request at:

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


> Add support for LDAPS in authentication provider
> 
>
> Key: NIFI-2325
> URL: https://issues.apache.org/jira/browse/NIFI-2325
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Joseph Witt
>Assignee: Matt Gilman
> Fix For: 1.2.0
>
>
> [~mcgilman] [~alopresto] please add thoughts if you have them.
> I propose we add support for LDAPS despite StartTLS being the now preferred 
> approach.  This offers more flexibility for use with many of the long 
> standing LDAP environments out there.



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

[GitHub] nifi pull request #1275: NIFI-2325 - Add support for LDAPS

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3132) sh scripts resolve log directory, some classpaths incorrectly in cygwin

[Bryan Rosander (JIRA)]

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

Bryan Rosander updated NIFI-3132:
-
Summary: sh scripts resolve log directory, some classpaths incorrectly in 
cygwin  (was: nifi.sh resolves log directory incorrectly in cygwin)

> sh scripts resolve log directory, some classpaths incorrectly in cygwin
> ---
>
> Key: NIFI-3132
> URL: https://issues.apache.org/jira/browse/NIFI-3132
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>Priority: Minor
>
> Running in cygwin results in the incorrect directory used for log directory.  
> The other relative paths appear to resolve properly.
> Please see org.apache.nifi.bootstrap.config.log.dir compared to other paths.
> This results in logs being created at:
> C:\cygdrive\c\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\logs
> instead of:
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\logs
> {code}
> bryan@bryan-win-vm /cygdrive/c/Users/bryan/Downloads/nifi-1.1.0-bin/nifi-1.1.0
> $ bin/nifi.sh run
> Java home: /cygdrive/c/Program Files/Java/jdk1.8.0_92
> NiFi home: C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0
> Bootstrap Config File: 
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\conf\bootstrap.conf
> 2016-11-30 09:57:54,528 INFO [main] org.apache.nifi.bootstrap.Command 
> Starting Apache NiFi...
> 2016-11-30 09:57:54,528 INFO [main] org.apache.nifi.bootstrap.Command Working 
> Directory: C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0
> 2016-11-30 09:57:54,528 INFO [main] org.apache.nifi.bootstrap.Command 
> Command: java -classpath 
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\conf;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\jcl-over-slf4j-1.7.12.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\jul-to-slf4j-1.7.12.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\log4j-over-slf4j-1.7.12.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\logback-classic-1.1.3.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\logback-core-1.1.3.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-api-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-documentation-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-framework-api-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-nar-utils-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-properties-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-runtime-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\slf4j-api-1.7.12.jar
>  -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m 
> -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true 
> -Djava.awt.headless=true -XX:+UseG1GC 
> -Djava.protocol.handler.pkgs=sun.net.www.protocol 
> -Dnifi.properties.file.path=C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\conf\nifi.properties
>  -Dnifi.bootstrap.listen.port=50031 -Dapp=NiFi 
> -Dorg.apache.nifi.bootstrap.config.log.dir=/cygdrive/c/Users/bryan/Downloads/nifi-1.1.0-bin/nifi-1.1.0/logs
>  org.apache.nifi.NiFi
> {code}



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

[jira] [Commented] (NIFI-3143) User Guide corrections needed for screenshots and text

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3143:
--

Github user andrewmlim commented on the issue:

https://github.com/apache/nifi/pull/1291
  
Just wanted to point out that the replacement for 
"configure-reporting-task-settings.png" is intentionally very different from 
what is currently in master.  The one in master is incorrect as it is supposed 
to show the settings tab of the "Configure Reporting Task" window not the "NiFi 
Settings" window with "Reporting Tasks" tab selected.


> User Guide corrections needed for screenshots and text
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there are still some screenshots that need to be added and there 
> were also a couple screenshots that were updated unintentionally.
> Lastly, also noticed some areas to update/fix in the doc.  Most notably:  the 
> addition of the upstream/downstream connections for component context menus 
> and references to "Stats" instead of "Status History".



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

[GitHub] nifi pull request #1292: NIFI-3132 - Using cygpath and quoting paths correct...

[brosander]

GitHub user brosander opened a pull request:

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

NIFI-3132 - Using cygpath and quoting paths correctly in sh scripts w…

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] - N/A - Have you written or updated unit tests to verify your changes?
- [x] - N/A - If adding new dependencies to the code, are these 
dependencies licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [x] - N/A - If applicable, have you updated the LICENSE file, including 
the main LICENSE file under nifi-assembly?
- [x] - N/A - If applicable, have you updated the NOTICE file, including 
the main NOTICE file found under nifi-assembly?
- [x] - N/A - If adding new Properties, have you added .displayName in 
addition to .name (programmatic access) for each of the new properties?

### For documentation related changes:
- [x] - N/A - 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.

…hen run in cygwin

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

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

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

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


commit 3eef9a29126effdde4b49d609865877e7718376a
Author: Bryan Rosander 
Date:   2016-12-02T19:43:22Z

NIFI-3132 - Using cygpath and quoting paths correctly in sh scripts when 
run in cygwin




---
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-3143) User Guide corrections needed for screenshots and text

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3143:
--

GitHub user andrewmlim opened a pull request:

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

NIFI-3143 User Guide corrections needed for screenshots and text




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

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

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

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


commit 495cea2c052942d1215a35a819f32ea9c03d85b3
Author: Andrew Lim 
Date:   2016-12-02T20:09:26Z

NIFI-3143 User Guide corrections needed for screenshots and text




> User Guide corrections needed for screenshots and text
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there are still some screenshots that need to be added and there 
> were also a couple screenshots that were updated unintentionally.
> Lastly, also noticed some areas to update/fix in the doc.  Most notably:  the 
> addition of the upstream/downstream connections for component context menus 
> and references to "Stats" instead of "Status History".



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

[GitHub] nifi pull request #1291: NIFI-3143 User Guide corrections needed for screens...

[andrewmlim]

GitHub user andrewmlim opened a pull request:

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

NIFI-3143 User Guide corrections needed for screenshots and text




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

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

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

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


commit 495cea2c052942d1215a35a819f32ea9c03d85b3
Author: Andrew Lim 
Date:   2016-12-02T20:09:26Z

NIFI-3143 User Guide corrections needed for screenshots and text




---
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-3143) User Guide corrections needed for screenshots and text

[Andrew Lim (JIRA)]

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

Andrew Lim commented on NIFI-3143:
--

The PR created for this will incorporate the patch of thesolson's branch for 
NIFI-3056 that wasn't merged.

> User Guide corrections needed for screenshots and text
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there are still some screenshots that need to be added and there 
> were also a couple screenshots that were updated unintentionally.
> Lastly, also noticed some areas to update/fix in the doc.  Most notably:  the 
> addition of the upstream/downstream connections for component context menus 
> and references to "Stats" instead of "Status History".



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

[jira] [Updated] (NIFI-3143) User Guide corrections needed for screenshots and text

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-3143:
-
Description: 
NIFI-3056 addressed numerous screenshots that needed to be updated or added as 
a result of NIFI-2036.

However, there are still some screenshots that need to be added and there were 
also a couple screenshots that were updated unintentionally.

Lastly, also noticed some areas to update/fix in the doc.  Most notably:  the 
addition of the upstream/downstream connections for component context menus and 
references to "Stats" instead of "Status History".

  was:
NIFI-3056 addressed numerous screenshots that needed to be updated or added as 
a result of NIFI-2036.

However, there were a couple screenshots that were updated unintentionally.


> User Guide corrections needed for screenshots and text
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there are still some screenshots that need to be added and there 
> were also a couple screenshots that were updated unintentionally.
> Lastly, also noticed some areas to update/fix in the doc.  Most notably:  the 
> addition of the upstream/downstream connections for component context menus 
> and references to "Stats" instead of "Status History".



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

[GitHub] nifi issue #1275: NIFI-2325 - Add support for LDAPS

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1275
  
I coordinated with @mcgilman this morning and he demoed LDAPS with client 
verify `demand` and LIP `REQUIRED` as working successfully (for TLS 
negotiation, not `SASL EXTERNAL` client authentication for LDAPS). I think it 
may have been a hostname resolution issue on my machine. We also verified 
`START_TLS` still works with these changes, and that ldapsearch worked 
successfully over port 636 when the ldaps protocol was explicitly indicated. 

```
root@80da99977283:/# ldapsearch -x -b dc=example,dc=org -D 
"cn=admin,dc=example,dc=org" -w admin -v -H ldaps://localhost:636
ldap_initialize( ldaps://localhost:636/??base )
filter: (objectclass=*)
requesting: All userApplication attributes
# extended LDIF
#
# LDAPv3
# base 

[jira] [Updated] (NIFI-3143) User Guide

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-3143:
-
Summary: User Guide   (was: Screenshots need to be corrected in User Guide)

> User Guide 
> ---
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there were a couple screenshots that were updated unintentionally.



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

[jira] [Updated] (NIFI-3143) User Guide corrections needed for screenshots and text

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-3143:
-
Summary: User Guide corrections needed for screenshots and text  (was: User 
Guide )

> User Guide corrections needed for screenshots and text
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there were a couple screenshots that were updated unintentionally.



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

[jira] [Commented] (NIFI-3132) nifi.sh resolves log directory incorrectly in cygwin

[Bryan Rosander (JIRA)]

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

Bryan Rosander commented on NIFI-3132:
--

The pathing is wrong for the lib directories in the toolkit scripts as well.

> nifi.sh resolves log directory incorrectly in cygwin
> 
>
> Key: NIFI-3132
> URL: https://issues.apache.org/jira/browse/NIFI-3132
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>Priority: Minor
>
> Running in cygwin results in the incorrect directory used for log directory.  
> The other relative paths appear to resolve properly.
> Please see org.apache.nifi.bootstrap.config.log.dir compared to other paths.
> This results in logs being created at:
> C:\cygdrive\c\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\logs
> instead of:
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\logs
> {code}
> bryan@bryan-win-vm /cygdrive/c/Users/bryan/Downloads/nifi-1.1.0-bin/nifi-1.1.0
> $ bin/nifi.sh run
> Java home: /cygdrive/c/Program Files/Java/jdk1.8.0_92
> NiFi home: C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0
> Bootstrap Config File: 
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\conf\bootstrap.conf
> 2016-11-30 09:57:54,528 INFO [main] org.apache.nifi.bootstrap.Command 
> Starting Apache NiFi...
> 2016-11-30 09:57:54,528 INFO [main] org.apache.nifi.bootstrap.Command Working 
> Directory: C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0
> 2016-11-30 09:57:54,528 INFO [main] org.apache.nifi.bootstrap.Command 
> Command: java -classpath 
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\conf;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\jcl-over-slf4j-1.7.12.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\jul-to-slf4j-1.7.12.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\log4j-over-slf4j-1.7.12.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\logback-classic-1.1.3.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\logback-core-1.1.3.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-api-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-documentation-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-framework-api-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-nar-utils-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-properties-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-runtime-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\slf4j-api-1.7.12.jar
>  -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m 
> -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true 
> -Djava.awt.headless=true -XX:+UseG1GC 
> -Djava.protocol.handler.pkgs=sun.net.www.protocol 
> -Dnifi.properties.file.path=C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\conf\nifi.properties
>  -Dnifi.bootstrap.listen.port=50031 -Dapp=NiFi 
> -Dorg.apache.nifi.bootstrap.config.log.dir=/cygdrive/c/Users/bryan/Downloads/nifi-1.1.0-bin/nifi-1.1.0/logs
>  org.apache.nifi.NiFi
> {code}



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

[jira] [Resolved] (NIFI-3140) FetchElasticsearchHttp no longer accepts optional type

[Joseph Percivall (JIRA)]

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

Joseph Percivall resolved NIFI-3140.

Resolution: Fixed

> FetchElasticsearchHttp no longer accepts optional type
> --
>
> Key: NIFI-3140
> URL: https://issues.apache.org/jira/browse/NIFI-3140
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> In NiFi 1.1.0, if the Type property is omitted from the 
> FetchElasticsearchHttp configuration (and a specific index is specified 
> rather than _all), the processor fails with an error "400 Bad Request".
> This is a result of FetchElasticsearchHttp URL building being aligned with 
> those used in the Query/ScrollElasticsearchHttp processors (added in 
> NIFI-2417). Unfortunately the REST API is not consistent between the Get and 
> Search APIs.
> For FetchElasticsearchHttp, the logic should be restored to insert a path 
> segment of "_all" if the Type is not provided, and the Index property 
> description should be reverted to not imply the use of "_all". Although it is 
> possible to issue a successful Get against all indexes, it cannot have a type 
> or document ID specified, and even then it does not return a document but 
> instead a listing of indexes, which is inconsistent with the purpose of the 
> processor.



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

[jira] [Commented] (NIFI-3140) FetchElasticsearchHttp no longer accepts optional type

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3140: Restored optional type handling in FetchElasticsearchHttp

This closes #1288

Signed-off-by: jpercivall 


> FetchElasticsearchHttp no longer accepts optional type
> --
>
> Key: NIFI-3140
> URL: https://issues.apache.org/jira/browse/NIFI-3140
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> In NiFi 1.1.0, if the Type property is omitted from the 
> FetchElasticsearchHttp configuration (and a specific index is specified 
> rather than _all), the processor fails with an error "400 Bad Request".
> This is a result of FetchElasticsearchHttp URL building being aligned with 
> those used in the Query/ScrollElasticsearchHttp processors (added in 
> NIFI-2417). Unfortunately the REST API is not consistent between the Get and 
> Search APIs.
> For FetchElasticsearchHttp, the logic should be restored to insert a path 
> segment of "_all" if the Type is not provided, and the Index property 
> description should be reverted to not imply the use of "_all". Although it is 
> possible to issue a successful Get against all indexes, it cannot have a type 
> or document ID specified, and even then it does not return a document but 
> instead a listing of indexes, which is inconsistent with the purpose of the 
> processor.



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

[jira] [Commented] (NIFI-3140) FetchElasticsearchHttp no longer accepts optional type

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3140:
--

Github user asfgit closed the pull request at:

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


> FetchElasticsearchHttp no longer accepts optional type
> --
>
> Key: NIFI-3140
> URL: https://issues.apache.org/jira/browse/NIFI-3140
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> In NiFi 1.1.0, if the Type property is omitted from the 
> FetchElasticsearchHttp configuration (and a specific index is specified 
> rather than _all), the processor fails with an error "400 Bad Request".
> This is a result of FetchElasticsearchHttp URL building being aligned with 
> those used in the Query/ScrollElasticsearchHttp processors (added in 
> NIFI-2417). Unfortunately the REST API is not consistent between the Get and 
> Search APIs.
> For FetchElasticsearchHttp, the logic should be restored to insert a path 
> segment of "_all" if the Type is not provided, and the Index property 
> description should be reverted to not imply the use of "_all". Although it is 
> possible to issue a successful Get against all indexes, it cannot have a type 
> or document ID specified, and even then it does not return a document but 
> instead a listing of indexes, which is inconsistent with the purpose of the 
> processor.



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

[GitHub] nifi pull request #1288: NIFI-3140: Restored optional type handling in Fetch...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3140) FetchElasticsearchHttp no longer accepts optional type

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3140:
--

Github user JPercivall commented on the issue:

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

Visually verified code and did a contrib-check build. In a standalone 
instance I ran FetchElasticsearchHTTP with and without a "type" hitting a 
secure 2.3 ES instance. Also used EL for the URL to verify NIFI-3095. 
Everything worked as expected. Thanks @mattyb149 I will merge it in.


> FetchElasticsearchHttp no longer accepts optional type
> --
>
> Key: NIFI-3140
> URL: https://issues.apache.org/jira/browse/NIFI-3140
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> In NiFi 1.1.0, if the Type property is omitted from the 
> FetchElasticsearchHttp configuration (and a specific index is specified 
> rather than _all), the processor fails with an error "400 Bad Request".
> This is a result of FetchElasticsearchHttp URL building being aligned with 
> those used in the Query/ScrollElasticsearchHttp processors (added in 
> NIFI-2417). Unfortunately the REST API is not consistent between the Get and 
> Search APIs.
> For FetchElasticsearchHttp, the logic should be restored to insert a path 
> segment of "_all" if the Type is not provided, and the Index property 
> description should be reverted to not imply the use of "_all". Although it is 
> possible to issue a successful Get against all indexes, it cannot have a type 
> or document ID specified, and even then it does not return a document but 
> instead a listing of indexes, which is inconsistent with the purpose of the 
> processor.



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

[GitHub] nifi issue #1288: NIFI-3140: Restored optional type handling in FetchElastic...

[JPercivall]

Github user JPercivall commented on the issue:

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

Visually verified code and did a contrib-check build. In a standalone 
instance I ran FetchElasticsearchHTTP with and without a "type" hitting a 
secure 2.3 ES instance. Also used EL for the URL to verify NIFI-3095. 
Everything worked as expected. Thanks @mattyb149 I will merge it in.


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

[jira] [Commented] (NIFI-3026) S2S initial connection behavior enhancement

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3026:
--

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/1208
  
@ijokarumawak Thanks for the updates! All looks good to me now. I've tested 
and everything seems to work well. Reviewed code and things look good. +1 
merged to master!


> S2S initial connection behavior enhancement
> ---
>
> Key: NIFI-3026
> URL: https://issues.apache.org/jira/browse/NIFI-3026
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>
> s2s client behavior and initial connection improvement is needed.
> Current experience is this: I, as a client (e.g. minifi), connect to a nifi 
> cluster of e.g. 10 nodes. but i need to specify 1 node URL to establish this 
> connection. this node may not be available 100% and go down, in which case my 
> initial connection won't work.
> Once S2S makes the first connection, it then has a list of all nodes, and can 
> check their status. But first connection failure would be a concern if the 
> specified URL is somehow not working. Usually for these problems, the client 
> should be able to specify multiple urls (according to multiple target cluster 
> nodes), comma-separated.



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

[GitHub] nifi issue #1208: NIFI-3026: Support multiple remote target URLs

[markap14]

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/1208
  
@ijokarumawak Thanks for the updates! All looks good to me now. I've tested 
and everything seems to work well. Reviewed code and things look good. +1 
merged to master!


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

[jira] [Commented] (NIFI-3026) S2S initial connection behavior enhancement

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3026: Support multiple remote target URLs

- Added urls in addition to the existing url, to support multiple target
  URLs
- Backward compatibility is provided by returning the first url if
  multipe urls are specified, but component accessing the url doesn't
support multiple urls
- UI is not fully updated yet. Following UI components are planned to be updated
  by different commits
  - Search component: only the first URL is searchable and shown
  - Component status: RPG status shows only the first URL
  - Component action history: only the first URL is searchable and shown
  - Updated Search component to use URLs.

This closes #1208.


> S2S initial connection behavior enhancement
> ---
>
> Key: NIFI-3026
> URL: https://issues.apache.org/jira/browse/NIFI-3026
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>
> s2s client behavior and initial connection improvement is needed.
> Current experience is this: I, as a client (e.g. minifi), connect to a nifi 
> cluster of e.g. 10 nodes. but i need to specify 1 node URL to establish this 
> connection. this node may not be available 100% and go down, in which case my 
> initial connection won't work.
> Once S2S makes the first connection, it then has a list of all nodes, and can 
> check their status. But first connection failure would be a concern if the 
> specified URL is somehow not working. Usually for these problems, the client 
> should be able to specify multiple urls (according to multiple target cluster 
> nodes), comma-separated.



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

[jira] [Commented] (NIFI-3026) S2S initial connection behavior enhancement

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3026:
--

Github user asfgit closed the pull request at:

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


> S2S initial connection behavior enhancement
> ---
>
> Key: NIFI-3026
> URL: https://issues.apache.org/jira/browse/NIFI-3026
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>
> s2s client behavior and initial connection improvement is needed.
> Current experience is this: I, as a client (e.g. minifi), connect to a nifi 
> cluster of e.g. 10 nodes. but i need to specify 1 node URL to establish this 
> connection. this node may not be available 100% and go down, in which case my 
> initial connection won't work.
> Once S2S makes the first connection, it then has a list of all nodes, and can 
> check their status. But first connection failure would be a concern if the 
> specified URL is somehow not working. Usually for these problems, the client 
> should be able to specify multiple urls (according to multiple target cluster 
> nodes), comma-separated.



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

[GitHub] nifi pull request #1208: NIFI-3026: Support multiple remote target URLs

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3135) Check restricted components on template instantiation

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3135:
--

Github user asfgit closed the pull request at:

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


> Check restricted components on template instantiation
> -
>
> Key: NIFI-3135
> URL: https://issues.apache.org/jira/browse/NIFI-3135
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.2.0
>
>
> When creating components we create a temporary instance to check if the 
> component is restricted. We should also be performing this check when 
> creating the components through template instantiation.



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

[jira] [Resolved] (NIFI-3135) Check restricted components on template instantiation

[Bryan Bende (JIRA)]

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

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

> Check restricted components on template instantiation
> -
>
> Key: NIFI-3135
> URL: https://issues.apache.org/jira/browse/NIFI-3135
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.2.0
>
>
> When creating components we create a temporary instance to check if the 
> component is restricted. We should also be performing this check when 
> creating the components through template instantiation.



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

[GitHub] nifi pull request #1287: NIFI-3135 - Authorizing restricted components on sn...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3135) Check restricted components on template instantiation

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3135: - Authorizing restricted components on snippet usage.
- Updating REST API docs accordingly.
- Adding some integration tests to exercise the additional restricted component 
checks.

This closes #1287.

Signed-off-by: Bryan Bende 


> Check restricted components on template instantiation
> -
>
> Key: NIFI-3135
> URL: https://issues.apache.org/jira/browse/NIFI-3135
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.2.0
>
>
> When creating components we create a temporary instance to check if the 
> component is restricted. We should also be performing this check when 
> creating the components through template instantiation.



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

[jira] [Updated] (NIFI-3141) TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 1.1.0

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky updated NIFI-3141:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 
> 1.1.0
> 
>
> Key: NIFI-3141
> URL: https://issues.apache.org/jira/browse/NIFI-3141
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Attachments: NiFi 1.0.0 TailFile status.png, NiFi 1.1.0 TailFile 
> status.png
>
>
> TailFile with NiFi 1.0.0 or earlier only handles single file. So it doesn't 
> have index in state key name. But the updated TailFile expects stored state 
> key has index in it, tried to extract the index and failed.
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
> at 
> org.apache.nifi.processors.standard.TailFile.initStates(TailFile.java:365) 
> ~[na:na]
> at 
> org.apache.nifi.processors.standard.TailFile.recoverState(TailFile.java:348) 
> ~[na:na]
> ... 16 common frames omitted
> {code}



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

[jira] [Updated] (NIFI-3141) TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 1.1.0

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky updated NIFI-3141:
---
Fix Version/s: 1.2.0

> TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 
> 1.1.0
> 
>
> Key: NIFI-3141
> URL: https://issues.apache.org/jira/browse/NIFI-3141
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Fix For: 1.2.0
>
> Attachments: NiFi 1.0.0 TailFile status.png, NiFi 1.1.0 TailFile 
> status.png
>
>
> TailFile with NiFi 1.0.0 or earlier only handles single file. So it doesn't 
> have index in state key name. But the updated TailFile expects stored state 
> key has index in it, tried to extract the index and failed.
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
> at 
> org.apache.nifi.processors.standard.TailFile.initStates(TailFile.java:365) 
> ~[na:na]
> at 
> org.apache.nifi.processors.standard.TailFile.recoverState(TailFile.java:348) 
> ~[na:na]
> ... 16 common frames omitted
> {code}



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

[jira] [Updated] (NIFI-3095) PutElasticSearch (2.x Bulk API) - Add expression language support to 'Elasticsearch Hosts' and 'Cluster Name' fields

[Joseph Percivall (JIRA)]

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

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

> PutElasticSearch (2.x Bulk API) - Add expression language support to 
> 'Elasticsearch Hosts' and 'Cluster Name' fields
> 
>
> Key: NIFI-3095
> URL: https://issues.apache.org/jira/browse/NIFI-3095
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Randy Bovay
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> Being able to a) Use Expression Language in the Hoss field, and ClusterName 
> fields.  
> This way we can provide a variable input to the service, and have it differ 
> in our different data centers and environments.



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

[jira] [Commented] (NIFI-3095) PutElasticSearch (2.x Bulk API) - Add expression language support to 'Elasticsearch Hosts' and 'Cluster Name' fields

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3095: Add EL support to Elasticsearch 2.x (and HTTP) processors

This closes #1276

Signed-off-by: jpercivall 


> PutElasticSearch (2.x Bulk API) - Add expression language support to 
> 'Elasticsearch Hosts' and 'Cluster Name' fields
> 
>
> Key: NIFI-3095
> URL: https://issues.apache.org/jira/browse/NIFI-3095
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Randy Bovay
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> Being able to a) Use Expression Language in the Hoss field, and ClusterName 
> fields.  
> This way we can provide a variable input to the service, and have it differ 
> in our different data centers and environments.



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

[jira] [Commented] (NIFI-3095) PutElasticSearch (2.x Bulk API) - Add expression language support to 'Elasticsearch Hosts' and 'Cluster Name' fields

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3095:
--

Github user asfgit closed the pull request at:

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


> PutElasticSearch (2.x Bulk API) - Add expression language support to 
> 'Elasticsearch Hosts' and 'Cluster Name' fields
> 
>
> Key: NIFI-3095
> URL: https://issues.apache.org/jira/browse/NIFI-3095
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Randy Bovay
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> Being able to a) Use Expression Language in the Hoss field, and ClusterName 
> fields.  
> This way we can provide a variable input to the service, and have it differ 
> in our different data centers and environments.



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

[GitHub] nifi pull request #1276: NIFI-3095: Add EL support to Elasticsearch 2.x (and...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3095) PutElasticSearch (2.x Bulk API) - Add expression language support to 'Elasticsearch Hosts' and 'Cluster Name' fields

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3095:
--

Github user JPercivall commented on the issue:

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

Visually verified code and did a contrib check build. In a standalone 
instance tested each processor with EL hitting secured and unsecured versions 
of ES 2.X. All of them (except for Fetch due to NIFI-3140) worked as expected. 
Thank you @mattyb149 I will squash and merge.


> PutElasticSearch (2.x Bulk API) - Add expression language support to 
> 'Elasticsearch Hosts' and 'Cluster Name' fields
> 
>
> Key: NIFI-3095
> URL: https://issues.apache.org/jira/browse/NIFI-3095
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Randy Bovay
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> Being able to a) Use Expression Language in the Hoss field, and ClusterName 
> fields.  
> This way we can provide a variable input to the service, and have it differ 
> in our different data centers and environments.



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

[jira] [Commented] (NIFI-3142) ExtractHL7Attributes processor does not route to REL_FAILURE for an exception other than an HL7Exception

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3142:
--

GitHub user klinvill opened a pull request:

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

Fix NIFI-3142: ExtractHL7Attribute processor: Route a flowfile to 
REL_FAILURE if processing the flow…

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?
- [ ] Have you written or updated unit tests to verify your changes?
- [n/a] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [n/a] If applicable, have you updated the LICENSE file, including the 
main LICENSE file under nifi-assembly?
- [n/a] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [n/a] If adding new Properties, have you added .displayName in addition 
to .name (programmatic access) for each of the new properties?

### For documentation related changes:
- [n/a] 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.

… file throws an exception that is not an HL7Exception for the 
ExtractHL7Attribute processor.

Fixed by changing the catch block to catch a throwable object instead of an 
HL7Exception object in the onTrigger method.

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

$ git pull https://github.com/klinvill/nifi NIFI-3142

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

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


commit 2f4a12e083be6acb8e5d2958c572e3428dc87458
Author: Kirby Linvill 
Date:   2016-12-02T14:08:03Z

Fix NIFI-3142: Route a flowfile to REL_FAILURE if processing the flow file 
throws an exception that is not an HL7Exception for the ExtractHL7Attribute 
processor.

Fixed by changing the catch block to catch a throwable object instead of an 
HL7Exception object in the onTrigger method.




> ExtractHL7Attributes processor does not route to REL_FAILURE for an exception 
> other than an HL7Exception
> 
>
> Key: NIFI-3142
> URL: https://issues.apache.org/jira/browse/NIFI-3142
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Kirby Linvill
>Priority: Minor
>  Labels: easyfix
>
> The ExtractHL7Attribute processor will not route a flowfile to REL_FAILURE if 
> processing the flow file throws an exception that is not an HL7Exception. 
> This bug is a result of the try catch block in the onTrigger method. It is 
> easily fixed by changing the catch block to catch a throwable object. Change
> {noformat} 
> try {
> ...
> } catch (final HL7Exception e) {
> getLogger().error("Failed to extract attributes from {} due to {}", new 
> Object[]{flowFile, e}, e);
> session.transfer(flowFile, REL_FAILURE);
> return;
> }
> {noformat} 
> to 
> {noformat} 
> try {
> ...
> } catch (final Throwable t) {
> getLogger().error("Failed to extract attributes from {} due to {}", new 
> Object[]{flowFile, t}, t);
> session.transfer(flowFile, REL_FAILURE);
> return;
> }
> {noformat} 



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

[GitHub] nifi pull request #1290: Fix NIFI-3142: ExtractHL7Attribute processor: Route...

[klinvill]

GitHub user klinvill opened a pull request:

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

Fix NIFI-3142: ExtractHL7Attribute processor: Route a flowfile to 
REL_FAILURE if processing the flow…

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?
- [ ] Have you written or updated unit tests to verify your changes?
- [n/a] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [n/a] If applicable, have you updated the LICENSE file, including the 
main LICENSE file under nifi-assembly?
- [n/a] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [n/a] If adding new Properties, have you added .displayName in addition 
to .name (programmatic access) for each of the new properties?

### For documentation related changes:
- [n/a] 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.

… file throws an exception that is not an HL7Exception for the 
ExtractHL7Attribute processor.

Fixed by changing the catch block to catch a throwable object instead of an 
HL7Exception object in the onTrigger method.

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

$ git pull https://github.com/klinvill/nifi NIFI-3142

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

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


commit 2f4a12e083be6acb8e5d2958c572e3428dc87458
Author: Kirby Linvill 
Date:   2016-12-02T14:08:03Z

Fix NIFI-3142: Route a flowfile to REL_FAILURE if processing the flow file 
throws an exception that is not an HL7Exception for the ExtractHL7Attribute 
processor.

Fixed by changing the catch block to catch a throwable object instead of an 
HL7Exception object in the onTrigger method.




---
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-3132) nifi.sh resolves log directory incorrectly in cygwin

[Bryan Rosander (JIRA)]

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

Bryan Rosander reassigned NIFI-3132:


Assignee: Bryan Rosander

> nifi.sh resolves log directory incorrectly in cygwin
> 
>
> Key: NIFI-3132
> URL: https://issues.apache.org/jira/browse/NIFI-3132
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>Priority: Minor
>
> Running in cygwin results in the incorrect directory used for log directory.  
> The other relative paths appear to resolve properly.
> Please see org.apache.nifi.bootstrap.config.log.dir compared to other paths.
> This results in logs being created at:
> C:\cygdrive\c\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\logs
> instead of:
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\logs
> {code}
> bryan@bryan-win-vm /cygdrive/c/Users/bryan/Downloads/nifi-1.1.0-bin/nifi-1.1.0
> $ bin/nifi.sh run
> Java home: /cygdrive/c/Program Files/Java/jdk1.8.0_92
> NiFi home: C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0
> Bootstrap Config File: 
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\conf\bootstrap.conf
> 2016-11-30 09:57:54,528 INFO [main] org.apache.nifi.bootstrap.Command 
> Starting Apache NiFi...
> 2016-11-30 09:57:54,528 INFO [main] org.apache.nifi.bootstrap.Command Working 
> Directory: C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0
> 2016-11-30 09:57:54,528 INFO [main] org.apache.nifi.bootstrap.Command 
> Command: java -classpath 
> C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\conf;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\jcl-over-slf4j-1.7.12.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\jul-to-slf4j-1.7.12.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\log4j-over-slf4j-1.7.12.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\logback-classic-1.1.3.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\logback-core-1.1.3.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-api-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-documentation-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-framework-api-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-nar-utils-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-properties-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\nifi-runtime-1.1.0.jar;C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\lib\slf4j-api-1.7.12.jar
>  -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m 
> -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true 
> -Djava.awt.headless=true -XX:+UseG1GC 
> -Djava.protocol.handler.pkgs=sun.net.www.protocol 
> -Dnifi.properties.file.path=C:\Users\bryan\Downloads\nifi-1.1.0-bin\nifi-1.1.0\.\conf\nifi.properties
>  -Dnifi.bootstrap.listen.port=50031 -Dapp=NiFi 
> -Dorg.apache.nifi.bootstrap.config.log.dir=/cygdrive/c/Users/bryan/Downloads/nifi-1.1.0-bin/nifi-1.1.0/logs
>  org.apache.nifi.NiFi
> {code}



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

[jira] [Commented] (NIFI-3143) Screenshots need to be corrected in User Guide

[Andrew Lim (JIRA)]

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

Andrew Lim commented on NIFI-3143:
--

When I created the patch off of thesolson's branch for NIFI-3056, I forgot to 
remove the screenshots that should not have been replaced.

> Screenshots need to be corrected in User Guide
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Priority: Minor
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there were a couple screenshots that were updated unintentionally.



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

[jira] [Assigned] (NIFI-3143) Screenshots need to be corrected in User Guide

[Andrew Lim (JIRA)]

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

Andrew Lim reassigned NIFI-3143:


Assignee: Andrew Lim

> Screenshots need to be corrected in User Guide
> --
>
> Key: NIFI-3143
> URL: https://issues.apache.org/jira/browse/NIFI-3143
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> NIFI-3056 addressed numerous screenshots that needed to be updated or added 
> as a result of NIFI-2036.
> However, there were a couple screenshots that were updated unintentionally.



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

[jira] [Created] (NIFI-3143) Screenshots need to be corrected in User Guide

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-3143:


 Summary: Screenshots need to be corrected in User Guide
 Key: NIFI-3143
 URL: https://issues.apache.org/jira/browse/NIFI-3143
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Documentation & Website
Reporter: Andrew Lim
Priority: Minor


NIFI-3056 addressed numerous screenshots that needed to be updated or added as 
a result of NIFI-2036.

However, there were a couple screenshots that were updated unintentionally.



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

[jira] [Commented] (NIFI-3135) Check restricted components on template instantiation

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3135:
--

Github user bbende commented on the issue:

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


> Check restricted components on template instantiation
> -
>
> Key: NIFI-3135
> URL: https://issues.apache.org/jira/browse/NIFI-3135
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.2.0
>
>
> When creating components we create a temporary instance to check if the 
> component is restricted. We should also be performing this check when 
> creating the components through template instantiation.



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

[GitHub] nifi issue #1287: NIFI-3135 - Authorizing restricted components on snippet u...

[bbende]

Github user bbende commented on the issue:

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


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

[jira] [Created] (NIFI-3142) ExtractHL7Attributes processor does not route to REL_FAILURE for an exception other than an HL7Exception

[Kirby Linvill (JIRA)]

Kirby Linvill created NIFI-3142:
---

 Summary: ExtractHL7Attributes processor does not route to 
REL_FAILURE for an exception other than an HL7Exception
 Key: NIFI-3142
 URL: https://issues.apache.org/jira/browse/NIFI-3142
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 1.0.0
Reporter: Kirby Linvill
Priority: Minor


The ExtractHL7Attribute processor will not route a flowfile to REL_FAILURE if 
processing the flow file throws an exception that is not an HL7Exception. This 
bug is a result of the try catch block in the onTrigger method. It is easily 
fixed by changing the catch block to catch a throwable object. Change
{noformat} 
try {
...
} catch (final HL7Exception e) {
getLogger().error("Failed to extract attributes from {} due to {}", new 
Object[]{flowFile, e}, e);
session.transfer(flowFile, REL_FAILURE);
return;
}
{noformat} 

to 

{noformat} 
try {
...
} catch (final Throwable t) {
getLogger().error("Failed to extract attributes from {} due to {}", new 
Object[]{flowFile, t}, t);
session.transfer(flowFile, REL_FAILURE);
return;
}
{noformat} 



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

[jira] [Commented] (NIFI-3141) TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 1.1.0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3141:
--

Github user asfgit closed the pull request at:

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


> TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 
> 1.1.0
> 
>
> Key: NIFI-3141
> URL: https://issues.apache.org/jira/browse/NIFI-3141
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Attachments: NiFi 1.0.0 TailFile status.png, NiFi 1.1.0 TailFile 
> status.png
>
>
> TailFile with NiFi 1.0.0 or earlier only handles single file. So it doesn't 
> have index in state key name. But the updated TailFile expects stored state 
> key has index in it, tried to extract the index and failed.
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
> at 
> org.apache.nifi.processors.standard.TailFile.initStates(TailFile.java:365) 
> ~[na:na]
> at 
> org.apache.nifi.processors.standard.TailFile.recoverState(TailFile.java:348) 
> ~[na:na]
> ... 16 common frames omitted
> {code}



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

[jira] [Commented] (NIFI-3141) TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 1.1.0

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3141: Fixed TailFile ArrayIndexOutOfBounds.

- Added unit test cases to simulate NiFi version update which fails without 
this fix.
- Added state object migration code, add file.0. prefix to state keys,
  and add length from stored position.

This closes #1289


> TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 
> 1.1.0
> 
>
> Key: NIFI-3141
> URL: https://issues.apache.org/jira/browse/NIFI-3141
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Attachments: NiFi 1.0.0 TailFile status.png, NiFi 1.1.0 TailFile 
> status.png
>
>
> TailFile with NiFi 1.0.0 or earlier only handles single file. So it doesn't 
> have index in state key name. But the updated TailFile expects stored state 
> key has index in it, tried to extract the index and failed.
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
> at 
> org.apache.nifi.processors.standard.TailFile.initStates(TailFile.java:365) 
> ~[na:na]
> at 
> org.apache.nifi.processors.standard.TailFile.recoverState(TailFile.java:348) 
> ~[na:na]
> ... 16 common frames omitted
> {code}



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

[GitHub] nifi pull request #1289: NIFI-3141: Fixed TailFile ArrayIndexOutOfBounds.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3141) TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 1.1.0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3141:
--

Github user olegz commented on the issue:

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


> TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 
> 1.1.0
> 
>
> Key: NIFI-3141
> URL: https://issues.apache.org/jira/browse/NIFI-3141
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Attachments: NiFi 1.0.0 TailFile status.png, NiFi 1.1.0 TailFile 
> status.png
>
>
> TailFile with NiFi 1.0.0 or earlier only handles single file. So it doesn't 
> have index in state key name. But the updated TailFile expects stored state 
> key has index in it, tried to extract the index and failed.
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
> at 
> org.apache.nifi.processors.standard.TailFile.initStates(TailFile.java:365) 
> ~[na:na]
> at 
> org.apache.nifi.processors.standard.TailFile.recoverState(TailFile.java:348) 
> ~[na:na]
> ... 16 common frames omitted
> {code}



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

[GitHub] nifi issue #1289: NIFI-3141: Fixed TailFile ArrayIndexOutOfBounds.

[olegz]

Github user olegz commented on the issue:

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


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

[jira] [Commented] (NIFI-1202) Allow user to configure Batch Size for site-to-site

[Koji Kawamura (JIRA)]

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

Koji Kawamura commented on NIFI-1202:
-

Started working on it. Modified UI to add Batch Settings. Updated screenshot is 
attached.

> Allow user to configure Batch Size for site-to-site
> ---
>
> Key: NIFI-1202
> URL: https://issues.apache.org/jira/browse/NIFI-1202
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI, Documentation & Website
>Reporter: Mark Payne
>Assignee: Mark Payne
> Attachments: WIP-added-batch-settings-ui.png, 
> configure-remote-port-window.png
>
>
> Currently, there is no way for a user to specify the batch size that 
> Site-to-Site will use. The framework decides this for you. However, if we 
> want to use the List/Fetch Pattern, it will be helpful to specify a small 
> batch size so that a small number of things that are listed are still well 
> distributed across the cluster.



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

[jira] [Updated] (NIFI-1202) Allow user to configure Batch Size for site-to-site

[Koji Kawamura (JIRA)]

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

Koji Kawamura updated NIFI-1202:

Attachment: WIP-added-batch-settings-ui.png

> Allow user to configure Batch Size for site-to-site
> ---
>
> Key: NIFI-1202
> URL: https://issues.apache.org/jira/browse/NIFI-1202
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI, Documentation & Website
>Reporter: Mark Payne
>Assignee: Mark Payne
> Attachments: WIP-added-batch-settings-ui.png, 
> configure-remote-port-window.png
>
>
> Currently, there is no way for a user to specify the batch size that 
> Site-to-Site will use. The framework decides this for you. However, if we 
> want to use the List/Fetch Pattern, it will be helpful to specify a small 
> batch size so that a small number of things that are listed are still well 
> distributed across the cluster.



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

[jira] [Commented] (NIFI-3141) TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 1.1.0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3141:
--

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/1289
  
Tested using state data created with NiFi 1.0.0:


![image](https://cloud.githubusercontent.com/assets/1107620/20827441/4d76e488-b8b5-11e6-92e9-d8f904f5c637.png)

Confirmed it works without issue, and after TailFile is triggered the old 
states are replaced with new state keys:


![image](https://cloud.githubusercontent.com/assets/1107620/20827467/73f6ac06-b8b5-11e6-9d5e-8e2b2575c177.png)


> TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 
> 1.1.0
> 
>
> Key: NIFI-3141
> URL: https://issues.apache.org/jira/browse/NIFI-3141
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Attachments: NiFi 1.0.0 TailFile status.png, NiFi 1.1.0 TailFile 
> status.png
>
>
> TailFile with NiFi 1.0.0 or earlier only handles single file. So it doesn't 
> have index in state key name. But the updated TailFile expects stored state 
> key has index in it, tried to extract the index and failed.
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
> at 
> org.apache.nifi.processors.standard.TailFile.initStates(TailFile.java:365) 
> ~[na:na]
> at 
> org.apache.nifi.processors.standard.TailFile.recoverState(TailFile.java:348) 
> ~[na:na]
> ... 16 common frames omitted
> {code}



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

[GitHub] nifi issue #1289: NIFI-3141: Fixed TailFile ArrayIndexOutOfBounds.

[ijokarumawak]

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/1289
  
Tested using state data created with NiFi 1.0.0:


![image](https://cloud.githubusercontent.com/assets/1107620/20827441/4d76e488-b8b5-11e6-92e9-d8f904f5c637.png)

Confirmed it works without issue, and after TailFile is triggered the old 
states are replaced with new state keys:


![image](https://cloud.githubusercontent.com/assets/1107620/20827467/73f6ac06-b8b5-11e6-9d5e-8e2b2575c177.png)


---
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-3141) TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 1.1.0

[Koji Kawamura (JIRA)]

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

Koji Kawamura updated NIFI-3141:

Assignee: Koji Kawamura
  Status: Patch Available  (was: Open)

> TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 
> 1.1.0
> 
>
> Key: NIFI-3141
> URL: https://issues.apache.org/jira/browse/NIFI-3141
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Attachments: NiFi 1.0.0 TailFile status.png, NiFi 1.1.0 TailFile 
> status.png
>
>
> TailFile with NiFi 1.0.0 or earlier only handles single file. So it doesn't 
> have index in state key name. But the updated TailFile expects stored state 
> key has index in it, tried to extract the index and failed.
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
> at 
> org.apache.nifi.processors.standard.TailFile.initStates(TailFile.java:365) 
> ~[na:na]
> at 
> org.apache.nifi.processors.standard.TailFile.recoverState(TailFile.java:348) 
> ~[na:na]
> ... 16 common frames omitted
> {code}



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