[jira] [Created] (NIFI-2918) JDBC getColumnName may return empty string

[Peter Wicks (JIRA)]

Peter Wicks created NIFI-2918:
-

 Summary: JDBC getColumnName may return empty string
 Key: NIFI-2918
 URL: https://issues.apache.org/jira/browse/NIFI-2918
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.1.0
Reporter: Peter Wicks
Assignee: Peter Wicks


The SAP Hana JDBC Driver returns an empty string for getColumnName if the 
column name in the SELECT statement was aliased.

Instead you have to call getColumnLabel on the ResultSetMetaData.

SAP as a company feels this is per the JDBC spec, so they are not going to 
change it.



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

[jira] [Resolved] (NIFI-1880) AsciiDoc warnings in "NiFi In-Depth" documentation

[Andy LoPresto (JIRA)]

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

Andy LoPresto resolved NIFI-1880.
-
   Resolution: Duplicate
 Assignee: Andy LoPresto
Fix Version/s: 1.0.0

A duplicate issue was filed and was resolved by commit 
cd1bccef8cb1deaa198d239804b24791207e0d39. 

> AsciiDoc warnings in "NiFi In-Depth" documentation
> --
>
> Key: NIFI-1880
> URL: https://issues.apache.org/jira/browse/NIFI-1880
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 0.6.1
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Minor
>  Labels: beginner, documentation
> Fix For: 1.0.0
>
>
> When building the project, there are asciidoc errors and warnings in 
> {{nifi-in-depth.adoc}}. 
> {code}
> [INFO] --- asciidoctor-maven-plugin:1.5.2:process-asciidoc (output-html) @ 
> nifi-docs ---
> [INFO] Rendered 
> /Users/alopresto/Workspace/nifi/nifi-docs/target/asciidoc/administration-guide.adoc
> [INFO] Rendered 
> /Users/alopresto/Workspace/nifi/nifi-docs/target/asciidoc/developer-guide.adoc
> [INFO] Rendered 
> /Users/alopresto/Workspace/nifi/nifi-docs/target/asciidoc/expression-language-guide.adoc
> [INFO] Rendered 
> /Users/alopresto/Workspace/nifi/nifi-docs/target/asciidoc/getting-started.adoc
> asciidoctor: WARNING: nifi-in-depth.adoc: line 48: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 57: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 70: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 89: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 100: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 104: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 120: section title out of 
> sequence: expected level 2, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 147: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 154: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 170: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 186: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 193: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: WARNING: nifi-in-depth.adoc: line 201: section title out of 
> sequence: expected level 3, got level 4
> asciidoctor: ERROR: nifi-in-depth.adoc: line 206: only book doctypes can 
> contain level 0 sections
> asciidoctor: ERROR: nifi-in-depth.adoc: line 206: only book doctypes can 
> contain level 0 sections
> asciidoctor: ERROR: nifi-in-depth.adoc: line 206: only book doctypes can 
> contain level 0 sections
> asciidoctor: ERROR: nifi-in-depth.adoc: line 206: only book doctypes can 
> contain level 0 sections
> [INFO] Rendered 
> /Users/alopresto/Workspace/nifi/nifi-docs/target/asciidoc/nifi-in-depth.adoc
> {code}



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

[jira] [Resolved] (NIFI-2698) HiveWriter checkstyle violation in Javadoc

[Andy LoPresto (JIRA)]

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

Andy LoPresto resolved NIFI-2698.
-
   Resolution: Cannot Reproduce
 Assignee: Andy LoPresto
Fix Version/s: 1.1.0

Went to work on this today and cannot reproduce it, either with a 
{{contrib-check}} build on the entire project or the specific module. Closing 
as {{Cannot Reproduce}}. 

{code}
hw12203:/Users/alopresto/Workspace/nifi (NIFI-2698) alopresto
 51s @ 16:56:28 $ cd nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/
hw12203:...resto/Workspace/nifi/nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors
 (NIFI-2698) alopresto
 9s @ 16:56:38 $ mck
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules...
[INFO] Installing Nexus Staging features:
[INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
nexus-staging-maven-plugin
[INFO]
[INFO] 
[INFO] Building nifi-hive-processors 1.1.0-SNAPSHOT
[INFO] 
[INFO]
[INFO] --- maven-checkstyle-plugin:2.15:check (default-cli) @ 
nifi-hive-processors ---
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 2.680 s
[INFO] Finished at: 2016-10-18T16:56:44-07:00
[INFO] Final Memory: 29M/981M
[INFO] 
hw12203:...resto/Workspace/nifi/nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors
 (NIFI-2698) alopresto
 6s @ 16:56:45 $
{code}

> HiveWriter checkstyle violation in Javadoc
> --
>
> Key: NIFI-2698
> URL: https://issues.apache.org/jira/browse/NIFI-2698
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Trivial
>  Labels: beginner, checkstyle
> Fix For: 1.1.0
>
>
> There is a checkstyle violation in {{HiveWriter.java}} -- in the Javadoc, a 
> static inner class is referenced but the class information cannot be loaded. 
> {code}
> [INFO] --- maven-checkstyle-plugin:2.15:check (default-cli) @ 
> nifi-hive-processors ---
> [WARNING] src/main/java/org/apache/nifi/util/hive/HiveWriter.java[102:20] 
> (javadoc) JavadocMethod: Unable to get class information for @throws tag 
> 'WriteFailure'.
> ...
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-checkstyle-plugin:2.15:check (default-cli) on 
> project nifi-hive-processors: You have 1 Checkstyle violation. -> [Help 1]
> {code}
> There are instructions to suppress this error type by modifying 
> {{checkstyle.xml}} [1]. 
> {code}
> 
> 
> 
> {code}
> [1] http://stackoverflow.com/a/35733030/70465



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

[jira] [Updated] (NIFI-1710) Resolve path name to nifi.sh in start script

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-1710:

Assignee: Andre

> Resolve path name to nifi.sh in start script
> 
>
> Key: NIFI-1710
> URL: https://issues.apache.org/jira/browse/NIFI-1710
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Joey Frazee
>Assignee: Andre
>Priority: Trivial
> Fix For: 1.1.0
>
>
> Currently if you symlink to nifi.sh the start script will not work because $0 
> doesn't evaluate to the physical location and the script assumes 
> bootstrap.conf is relative to the script.
> This means you can't, for example, symlink nifi.sh to /etc/init.d and use the 
> respective service commands to control NiFi.
> Adding realpath or readlink to the script should fix this.



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

[jira] [Updated] (NIFI-1710) Resolve path name to nifi.sh in start script

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-1710:

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

Fixed via PR 1137. 

> Resolve path name to nifi.sh in start script
> 
>
> Key: NIFI-1710
> URL: https://issues.apache.org/jira/browse/NIFI-1710
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Joey Frazee
>Assignee: Andre
>Priority: Trivial
> Fix For: 1.1.0
>
>
> Currently if you symlink to nifi.sh the start script will not work because $0 
> doesn't evaluate to the physical location and the script assumes 
> bootstrap.conf is relative to the script.
> This means you can't, for example, symlink nifi.sh to /etc/init.d and use the 
> respective service commands to control NiFi.
> Adding realpath or readlink to the script should fix this.



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

[jira] [Updated] (NIFI-1710) Resolve path name to nifi.sh in start script

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-1710:

Component/s: Tools and Build

> Resolve path name to nifi.sh in start script
> 
>
> Key: NIFI-1710
> URL: https://issues.apache.org/jira/browse/NIFI-1710
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Joey Frazee
>Priority: Trivial
> Fix For: 1.1.0
>
>
> Currently if you symlink to nifi.sh the start script will not work because $0 
> doesn't evaluate to the physical location and the script assumes 
> bootstrap.conf is relative to the script.
> This means you can't, for example, symlink nifi.sh to /etc/init.d and use the 
> respective service commands to control NiFi.
> Adding realpath or readlink to the script should fix this.



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

[jira] [Updated] (NIFI-1710) Resolve path name to nifi.sh in start script

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-1710:

Fix Version/s: 1.1.0

> Resolve path name to nifi.sh in start script
> 
>
> Key: NIFI-1710
> URL: https://issues.apache.org/jira/browse/NIFI-1710
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Joey Frazee
>Priority: Trivial
> Fix For: 1.1.0
>
>
> Currently if you symlink to nifi.sh the start script will not work because $0 
> doesn't evaluate to the physical location and the script assumes 
> bootstrap.conf is relative to the script.
> This means you can't, for example, symlink nifi.sh to /etc/init.d and use the 
> respective service commands to control NiFi.
> Adding realpath or readlink to the script should fix this.



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

[jira] [Commented] (NIFI-1710) Resolve path name to nifi.sh in start script

[ASF subversion and git services (JIRA)]

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

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

Commit 3914141c45c574fb8d22a72af99165cb535f5f17 in nifi's branch 
refs/heads/master from Andre F de Miranda
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=3914141 ]

NIFI-1710 - Resolve path name to nifi.sh script

This closes #1137.

Signed-off-by: Andy LoPresto 


> Resolve path name to nifi.sh in start script
> 
>
> Key: NIFI-1710
> URL: https://issues.apache.org/jira/browse/NIFI-1710
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Priority: Trivial
>
> Currently if you symlink to nifi.sh the start script will not work because $0 
> doesn't evaluate to the physical location and the script assumes 
> bootstrap.conf is relative to the script.
> This means you can't, for example, symlink nifi.sh to /etc/init.d and use the 
> respective service commands to control NiFi.
> Adding realpath or readlink to the script should fix this.



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

[GitHub] nifi pull request #1137: NIFI-1710 - Resolve path name to nifi.sh script

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-1710) Resolve path name to nifi.sh in start script

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1710:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1137
  
Built with `contrib-check`, all tests pass (Mac OS X 10.11.6, GNU bash, 
version 4.3.42(1)-release (x86_64-apple-darwin15.0.0), Java 1.8.0_101). Created 
a symlink to `bin/nifi.sh` in another directory and was able to execute the 
script. +1, merging. 

```
hw12203:/Users/alopresto/Workspace (master) alopresto
 27s @ 16:32:11 $ cd scratch/
hw12203:/Users/alopresto/Workspace/scratch (master) alopresto
 14s @ 16:32:30 $ ln -s 
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT/bin/nifi.sh
 nifi
hw12203:/Users/alopresto/Workspace/scratch (master) alopresto
 10s @ 16:33:43 $ ls -l nifi
lrwxr-xr-x  1 alopresto  staff  108 Oct 18 16:32 nifi -> 
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT/bin/nifi.sh
hw12203:/Users/alopresto/Workspace/scratch (master) alopresto
 4s @ 16:33:52 $ ./nifi status

Java home: /Users/alopresto/.jenv/versions/1.8
NiFi home: 
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT

Bootstrap Config File: 
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT/conf/bootstrap.conf

2016-10-18 16:33:58,029 INFO [main] org.apache.nifi.bootstrap.Command 
Apache NiFi is currently running, listening to Bootstrap on port 58166, 
PID=78128

hw12203:/Users/alopresto/Workspace/scratch (master) alopresto
 9s @ 16:34:01 $ ./nifi stop

Java home: /Users/alopresto/.jenv/versions/1.8
NiFi home: 
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT

Bootstrap Config File: 
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.1.0-SNAPSHOT-bin/nifi-1.1.0-SNAPSHOT/conf/bootstrap.conf

2016-10-18 16:35:43,851 INFO [main] org.apache.nifi.bootstrap.Command 
Apache NiFi has accepted the Shutdown Command and is shutting down now
2016-10-18 16:35:43,883 INFO [main] org.apache.nifi.bootstrap.Command 
Waiting for Apache NiFi to finish shutting down...
2016-10-18 16:35:45,893 INFO [main] org.apache.nifi.bootstrap.Command NiFi 
has finished shutting down.

hw12203:/Users/alopresto/Workspace/scratch (master) alopresto
 107s @ 16:35:49 $ 
```


> Resolve path name to nifi.sh in start script
> 
>
> Key: NIFI-1710
> URL: https://issues.apache.org/jira/browse/NIFI-1710
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Priority: Trivial
>
> Currently if you symlink to nifi.sh the start script will not work because $0 
> doesn't evaluate to the physical location and the script assumes 
> bootstrap.conf is relative to the script.
> This means you can't, for example, symlink nifi.sh to /etc/init.d and use the 
> respective service commands to control NiFi.
> Adding realpath or readlink to the script should fix this.



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

[jira] [Commented] (NIFI-1710) Resolve path name to nifi.sh in start script

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1710:
--

Github user alopresto commented on the issue:

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


> Resolve path name to nifi.sh in start script
> 
>
> Key: NIFI-1710
> URL: https://issues.apache.org/jira/browse/NIFI-1710
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Priority: Trivial
>
> Currently if you symlink to nifi.sh the start script will not work because $0 
> doesn't evaluate to the physical location and the script assumes 
> bootstrap.conf is relative to the script.
> This means you can't, for example, symlink nifi.sh to /etc/init.d and use the 
> respective service commands to control NiFi.
> Adding realpath or readlink to the script should fix this.



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

[jira] [Updated] (NIFI-2652) Handle multiple invocations of the encrypt-config tool

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2652:

Fix Version/s: 1.2.0

> Handle multiple invocations of the encrypt-config tool
> --
>
> Key: NIFI-2652
> URL: https://issues.apache.org/jira/browse/NIFI-2652
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: bootstrap, config, encryption, security
> Fix For: 1.2.0
>
>
> A discussion between [~jtstorck] and myself led to some possible scenarios 
> with the {{encrypt-config}} tool. If a user invokes the tool multiple times 
> on the same input files (updating in place), what should happen?
> Currently:
> The tool will not operate on any already-protected properties. So sensitive 
> properties present and unprotected would be protected by the first 
> invocation. If, before the second invocation, new sensitive values were 
> provided in the {{nifi.properties}} file, they would be protected by the 
> second invocation. If the user provides the same key/password as the first 
> invocation, all properties would be encrypted with the same key. However, if 
> a different key/password were used, the properties encrypted on the second 
> invocation would be protected with a different key, and the new key would 
> overwrite the key in the {{bootstrap.conf}} file, rendering the first set of 
> properties unrecoverable. 
> Possible solutions:
> On invocation of the tool, it first tries to read the existing key from 
> {{bootstrap.conf}}. If no key is present, operate as normal. 
> * Possibly require second entry of the key/password for confirmation to 
> ensure it was not mistyped
> If a key *is* present (one of the following):
> * (Derive if necessary and) validate the key against the existing key and if 
> it does not match, fail to run
> * Decrypt any existing encrypted properties with the persisted key and 
> re-encrypt all sensitive properties with the new key
> The second option does not require the same key/password to be used 
> repeatedly and also provides a mechanism for key migration/rollover. 
> Another possible error scenario is if the first invocation was run with the 
> JCE unlimited strength cryptographic jurisdiction policies not present (so 
> the system was limited to 128-bit encryption) and subsequent invocations are 
> run with the policies installed (in which case the tool will attempt to use 
> 256-bit encryption). The individual properties will be marked with key 
> strength available at the time they were encrypted, so this would also 
> indicate the second option above is more robust. However, if the opposite 
> flow occurs (256-bit available at first invocation, 128-bit subsequently), 
> the tool will not be able to decrypt and re-encrypt the existing protected 
> properties. 



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

[jira] [Updated] (NIFI-2655) Encrypted config tool should handle absence of "-n" flag

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2655:

Fix Version/s: 1.2.0

> Encrypted config tool should handle absence of "-n" flag
> 
>
> Key: NIFI-2655
> URL: https://issues.apache.org/jira/browse/NIFI-2655
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Minor
>  Labels: config, security
> Fix For: 1.2.0
>
>
> The {{encrypt-config}} tool will fail if the source {{-n nifi.properties}} 
> flag is not present. However, it first looks for {{./conf/nifi.properties}} 
> before failing. Either {{-n}} should be a required flag or a default 
> {{nifi.properties}} template file should be populated within the tool. 



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

[jira] [Updated] (NIFI-2656) Allow bootstrap process to prompt for password/key

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2656:

Fix Version/s: (was: 1.1.0)
   1.2.0

> Allow bootstrap process to prompt for password/key
> --
>
> Key: NIFI-2656
> URL: https://issues.apache.org/jira/browse/NIFI-2656
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Configuration, Core Framework
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Minor
>  Labels: bootstrap, config, encryption, security
> Fix For: 1.2.0
>
>
> The bootstrap process {{RunNiFi.java}} is currently responsible for reading 
> the key from {{bootstrap.conf}} and sending it to the running NiFi process 
> {{NiFi.java}} to be used for sensitive property decryption. This exposes the 
> key in two places:
> * Plaintext in {{bootstrap.conf}}
> * In the process invocation
> Running the following command ({{ps -aef | grep -i nifi}}) will result in the 
> following output:
> {code}
> ...
>   501 11597 11596   0  6:51PM ttys0010:08.55 
> /Users/alopresto/.jenv/versions/1.8/bin/java -classpath 
> /Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./conf:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/bcprov-jdk15on-1.54.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/commons-lang3-3.4.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/jcl-over-slf4j-1.7.12.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/jul-to-slf4j-1.7.12.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/log4j-over-slf4j-1.7.12.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/logback-classic-1.1.3.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/logback-core-1.1.3.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-api-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-documentation-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-framework-api-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-nar-utils-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-properties-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-properties-loader-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-runtime-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./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=/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./conf/nifi.properties
>  -Dnifi.bootstrap.listen.port=58213 -Dapp=NiFi 
> -Dorg.apache.nifi.bootstrap.config.log.dir=/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/logs
>  org.apache.nifi.NiFi -k 
> 0123456789ABCDEFFEDCBA98765432100123456789ABCDEFFEDCBA9876543210
> ...
> {code}
> To allow for a more secure invocation, the NiFi process could pause and 
> prompt for the password/key entry in a secure console if it is not provided 
> in the invocation arguments from bootstrap (or if a special flag is 
> provided). While this would require manual intervention to start the process, 
> it would not be default behavior. 



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

[jira] [Updated] (NIFI-2654) Encrypted configs should handle login identity provider configs

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2654:

Fix Version/s: 1.2.0

> Encrypted configs should handle login identity provider configs
> ---
>
> Key: NIFI-2654
> URL: https://issues.apache.org/jira/browse/NIFI-2654
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: config, encryption, ldap, security
> Fix For: 1.2.0
>
>
> The encrypted configuration tool and internal logic to load unprotected 
> values should handle sensitive values contained in the login identity 
> providers (like LDAP Manager Password).



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

[jira] [Updated] (NIFI-2653) Encrypted configs should handle variable registry

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2653:

Fix Version/s: 1.2.0

> Encrypted configs should handle variable registry
> -
>
> Key: NIFI-2653
> URL: https://issues.apache.org/jira/browse/NIFI-2653
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: config, encryption, security
> Fix For: 1.2.0
>
>
> The encrypted configuration tool and internal logic to load unprotected 
> values should handle sensitive values contained in the variable registry 
> (perhaps with a unique/derived key for external containers). 



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

[jira] [Updated] (NIFI-2913) Nifi processeror's input form & long text

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2913:

Fix Version/s: 1.1.0

> Nifi processeror's input form & long text
> -
>
> Key: NIFI-2913
> URL: https://issues.apache.org/jira/browse/NIFI-2913
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Chrome 53
> Firefox 49.0.1
>Reporter: Yari Marchetti
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 1.1.0
>
>
> Hello,
> I need to configure several processors with some very long text and, even if 
> it's very easy to create them, I'm finding the UI for reading a little 
> "unhandy". The reason is that:
> - As long as the text is only one line (even if very very long), there's no 
> problem: a scrolling bar is created but the resize handle available in all 
> major browser is visible so I can simply resize the text area to a suitable 
> dimension. Same is true horizontally (I think scroll bar kicks in after 
> something like 5 or 6)
> ​​
> - But when the text exceed the max dimension both horizontally and 
> vertically, the resize handle vanish and there's no way to resize the text 
> are anymore.
> - I'm not a CSS/JS expert but as far as I can see it's all due to this line:
> 
> which, if removed, brings back the resize handle.
> Could you please look into it?
> Thanks,
> Yari



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

[jira] [Updated] (NIFI-2905) ExecuteProcess should log error stream instead of ignoring it

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2905:

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

> ExecuteProcess should log error stream instead of ignoring it
> -
>
> Key: NIFI-2905
> URL: https://issues.apache.org/jira/browse/NIFI-2905
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Fix For: 1.1.0
>
>
> When a command executed by ExecuteProcess processor didn't work properly and 
> emitted error messages to error stream, but the processor's configured with 
> 'Redirect Error Stream' as 'false' (default), then the error messages are 
> ignored, thus there's no way for user to see what went wrong.
> It can provide better UX by logging error stream as WARN level so that user 
> can see it on bulletin.



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

[jira] [Commented] (NIFI-2905) ExecuteProcess should log error stream instead of ignoring it

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2905:
--

Github user asfgit closed the pull request at:

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


> ExecuteProcess should log error stream instead of ignoring it
> -
>
> Key: NIFI-2905
> URL: https://issues.apache.org/jira/browse/NIFI-2905
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>
> When a command executed by ExecuteProcess processor didn't work properly and 
> emitted error messages to error stream, but the processor's configured with 
> 'Redirect Error Stream' as 'false' (default), then the error messages are 
> ignored, thus there's no way for user to see what went wrong.
> It can provide better UX by logging error stream as WARN level so that user 
> can see it on bulletin.



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

[jira] [Commented] (NIFI-2905) ExecuteProcess should log error stream instead of ignoring it

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2905: Log error stream of ExecuteProcess cmd

ExecuteProcess ignores error stream when Redirect Error Stream is
false, this commit let it to be logged instead so that user can see it on
bulletin.

This closes #1143.

Signed-off-by: Andy LoPresto 


> ExecuteProcess should log error stream instead of ignoring it
> -
>
> Key: NIFI-2905
> URL: https://issues.apache.org/jira/browse/NIFI-2905
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>
> When a command executed by ExecuteProcess processor didn't work properly and 
> emitted error messages to error stream, but the processor's configured with 
> 'Redirect Error Stream' as 'false' (default), then the error messages are 
> ignored, thus there's no way for user to see what went wrong.
> It can provide better UX by logging error stream as WARN level so that user 
> can see it on bulletin.



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

[GitHub] nifi pull request #1143: NIFI-2905: Log error stream of ExecuteProcess cmd

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] nifi issue #1143: NIFI-2905: Log error stream of ExecuteProcess cmd

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1143
  
Built with `contrib-check` and verified all tests pass. I started the 
application, and used an `ExecuteProcess` processor with command `cd` and 
arguments `non-existent-dir`. With `Redirect Error Stream` set to **false** 
(default), the errors appeared as bulletins. With `Redirect Error Stream` set 
to **true**, no bulletins were raised, and the error message was found in the 
resulting flowfile contents. 

+1, merging. 


---
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-2905) ExecuteProcess should log error stream instead of ignoring it

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2905:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1143
  
Built with `contrib-check` and verified all tests pass. I started the 
application, and used an `ExecuteProcess` processor with command `cd` and 
arguments `non-existent-dir`. With `Redirect Error Stream` set to **false** 
(default), the errors appeared as bulletins. With `Redirect Error Stream` set 
to **true**, no bulletins were raised, and the error message was found in the 
resulting flowfile contents. 

+1, merging. 


> ExecuteProcess should log error stream instead of ignoring it
> -
>
> Key: NIFI-2905
> URL: https://issues.apache.org/jira/browse/NIFI-2905
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>
> When a command executed by ExecuteProcess processor didn't work properly and 
> emitted error messages to error stream, but the processor's configured with 
> 'Redirect Error Stream' as 'false' (default), then the error messages are 
> ignored, thus there's no way for user to see what went wrong.
> It can provide better UX by logging error stream as WARN level so that user 
> can see it on bulletin.



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

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

[joaohf]

Github user joaohf commented on the issue:

https://github.com/apache/nifi/pull/1047
  
Hi,

I've tested this and the output files from rpm package is the same of 
tar.gz. 


---
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-2812) Error when start nifi after installation from rpm

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2812:
--

Github user joaohf commented on the issue:

https://github.com/apache/nifi/pull/1047
  
Hi,

I've tested this and the output files from rpm package is the same of 
tar.gz. 


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



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

[jira] [Commented] (NIFI-2905) ExecuteProcess should log error stream instead of ignoring it

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2905:
--

Github user alopresto commented on the issue:

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


> ExecuteProcess should log error stream instead of ignoring it
> -
>
> Key: NIFI-2905
> URL: https://issues.apache.org/jira/browse/NIFI-2905
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>
> When a command executed by ExecuteProcess processor didn't work properly and 
> emitted error messages to error stream, but the processor's configured with 
> 'Redirect Error Stream' as 'false' (default), then the error messages are 
> ignored, thus there's no way for user to see what went wrong.
> It can provide better UX by logging error stream as WARN level so that user 
> can see it on bulletin.



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

[GitHub] nifi issue #1143: NIFI-2905: Log error stream of ExecuteProcess cmd

[alopresto]

Github user alopresto commented on the issue:

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


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

[jira] [Updated] (NIFI-2913) Nifi processeror's input form & long text

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2913:

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

> Nifi processeror's input form & long text
> -
>
> Key: NIFI-2913
> URL: https://issues.apache.org/jira/browse/NIFI-2913
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Chrome 53
> Firefox 49.0.1
>Reporter: Yari Marchetti
>Assignee: Scott Aslan
>Priority: Minor
>
> Hello,
> I need to configure several processors with some very long text and, even if 
> it's very easy to create them, I'm finding the UI for reading a little 
> "unhandy". The reason is that:
> - As long as the text is only one line (even if very very long), there's no 
> problem: a scrolling bar is created but the resize handle available in all 
> major browser is visible so I can simply resize the text area to a suitable 
> dimension. Same is true horizontally (I think scroll bar kicks in after 
> something like 5 or 6)
> ​​
> - But when the text exceed the max dimension both horizontally and 
> vertically, the resize handle vanish and there's no way to resize the text 
> are anymore.
> - I'm not a CSS/JS expert but as far as I can see it's all due to this line:
> 
> which, if removed, brings back the resize handle.
> Could you please look into it?
> Thanks,
> Yari



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

[jira] [Commented] (NIFI-2913) Nifi processeror's input form & long text

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2913:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1145
  
Ran `contrib-check`, all tests pass, verified this fixes the issue. +1, 
merging.


> Nifi processeror's input form & long text
> -
>
> Key: NIFI-2913
> URL: https://issues.apache.org/jira/browse/NIFI-2913
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Chrome 53
> Firefox 49.0.1
>Reporter: Yari Marchetti
>Assignee: Scott Aslan
>Priority: Minor
>
> Hello,
> I need to configure several processors with some very long text and, even if 
> it's very easy to create them, I'm finding the UI for reading a little 
> "unhandy". The reason is that:
> - As long as the text is only one line (even if very very long), there's no 
> problem: a scrolling bar is created but the resize handle available in all 
> major browser is visible so I can simply resize the text area to a suitable 
> dimension. Same is true horizontally (I think scroll bar kicks in after 
> something like 5 or 6)
> ​​
> - But when the text exceed the max dimension both horizontally and 
> vertically, the resize handle vanish and there's no way to resize the text 
> are anymore.
> - I'm not a CSS/JS expert but as far as I can see it's all due to this line:
> 
> which, if removed, brings back the resize handle.
> Could you please look into it?
> Thanks,
> Yari



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

[GitHub] nifi issue #1145: [NIFI-2913] update z-index of codemirror resize handle to ...

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1145
  
Ran `contrib-check`, all tests pass, verified this fixes the issue. +1, 
merging.


---
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 #1145: [NIFI-2913] update z-index of codemirror resize han...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2913) Nifi processeror's input form & long text

[ASF subversion and git services (JIRA)]

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

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

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

[NIFI-2913] update z-index of codemirror resize handle to match the z-index of 
the codemirror vert. and horz. scrollbars

This closes #1145.

Signed-off-by: Andy LoPresto 


> Nifi processeror's input form & long text
> -
>
> Key: NIFI-2913
> URL: https://issues.apache.org/jira/browse/NIFI-2913
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Chrome 53
> Firefox 49.0.1
>Reporter: Yari Marchetti
>Assignee: Scott Aslan
>Priority: Minor
>
> Hello,
> I need to configure several processors with some very long text and, even if 
> it's very easy to create them, I'm finding the UI for reading a little 
> "unhandy". The reason is that:
> - As long as the text is only one line (even if very very long), there's no 
> problem: a scrolling bar is created but the resize handle available in all 
> major browser is visible so I can simply resize the text area to a suitable 
> dimension. Same is true horizontally (I think scroll bar kicks in after 
> something like 5 or 6)
> ​​
> - But when the text exceed the max dimension both horizontally and 
> vertically, the resize handle vanish and there's no way to resize the text 
> are anymore.
> - I'm not a CSS/JS expert but as far as I can see it's all due to this line:
> 
> which, if removed, brings back the resize handle.
> Could you please look into it?
> Thanks,
> Yari



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

[jira] [Created] (NIFI-2917) Release capture of keyboard shortcuts when UI client is disconnected from server to allow Ctrl/Cmd + R for refresh

[Andy LoPresto (JIRA)]

Andy LoPresto created NIFI-2917:
---

 Summary: Release capture of keyboard shortcuts when UI client is 
disconnected from server to allow Ctrl/Cmd + R for refresh
 Key: NIFI-2917
 URL: https://issues.apache.org/jira/browse/NIFI-2917
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core UI
Affects Versions: 0.7.0, 1.0.0
Reporter: Andy LoPresto
Priority: Trivial
 Fix For: 1.1.0


When a browser window is open and the NiFi UI is loaded, and then the server is 
stopped, the UI displays a page explaining that the connection is not 
available. 

This UI page captures keyboard commands, so when the server is restarted, 
pressing Ctrl/Cmd + R does not execute the browser's refresh function. Rather, 
the refresh menu or toolbar item must be invoked using the mouse. 



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

[jira] [Commented] (NIFI-2913) Nifi processeror's input form & long text

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2913:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1145
  
@scottyaslan I built this and once I have entered text that extends past 
the boundaries to the right and the bottom, I can still use the resize handle, 
but I can only resize vertically. Is this intentional?


> Nifi processeror's input form & long text
> -
>
> Key: NIFI-2913
> URL: https://issues.apache.org/jira/browse/NIFI-2913
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Chrome 53
> Firefox 49.0.1
>Reporter: Yari Marchetti
>Assignee: Scott Aslan
>Priority: Minor
>
> Hello,
> I need to configure several processors with some very long text and, even if 
> it's very easy to create them, I'm finding the UI for reading a little 
> "unhandy". The reason is that:
> - As long as the text is only one line (even if very very long), there's no 
> problem: a scrolling bar is created but the resize handle available in all 
> major browser is visible so I can simply resize the text area to a suitable 
> dimension. Same is true horizontally (I think scroll bar kicks in after 
> something like 5 or 6)
> ​​
> - But when the text exceed the max dimension both horizontally and 
> vertically, the resize handle vanish and there's no way to resize the text 
> are anymore.
> - I'm not a CSS/JS expert but as far as I can see it's all due to this line:
> 
> which, if removed, brings back the resize handle.
> Could you please look into it?
> Thanks,
> Yari



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

[GitHub] nifi issue #1145: [NIFI-2913] update z-index of codemirror resize handle to ...

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1145
  
@scottyaslan I built this and once I have entered text that extends past 
the boundaries to the right and the bottom, I can still use the resize handle, 
but I can only resize vertically. Is this intentional?


---
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-2913) Nifi processeror's input form & long text

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2913:
--

Github user alopresto commented on the issue:

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


> Nifi processeror's input form & long text
> -
>
> Key: NIFI-2913
> URL: https://issues.apache.org/jira/browse/NIFI-2913
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Chrome 53
> Firefox 49.0.1
>Reporter: Yari Marchetti
>Assignee: Scott Aslan
>Priority: Minor
>
> Hello,
> I need to configure several processors with some very long text and, even if 
> it's very easy to create them, I'm finding the UI for reading a little 
> "unhandy". The reason is that:
> - As long as the text is only one line (even if very very long), there's no 
> problem: a scrolling bar is created but the resize handle available in all 
> major browser is visible so I can simply resize the text area to a suitable 
> dimension. Same is true horizontally (I think scroll bar kicks in after 
> something like 5 or 6)
> ​​
> - But when the text exceed the max dimension both horizontally and 
> vertically, the resize handle vanish and there's no way to resize the text 
> are anymore.
> - I'm not a CSS/JS expert but as far as I can see it's all due to this line:
> 
> which, if removed, brings back the resize handle.
> Could you please look into it?
> Thanks,
> Yari



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

[GitHub] nifi issue #1145: [NIFI-2913] update z-index of codemirror resize handle to ...

[alopresto]

Github user alopresto commented on the issue:

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


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

[jira] [Updated] (NIFI-2916) processor specific kerberos credentials for publishKafka and consumeKafka

[Pierre Villard (JIRA)]

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

Pierre Villard updated NIFI-2916:
-
 Assignee: (was: Andre)
Fix Version/s: (was: 1.1.0)

> processor specific kerberos credentials for publishKafka and consumeKafka
> -
>
> Key: NIFI-2916
> URL: https://issues.apache.org/jira/browse/NIFI-2916
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: William S Cochran
>
> Please add the capability and or documentation to configure processor 
> specific kerberos credentials for publishKafka and consumeKafka. 
> Currently the only method for Kerberos authentication appears to be via 
> java.arg options in bootstrap.conf:
> java.arg.15=-Djava.security.krb5.conf=/etc/krb5.conf
> java.arg.16=-Djava.security.auth.login.config=./conf/kafka.client.jaas.conf
> This means all nifi kafka processors currently must share the same global 
> credential.



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

[jira] [Updated] (NIFI-2916) processor specific kerberos credentials for publishKafka and consumeKafka

[William S Cochran (JIRA)]

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

William S Cochran updated NIFI-2916:

Description: 
Please add the capability and or documentation to configure processor specific 
kerberos credentials for publishKafka and consumeKafka. 

Currently the only method for Kerberos authentication appears to be via 
java.arg options in bootstrap.conf:
java.arg.15=-Djava.security.krb5.conf=/etc/krb5.conf
java.arg.16=-Djava.security.auth.login.config=./conf/kafka.client.jaas.conf

This means all nifi kafka processors currently must share the same global 
credential.


  was:
As NiFi continue to increase its abilities to complement SIEM, Splunk and ELK 
deployments, a number of users will be looking to parse CEF formatted 
logs[1][2].

CEF is a format specified by Arcsight (now part of HPE) and is described in 
detail in here:

https://www.protect724.hpe.com/docs/DOC-1072

[1] 
http://apache-nifi.1125220.n5.nabble.com/Suggestion-of-processors-td9795.html
[2] 
https://community.hortonworks.com/questions/43185/which-processor-is-used-to-parse-cef-format-logs.html


> processor specific kerberos credentials for publishKafka and consumeKafka
> -
>
> Key: NIFI-2916
> URL: https://issues.apache.org/jira/browse/NIFI-2916
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: William S Cochran
>Assignee: Andre
> Fix For: 1.1.0
>
>
> Please add the capability and or documentation to configure processor 
> specific kerberos credentials for publishKafka and consumeKafka. 
> Currently the only method for Kerberos authentication appears to be via 
> java.arg options in bootstrap.conf:
> java.arg.15=-Djava.security.krb5.conf=/etc/krb5.conf
> java.arg.16=-Djava.security.auth.login.config=./conf/kafka.client.jaas.conf
> This means all nifi kafka processors currently must share the same global 
> credential.



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

[jira] [Created] (NIFI-2916) processor specific kerberos credentials for publishKafka and consumeKafka

[William S Cochran (JIRA)]

William S Cochran created NIFI-2916:
---

 Summary: processor specific kerberos credentials for publishKafka 
and consumeKafka
 Key: NIFI-2916
 URL: https://issues.apache.org/jira/browse/NIFI-2916
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: William S Cochran
Assignee: Andre
 Fix For: 1.1.0


As NiFi continue to increase its abilities to complement SIEM, Splunk and ELK 
deployments, a number of users will be looking to parse CEF formatted 
logs[1][2].

CEF is a format specified by Arcsight (now part of HPE) and is described in 
detail in here:

https://www.protect724.hpe.com/docs/DOC-1072

[1] 
http://apache-nifi.1125220.n5.nabble.com/Suggestion-of-processors-td9795.html
[2] 
https://community.hortonworks.com/questions/43185/which-processor-is-used-to-parse-cef-format-logs.html



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

[GitHub] nifi-minifi pull request #46: MINIFI-39 Adding PeriodicStatusReporter to the...

[JPercivall]

GitHub user JPercivall opened a pull request:

https://github.com/apache/nifi-minifi/pull/46

MINIFI-39 Adding PeriodicStatusReporter to the bootstrap process with…

… an implementation to log the FlowStatus

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

$ git pull https://github.com/JPercivall/nifi-minifi MINIFI-39

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

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


commit 2e6d89e56f54ed82b75eef56f16062c35dbd70c2
Author: Joseph Percivall 
Date:   2016-10-18T20:33:25Z

MINIFI-39 Adding PeriodicStatusReporter to the bootstrap process with an 
implementation to log the FlowStatus




---
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-2915) View Details Icon in User Guide is incorrect

[Andrew Lim (JIRA)]

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

Andrew Lim reassigned NIFI-2915:


Assignee: Andrew Lim

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



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

[jira] [Created] (NIFI-2915) View Details Icon in User Guide is incorrect

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2915:


 Summary: View Details Icon in User Guide is incorrect
 Key: NIFI-2915
 URL: https://issues.apache.org/jira/browse/NIFI-2915
 Project: Apache NiFi
  Issue Type: Bug
  Components: Documentation & Website
Affects Versions: 1.0.0
Reporter: Andrew Lim
Priority: Trivial


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



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

[GitHub] nifi-minifi pull request #45: MINIFI-117 - Maintainable Configuration Versio...

[brosander]

GitHub user brosander opened a pull request:

https://github.com/apache/nifi-minifi/pull/45

MINIFI-117 - Maintainable Configuration Versioning



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

$ git pull https://github.com/brosander/nifi-minifi MINIFI-117-3

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

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


commit 1f8f6e605dce1ab5dfab10f7a267e46c7c727bfe
Author: Bryan Rosander 
Date:   2016-10-07T17:23:21Z

MINIFI-117 - Maintainable Configuration Versioning




---
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-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[Matt Burgess (JIRA)]

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

Matt Burgess updated NIFI-2828:
---
Status: Patch Available  (was: In Progress)

> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> 
>
> Key: NIFI-2828
> URL: https://issues.apache.org/jira/browse/NIFI-2828
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



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

[jira] [Comment Edited] (NIFI-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[Matt Burgess (JIRA)]

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

Matt Burgess edited comment on NIFI-2828 at 10/18/16 8:25 PM:
--

Reopening due to issue with Hadoop version included with Hive. 

The Hive NAR brings in hadoop-client, and its version is set by the 
hadoop.version property. This means that it will still get the version of 
Hadoop used by the Hadoop Libraries NAR, and can lead to incompatibilities.

Proposed change is to add a property called "hive.hadoop.version", used in the 
Hive NAR POM, defaulting to hadoop.version. This maintains the current 
behavior, but allows the Hadoop dependencies in the Hive NAR to be updated 
independently of the Hadoop version(s) elsewhere.


was (Author: mattyb149):
Reopening due to issue with Hadoop version included with Hive. 

The Hive NAR brings in hadoop-client, and its version is set by the 
hadoop.version property. This means that it will still get the version of 
Hadoop used by the Hadoop Libraries NAR, and can lead to incompatibilities.

Proposed change is to add a property called "hive.hadoop.version", used in the 
Hive NAR POM, but set in the top-level POM, defaulting to ${hadoop.version}. 
This maintains the current behavior, but allows the Hadoop dependencies in the 
Hive NAR to be updated independently of the Hadoop version(s) elsewhere.

> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> 
>
> Key: NIFI-2828
> URL: https://issues.apache.org/jira/browse/NIFI-2828
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



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

[jira] [Updated] (NIFI-2883) "Additional details" are not being displayed in the documentation for the PublishKafka_0_10 and ConsumeKafka_0_10 processors

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2883:
-
Assignee: Andrew Lim

> "Additional details" are not being displayed in the documentation for the 
> PublishKafka_0_10 and ConsumeKafka_0_10 processors
> 
>
> Key: NIFI-2883
> URL: https://issues.apache.org/jira/browse/NIFI-2883
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> Even though the additionalDetails.html files exist for these processors, that 
> information is not being displayed in the docs.  Appears to be due to the 
> directory holding the html files not matching the processor name.
> For example,
> nifi-kafka-0-10-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka
> should be:
> nifi-kafka-0-10-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10



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

[jira] [Commented] (NIFI-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2828:
--

GitHub user mattyb149 opened a pull request:

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

NIFI-2828: Fixed issue with transitive Hadoop dependencies in Hive NAR





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

$ git pull https://github.com/mattyb149/nifi NIFI-2828_2

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

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


commit 7b987df3b092280401cfc1115aa82a0b668a24cb
Author: Matt Burgess 
Date:   2016-10-18T20:22:15Z

NIFI-2828: Fixed issue with transitive Hadoop dependencies in Hive NAR




> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> 
>
> Key: NIFI-2828
> URL: https://issues.apache.org/jira/browse/NIFI-2828
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



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

[GitHub] nifi pull request #1146: NIFI-2828: Fixed issue with transitive Hadoop depen...

[mattyb149]

GitHub user mattyb149 opened a pull request:

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

NIFI-2828: Fixed issue with transitive Hadoop dependencies in Hive NAR





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

$ git pull https://github.com/mattyb149/nifi NIFI-2828_2

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

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


commit 7b987df3b092280401cfc1115aa82a0b668a24cb
Author: Matt Burgess 
Date:   2016-10-18T20:22:15Z

NIFI-2828: Fixed issue with transitive Hadoop dependencies in Hive NAR




---
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-1459) Scroll bar in the properties tab of processor Config appears behind allowable values dropdown

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1459:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1070
  
@scottyaslan This addresses the issue in the property table used throughout 
the canvas, however the same problem exists in the UpdateAttribute Custom UI. 
Would you be able to update that too?


> Scroll bar in the properties tab of processor Config appears behind allowable 
> values dropdown
> -
>
> Key: NIFI-1459
> URL: https://issues.apache.org/jira/browse/NIFI-1459
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.4.1
> Environment: OSX 10.10.15 with "Show scroll bars" option set to "When 
> scrolling" and using Google Chrome version 48.0.2564.97 (64-bit)
>Reporter: Joseph Percivall
>Assignee: Scott Aslan
>Priority: Trivial
> Attachments: Screen Shot 2016-02-02 at 11.23.46 AM.png
>
>
> In processors with many properties, one of them being a dropdown of allowable 
> values,  when the value for the property is select (bringing up the pop-up) 
> the scroll bar will overlap the box.



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

[jira] [Commented] (NIFI-2613) Support extracting content from Microsoft Excel (.xlxs) documents

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2613:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/929
  
I have a few more comments from running the processor and reviewing the 
code:

**Processor Annotations**
* The CapabilityDescription says this processor transfers one flowfile for 
each sheet in the Excel document, but that was not my experience.  It 
aggregated all content into one output flowfile.  Is that the intended behavior?
* Most NiFi attribute names are lowercase, "sheetname" or "sheet.name" 
instead of "SheetName".  I don't believe there is a hard and fast rule there, 
but I recommend going lowercase if you do not have a strong preference.

**Properties**
* PropertyDescriptors should have `name` as a machine readable key like 
"extract-sheets" and `displayName` for the user "Sheets to Extract".

**Exception Handling and Logging**
Most NiFi components use `getLogger().error(...` as you do later in the 
code, rather than `printStackTrace()`.  I haven't tested these error cases, but 
they appear to be informational rather than stopping or failing the flow.  
Would `getLogger().info(...` or `getLogger().debug(...` be a better fit here?  
Do users need the full stack trace, or would just the message be helpful enough?
```
} catch (InvalidFormatException e) {
e.printStackTrace();
} catch (OpenXML4JException e) {
e.printStackTrace();
} catch (SAXException e) {
e.printStackTrace();
}
```



> Support extracting content from Microsoft Excel (.xlxs) documents
> -
>
> Key: NIFI-2613
> URL: https://issues.apache.org/jira/browse/NIFI-2613
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Jeremy Dyer
>Assignee: Jeremy Dyer
>
> Microsoft Excel is a wildly popular application that businesses rely heavily 
> on to store, visualize, and calculate data. Any single company most likely 
> has thousands of Excel documents containing data that could be very valuable 
> if ingested via NiFi and combined with other datasources. Apache POI is a 
> popular 100% Java library for parsing several Microsoft document formats 
> including Excel. Apache POI is extremely flexible and can do several things. 
> This issue would focus solely on using Apache POI to parse an incoming .xlxs 
> document and convert it to CSV. The processor should be capable of limiting 
> which excel sheets. CSV seems like the natural choice for outputting each row 
> since this feature is already available in Excel and feels very natural to 
> most Excel sheet designs.
> This capability should most likely introduce a new "poi" module as I envision 
> many more capabilities around parsing Microsoft documents could come from 
> this base effort.



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

[GitHub] nifi issue #1070: [NIFI-1459] add css translate3d to properties table editor...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1070
  
@scottyaslan This addresses the issue in the property table used throughout 
the canvas, however the same problem exists in the UpdateAttribute Custom UI. 
Would you be able to update that too?


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

[GitHub] nifi issue #929: NIFI-2613 - Apache POI processor to convert Excel documents...

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/929
  
I have a few more comments from running the processor and reviewing the 
code:

**Processor Annotations**
* The CapabilityDescription says this processor transfers one flowfile for 
each sheet in the Excel document, but that was not my experience.  It 
aggregated all content into one output flowfile.  Is that the intended behavior?
* Most NiFi attribute names are lowercase, "sheetname" or "sheet.name" 
instead of "SheetName".  I don't believe there is a hard and fast rule there, 
but I recommend going lowercase if you do not have a strong preference.

**Properties**
* PropertyDescriptors should have `name` as a machine readable key like 
"extract-sheets" and `displayName` for the user "Sheets to Extract".

**Exception Handling and Logging**
Most NiFi components use `getLogger().error(...` as you do later in the 
code, rather than `printStackTrace()`.  I haven't tested these error cases, but 
they appear to be informational rather than stopping or failing the flow.  
Would `getLogger().info(...` or `getLogger().debug(...` be a better fit here?  
Do users need the full stack trace, or would just the message be helpful enough?
```
} catch (InvalidFormatException e) {
e.printStackTrace();
} catch (OpenXML4JException e) {
e.printStackTrace();
} catch (SAXException e) {
e.printStackTrace();
}
```



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

[GitHub] nifi-minifi pull request #44: Add the GitHub PR template to the repository

[apiri]

GitHub user apiri opened a pull request:

https://github.com/apache/nifi-minifi/pull/44

Add the GitHub PR template to the repository

Taken mostly from the efforts of NiFi and updated to be appropriate for 
MiNiFi.

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

$ git pull https://github.com/apiri/nifi-minifi add-pr-template

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

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


commit bd58210e7478a06653122844169208e76e41e73a
Author: Aldrin Piri 
Date:   2016-10-18T20:19:54Z

Add the PR template to the repository.




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

[GitHub] nifi-minifi pull request #43: MINIFI-115 Upgrade to NiFi 1.0 API

[apiri]

GitHub user apiri opened a pull request:

https://github.com/apache/nifi-minifi/pull/43

MINIFI-115 Upgrade to NiFi 1.0 API

This series of commits, left in their original form, shows the path taken 
to upgrade MiNiFi to make use of the 1.0 NiFi API.  While this is functional, 
there has been a size increase from this process.  Other issues open may depend 
upon this work, so it is provided while assembly is evaluated to reduce size.  

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

$ git pull https://github.com/apiri/nifi-minifi minifi-115

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

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


commit 19793ca58536160052c38ffc0633c23b71317ea1
Author: Aldrin Piri 
Date:   2016-10-05T20:47:14Z

MINIFI-115 Bump NiFi versions to 1.0.0

commit a2ffa018d4b8c80d35f8cf18532843d63e19a7a9
Author: Aldrin Piri 
Date:   2016-10-05T20:51:17Z

MINIFI-115 Remove provenance reporting bundle to use the NiFi equivalent.

commit 0a156f182c328e7ad304904957787a19cd858d1d
Author: Aldrin Piri 
Date:   2016-10-05T20:54:06Z

Add dependency on nifi-framework-api and change AuthorityProvider to 
Authorizer.

commit 6a2eb2d864c160f0f443a4cd2fcf0a658839debf
Author: Aldrin Piri 
Date:   2016-10-06T18:24:23Z

work in progress

commit 444582c8b1db018f48db4f7c2c49f418f602114b
Author: Aldrin Piri 
Date:   2016-10-07T19:19:26Z

removing references to provenance reporting bundle.  this should default to 
the bundle introduced in NiFi

commit 6b120f4211428cf960345f9507bf0ad6dabd6bef
Author: Aldrin Piri 
Date:   2016-10-07T19:55:33Z

Adjust provenance repository to new API.

commit 77c16459fae5209c90f30950c2170eeed7b0bbf8
Author: Aldrin Piri 
Date:   2016-10-10T13:23:16Z

Adjusting ConfigMain to use ComponentDTO.

commit 1d60f4740de82084b5ad7cd208eef4bd6588c435
Author: Aldrin Piri 
Date:   2016-10-10T14:35:44Z

Adjusting handling of remote authorization failures for RPGs and updating 
status code.

commit 9bbd40df10a45ef9e7a1c5ae5b3c37fe58f1b66b
Author: Aldrin Piri 
Date:   2016-10-10T14:38:52Z

Completed all code changes to support libraries.  Now issues at runtime 
with needed dependencies.

commit c9045b33b39c96540f602277b785443aba60ab79
Author: Aldrin Piri 
Date:   2016-10-10T14:43:06Z

Provide nifi-framework-api to provide FlowFilePrioritizer interface.

commit 8c19a7842e0b03f8849c5108433881ba5f5d84d4
Author: Aldrin Piri 
Date:   2016-10-10T16:35:17Z

Adjusting classloading and adjusting Persistent Prov repo.

commit b81507e74ae4ac662e94176cb5adbb0494ed8f1b
Author: Aldrin Piri 
Date:   2016-10-10T16:56:59Z

Include httpclient as it is needed for Site to Site.

commit 7a7f90c2d10290c9bcd7fd5351a8d6320ffbe420
Author: Aldrin Piri 
Date:   2016-10-10T18:17:07Z

Creating a configexception to allow removal of ZooKeeper dependency.

commit 86295a3f2fcf1a2db36092743a4f1d6404bfa1fc
Author: Aldrin Piri 
Date:   2016-10-12T20:03:55Z

Excluding lucene-analyzers-common.

commit c817798d8db5b62692932e828009f81e82905c58
Author: Aldrin Piri 
Date:   2016-10-17T15:38:17Z

Removing reliance on LuceneUtil.

commit 4616d0219b98c1ced4da4e9a307549afbfa8188d
Author: Aldrin Piri 
Date:   2016-10-17T16:08:11Z

Including lucene core needed for utility methods.  Removing extraneous 
logging message.

commit b7771a34f184964f42d14a8219d9517feeb23706
Author: Aldrin Piri 
Date:   2016-10-17T16:39:49Z

Adding site-to-site-reporting nar to assembly.




---
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-1459) Scroll bar in the properties tab of processor Config appears behind allowable values dropdown

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1459:
--

Github user mcgilman commented on the issue:

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


> Scroll bar in the properties tab of processor Config appears behind allowable 
> values dropdown
> -
>
> Key: NIFI-1459
> URL: https://issues.apache.org/jira/browse/NIFI-1459
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 0.4.1
> Environment: OSX 10.10.15 with "Show scroll bars" option set to "When 
> scrolling" and using Google Chrome version 48.0.2564.97 (64-bit)
>Reporter: Joseph Percivall
>Assignee: Scott Aslan
>Priority: Trivial
> Attachments: Screen Shot 2016-02-02 at 11.23.46 AM.png
>
>
> In processors with many properties, one of them being a dropdown of allowable 
> values,  when the value for the property is select (bringing up the pop-up) 
> the scroll bar will overlap the box.



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

[GitHub] nifi issue #1070: [NIFI-1459] add css translate3d to properties table editor...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1070
  
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-2613) Support extracting content from Microsoft Excel (.xlxs) documents

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2613:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/929
  
@jdye64 I still had trouble building and running NiFi with this PR.

* root POM still references nifi-poi-bundle version "1.0-SNAPSHOT"
* nifi-poi-nar still has a dependency on nifi-poi-processors version 
"1.0-SNAPSHOT"
* NiFi fails to start processing the entry for 
org.apache.nifi.processors.kite.ConvertAvroToParquet in 
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/resources/META-INF/services/org.apache.nifi.processor.Processor
 (unintentionally included in commit?)

Would you please try running `mvn clean install -Pcontrib-check`, verifying 
that the latest nifi-poi-nar is included in the lib output, and that NiFi 
starts OK?


> Support extracting content from Microsoft Excel (.xlxs) documents
> -
>
> Key: NIFI-2613
> URL: https://issues.apache.org/jira/browse/NIFI-2613
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Jeremy Dyer
>Assignee: Jeremy Dyer
>
> Microsoft Excel is a wildly popular application that businesses rely heavily 
> on to store, visualize, and calculate data. Any single company most likely 
> has thousands of Excel documents containing data that could be very valuable 
> if ingested via NiFi and combined with other datasources. Apache POI is a 
> popular 100% Java library for parsing several Microsoft document formats 
> including Excel. Apache POI is extremely flexible and can do several things. 
> This issue would focus solely on using Apache POI to parse an incoming .xlxs 
> document and convert it to CSV. The processor should be capable of limiting 
> which excel sheets. CSV seems like the natural choice for outputting each row 
> since this feature is already available in Excel and feels very natural to 
> most Excel sheet designs.
> This capability should most likely introduce a new "poi" module as I envision 
> many more capabilities around parsing Microsoft documents could come from 
> this base effort.



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

[GitHub] nifi issue #929: NIFI-2613 - Apache POI processor to convert Excel documents...

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/929
  
@jdye64 I still had trouble building and running NiFi with this PR.

* root POM still references nifi-poi-bundle version "1.0-SNAPSHOT"
* nifi-poi-nar still has a dependency on nifi-poi-processors version 
"1.0-SNAPSHOT"
* NiFi fails to start processing the entry for 
org.apache.nifi.processors.kite.ConvertAvroToParquet in 
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/resources/META-INF/services/org.apache.nifi.processor.Processor
 (unintentionally included in commit?)

Would you please try running `mvn clean install -Pcontrib-check`, verifying 
that the latest nifi-poi-nar is included in the lib output, and that NiFi 
starts OK?


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

[GitHub] nifi issue #1104: [NIFI-2844] Update CSS styles for Cluster Summary Dialog i...

[scottyaslan]

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1104
  
Please do not mergeI will address the comments in 
https://issues.apache.org/jira/browse/NIFI-2844 to match these styles with that 
of the operate palette.


---
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-2844) The icon for the component is cut-off in the Cluster Summary window.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2844:
--

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1104
  
Please do not mergeI will address the comments in 
https://issues.apache.org/jira/browse/NIFI-2844 to match these styles with that 
of the operate palette.


> The icon for the component is cut-off in the Cluster  Summary 
> window.
> 
>
> Key: NIFI-2844
> URL: https://issues.apache.org/jira/browse/NIFI-2844
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: NIFI-2844_connection.png, NIFI-2844_inputPort.png, 
> NIFI-2844_outputPort.png, NIFI-2844_processor.png, selected-component-info.png
>
>
> In a clustered environment, select "Summary" from the Global Menu.
> As an example, in the Processors tab, select "View processor details" icon 
> (the 3 cube cluster icon) for one of the processors.  The icon shown for the 
> processor is cut-off at the top.
> This also occurs for the following components:
> -Input Ports
> -Output Ports
> -Connections
> Screenshots attached.



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

[jira] [Commented] (NIFI-2685) Builds fails due to "java.awt.AWTError: Can't connect to X11 window server "

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2685:
---

reviewing 

> Builds fails due to "java.awt.AWTError: Can't connect to X11 window server "
> 
>
> Key: NIFI-2685
> URL: https://issues.apache.org/jira/browse/NIFI-2685
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Andre
>Assignee: Joseph Witt
>Priority: Trivial
> Fix For: 1.1.0, 0.8.0
>
>
> When building NiFi on a machine with ssh X11 forwarding enabled, maven may 
> fail to build due to the following error:
> {code}
> testResize(org.apache.nifi.processors.image.TestResizeImage)  Time elapsed: 
> 2.22 sec  <<< FAILURE!
> java.lang.AssertionError: java.awt.AWTError: Can't connect to X11 window 
> server using 'localhost:12.0' as the value of the DISPLAY variable.
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:192)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:151)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:146)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:141)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:136)
> at 
> org.apache.nifi.processors.image.TestResizeImage.testResize(TestResizeImage.java:44)
> {code}



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

[jira] [Assigned] (NIFI-2685) Builds fails due to "java.awt.AWTError: Can't connect to X11 window server "

[Joseph Witt (JIRA)]

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

Joseph Witt reassigned NIFI-2685:
-

Assignee: Joseph Witt  (was: Andre)

> Builds fails due to "java.awt.AWTError: Can't connect to X11 window server "
> 
>
> Key: NIFI-2685
> URL: https://issues.apache.org/jira/browse/NIFI-2685
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Andre
>Assignee: Joseph Witt
>Priority: Trivial
> Fix For: 1.1.0, 0.8.0
>
>
> When building NiFi on a machine with ssh X11 forwarding enabled, maven may 
> fail to build due to the following error:
> {code}
> testResize(org.apache.nifi.processors.image.TestResizeImage)  Time elapsed: 
> 2.22 sec  <<< FAILURE!
> java.lang.AssertionError: java.awt.AWTError: Can't connect to X11 window 
> server using 'localhost:12.0' as the value of the DISPLAY variable.
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:192)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:151)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:146)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:141)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:136)
> at 
> org.apache.nifi.processors.image.TestResizeImage.testResize(TestResizeImage.java:44)
> {code}



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

[jira] [Reopened] (NIFI-2828) SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP transport

[Matt Burgess (JIRA)]

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

Matt Burgess reopened NIFI-2828:


Reopening due to issue with Hadoop version included with Hive. 

The Hive NAR brings in hadoop-client, and its version is set by the 
hadoop.version property. This means that it will still get the version of 
Hadoop used by the Hadoop Libraries NAR, and can lead to incompatibilities.

Proposed change is to add a property called "hive.hadoop.version", used in the 
Hive NAR POM, but set in the top-level POM, defaulting to ${hadoop.version}. 
This maintains the current behavior, but allows the Hadoop dependencies in the 
Hive NAR to be updated independently of the Hadoop version(s) elsewhere.

> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> 
>
> Key: NIFI-2828
> URL: https://issues.apache.org/jira/browse/NIFI-2828
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joey Frazee
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



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

[jira] [Commented] (NIFI-2500) Allow request buffer to be configurable on HandleHTTPRequest processor

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2500:
---

+1.  Looks good.  Tested on a live flow as best i could.  was able to reproduce 
queue exhaustion and then update queue size and could not.  So while not 
definitive is a good sign.

> Allow request buffer to be configurable on HandleHTTPRequest processor
> --
>
> Key: NIFI-2500
> URL: https://issues.apache.org/jira/browse/NIFI-2500
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Matthew Clarke
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.1.0
>
>
> The request buffer for the HandleHTTPRequest buffer is hard coded to 50.  For 
> environments where bursts of requests can come in that exceed that threshold, 
> the processor will trigger Service Unavailable responses. Users should be 
> able to increase that buffer to meet their dataflow needs similar to how the 
> ConsumeMQTT processor works.



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

[jira] [Updated] (NIFI-2500) Allow request buffer to be configurable on HandleHTTPRequest processor

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2500:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Allow request buffer to be configurable on HandleHTTPRequest processor
> --
>
> Key: NIFI-2500
> URL: https://issues.apache.org/jira/browse/NIFI-2500
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Matthew Clarke
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.1.0
>
>
> The request buffer for the HandleHTTPRequest buffer is hard coded to 50.  For 
> environments where bursts of requests can come in that exceed that threshold, 
> the processor will trigger Service Unavailable responses. Users should be 
> able to increase that buffer to meet their dataflow needs similar to how the 
> ConsumeMQTT processor works.



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

[GitHub] nifi pull request #1131: NIFI-2500 made container queue configurable

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2500) Allow request buffer to be configurable on HandleHTTPRequest processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2500:
--

Github user asfgit closed the pull request at:

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


> Allow request buffer to be configurable on HandleHTTPRequest processor
> --
>
> Key: NIFI-2500
> URL: https://issues.apache.org/jira/browse/NIFI-2500
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Matthew Clarke
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.1.0
>
>
> The request buffer for the HandleHTTPRequest buffer is hard coded to 50.  For 
> environments where bursts of requests can come in that exceed that threshold, 
> the processor will trigger Service Unavailable responses. Users should be 
> able to increase that buffer to meet their dataflow needs similar to how the 
> ConsumeMQTT processor works.



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

[jira] [Commented] (NIFI-2500) Allow request buffer to be configurable on HandleHTTPRequest processor

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2500 This closes #1131. made container queue configurable


> Allow request buffer to be configurable on HandleHTTPRequest processor
> --
>
> Key: NIFI-2500
> URL: https://issues.apache.org/jira/browse/NIFI-2500
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Matthew Clarke
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.1.0
>
>
> The request buffer for the HandleHTTPRequest buffer is hard coded to 50.  For 
> environments where bursts of requests can come in that exceed that threshold, 
> the processor will trigger Service Unavailable responses. Users should be 
> able to increase that buffer to meet their dataflow needs similar to how the 
> ConsumeMQTT processor works.



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

[jira] [Updated] (NIFI-2913) Nifi processeror's input form & long text

[Scott Aslan (JIRA)]

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

Scott Aslan updated NIFI-2913:
--
Status: Patch Available  (was: In Progress)

> Nifi processeror's input form & long text
> -
>
> Key: NIFI-2913
> URL: https://issues.apache.org/jira/browse/NIFI-2913
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Chrome 53
> Firefox 49.0.1
>Reporter: Yari Marchetti
>Assignee: Scott Aslan
>Priority: Minor
>
> Hello,
> I need to configure several processors with some very long text and, even if 
> it's very easy to create them, I'm finding the UI for reading a little 
> "unhandy". The reason is that:
> - As long as the text is only one line (even if very very long), there's no 
> problem: a scrolling bar is created but the resize handle available in all 
> major browser is visible so I can simply resize the text area to a suitable 
> dimension. Same is true horizontally (I think scroll bar kicks in after 
> something like 5 or 6)
> ​​
> - But when the text exceed the max dimension both horizontally and 
> vertically, the resize handle vanish and there's no way to resize the text 
> are anymore.
> - I'm not a CSS/JS expert but as far as I can see it's all due to this line:
> 
> which, if removed, brings back the resize handle.
> Could you please look into it?
> Thanks,
> Yari



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

[jira] [Commented] (NIFI-2913) Nifi processeror's input form & long text

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2913:
--

GitHub user scottyaslan opened a pull request:

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

[NIFI-2913] update z-index of codemirror resize handle to match the z…

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

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

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

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

…-index of the codemirror vert. and horz. scrollbars

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

$ git pull https://github.com/scottyaslan/nifi NIFI-2913

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

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


commit 6b3348cddae9c0c04d23bc9e6d47cbac7e213320
Author: Scott Aslan 
Date:   2016-10-18T18:43:48Z

[NIFI-2913] update z-index of codemirror resize handle to match the z-index 
of the codemirror vert. and horz. scrollbars




> Nifi processeror's input form & long text
> -
>
> Key: NIFI-2913
> URL: https://issues.apache.org/jira/browse/NIFI-2913
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Chrome 53
> Firefox 49.0.1
>Reporter: Yari Marchetti
>Assignee: Scott Aslan
>Priority: Minor
>
> Hello,
> I need to configure several processors with some very long text and, even if 
> it's very easy to create them, I'm finding the UI for reading a little 
> "unhandy". The reason is that:
> - As long as the text is only one line (even if very very long), there's no 
> problem: a scrolling bar is created but the resize handle available in all 
> major browser is visible so I can simply resize the text area to a suitable 
> dimension. Same is true horizontally (I think scroll bar kicks in after 
> something like 5 or 6)
> ​​
> - But when the text exceed the max dimension both horizontally and 
> vertically, the resize handle vanish and there's no way to resize the text 
> are anymore.
> - I'm not a CSS/JS expert but as far as I can see it's all due to this line:
> 
> which, if removed, brings back the resize handle.
> Could you please look into it?
> Thanks,
> Yari



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

[GitHub] nifi pull request #1145: [NIFI-2913] update z-index of codemirror resize han...

[scottyaslan]

GitHub user scottyaslan opened a pull request:

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

[NIFI-2913] update z-index of codemirror resize handle to match the z…

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

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

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

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

…-index of the codemirror vert. and horz. scrollbars

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

$ git pull https://github.com/scottyaslan/nifi NIFI-2913

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

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


commit 6b3348cddae9c0c04d23bc9e6d47cbac7e213320
Author: Scott Aslan 
Date:   2016-10-18T18:43:48Z

[NIFI-2913] update z-index of codemirror resize handle to match the z-index 
of the codemirror vert. and horz. scrollbars




---
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-2913) Nifi processeror's input form & long text

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2913:
-

Assignee: Scott Aslan

> Nifi processeror's input form & long text
> -
>
> Key: NIFI-2913
> URL: https://issues.apache.org/jira/browse/NIFI-2913
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Chrome 53
> Firefox 49.0.1
>Reporter: Yari Marchetti
>Assignee: Scott Aslan
>Priority: Minor
>
> Hello,
> I need to configure several processors with some very long text and, even if 
> it's very easy to create them, I'm finding the UI for reading a little 
> "unhandy". The reason is that:
> - As long as the text is only one line (even if very very long), there's no 
> problem: a scrolling bar is created but the resize handle available in all 
> major browser is visible so I can simply resize the text area to a suitable 
> dimension. Same is true horizontally (I think scroll bar kicks in after 
> something like 5 or 6)
> ​​
> - But when the text exceed the max dimension both horizontally and 
> vertically, the resize handle vanish and there's no way to resize the text 
> are anymore.
> - I'm not a CSS/JS expert but as far as I can see it's all due to this line:
> 
> which, if removed, brings back the resize handle.
> Could you please look into it?
> Thanks,
> Yari



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

[jira] [Commented] (NIFI-2500) Allow request buffer to be configurable on HandleHTTPRequest processor

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2500:
---

reviewed code.  running some tests now

> Allow request buffer to be configurable on HandleHTTPRequest processor
> --
>
> Key: NIFI-2500
> URL: https://issues.apache.org/jira/browse/NIFI-2500
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.6.1
>Reporter: Matthew Clarke
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.1.0
>
>
> The request buffer for the HandleHTTPRequest buffer is hard coded to 50.  For 
> environments where bursts of requests can come in that exceed that threshold, 
> the processor will trigger Service Unavailable responses. Users should be 
> able to increase that buffer to meet their dataflow needs similar to how the 
> ConsumeMQTT processor works.



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

[jira] [Commented] (NIFI-2888) Display processor fill color when sufficiently zoomed out.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2888:
--

Github user mcgilman commented on the issue:

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


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



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

[GitHub] nifi issue #1133: [NIFI-2888] Display processor fill color when sufficiently...

[mcgilman]

Github user mcgilman commented on the issue:

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


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

[GitHub] nifi pull request #1126: NIFI-1769: Implemented SSE with KMS.

[jvwing]

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

https://github.com/apache/nifi/pull/1126#discussion_r83904092
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -458,6 +471,13 @@ public void process(final InputStream rawIn) throws 
IOException {
 // single part upload
 //
 final PutObjectRequest request = new 
PutObjectRequest(bucket, key, in, objectMetadata);
+if (keyId != null) {
+if 
(!context.getProperty(SIGNER_OVERRIDE).getValue().equals("AWSS3V4Signer")) {
--- End diff --

Would it be enough to check that it's not V2?  I don't think we need to 
make it impossible to get wrong, as long as we make a good faith attempt to 
help them get it right.  I'm thinking of a few things - 

1. The default should now be V4, I would prefer we not force users to nail 
down their signature version
1. AWS regions and SDK versions are complicated, for example we don't check 
if your region supports V4
1. If or when AWS comes out with signature V5, we would have to update this 
field


---
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 #1126: NIFI-1769: Implemented SSE with KMS.

[jvwing]

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

https://github.com/apache/nifi/pull/1126#discussion_r83901899
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -200,15 +201,24 @@
 .displayName("Server Side Encryption")
 .description("Specifies the algorithm used for server side 
encryption.")
 .required(true)
-.allowableValues(NO_SERVER_SIDE_ENCRYPTION, 
ObjectMetadata.AES_256_SERVER_SIDE_ENCRYPTION)
+.allowableValues(NO_SERVER_SIDE_ENCRYPTION, 
ObjectMetadata.AES_256_SERVER_SIDE_ENCRYPTION, KMS_MANAGED)
 .defaultValue(NO_SERVER_SIDE_ENCRYPTION)
 .build();
 
+public static final PropertyDescriptor AWS_KMS_KEY = new 
PropertyDescriptor.Builder()
+.name("aws-kms-key")
+.displayName("Server Side Encryption using KMS")
--- End diff --

I recommend the displayName be a bit more direct, this field is the alias 
of a KMS key, and it's going to be used for SSE.


---
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-1769) Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1769:
--

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

https://github.com/apache/nifi/pull/1126#discussion_r83904222
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -458,6 +471,13 @@ public void process(final InputStream rawIn) throws 
IOException {
 // single part upload
 //
 final PutObjectRequest request = new 
PutObjectRequest(bucket, key, in, objectMetadata);
+if (keyId != null) {
+if 
(!context.getProperty(SIGNER_OVERRIDE).getValue().equals("AWSS3V4Signer")) {
+getLogger().error("Uploading 
with AWS:KMS requires S3V4 signature, please enable it");
+return;
--- End diff --

The `return` here routes the flowfile to success without going to S3.  Is 
that intended?


> Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS
> -
>
> Key: NIFI-1769
> URL: https://issues.apache.org/jira/browse/NIFI-1769
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 0.5.1
>Reporter: Michiel Moonen
>Priority: Minor
>  Labels: newbie, patch, security
>
> Currently there is no support for SSE-KMS S3 Signature Version 4 
> Authentication. This is necessary for enhanced security features



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

[jira] [Commented] (NIFI-1769) Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1769:
--

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

https://github.com/apache/nifi/pull/1126#discussion_r83902231
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/s3/ITPutS3Object.java
 ---
@@ -50,14 +44,19 @@
 import org.junit.Ignore;
 import org.junit.Test;
 
-import com.amazonaws.AmazonClientException;
--- End diff --

Same thing again about re-sorting imports.


> Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS
> -
>
> Key: NIFI-1769
> URL: https://issues.apache.org/jira/browse/NIFI-1769
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 0.5.1
>Reporter: Michiel Moonen
>Priority: Minor
>  Labels: newbie, patch, security
>
> Currently there is no support for SSE-KMS S3 Signature Version 4 
> Authentication. This is necessary for enhanced security features



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

[jira] [Commented] (NIFI-1769) Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1769:
--

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

https://github.com/apache/nifi/pull/1126#discussion_r83901899
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -200,15 +201,24 @@
 .displayName("Server Side Encryption")
 .description("Specifies the algorithm used for server side 
encryption.")
 .required(true)
-.allowableValues(NO_SERVER_SIDE_ENCRYPTION, 
ObjectMetadata.AES_256_SERVER_SIDE_ENCRYPTION)
+.allowableValues(NO_SERVER_SIDE_ENCRYPTION, 
ObjectMetadata.AES_256_SERVER_SIDE_ENCRYPTION, KMS_MANAGED)
 .defaultValue(NO_SERVER_SIDE_ENCRYPTION)
 .build();
 
+public static final PropertyDescriptor AWS_KMS_KEY = new 
PropertyDescriptor.Builder()
+.name("aws-kms-key")
+.displayName("Server Side Encryption using KMS")
--- End diff --

I recommend the displayName be a bit more direct, this field is the alias 
of a KMS key, and it's going to be used for SSE.


> Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS
> -
>
> Key: NIFI-1769
> URL: https://issues.apache.org/jira/browse/NIFI-1769
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 0.5.1
>Reporter: Michiel Moonen
>Priority: Minor
>  Labels: newbie, patch, security
>
> Currently there is no support for SSE-KMS S3 Signature Version 4 
> Authentication. This is necessary for enhanced security features



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

[jira] [Commented] (NIFI-1769) Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1769:
--

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

https://github.com/apache/nifi/pull/1126#discussion_r83904288
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -551,6 +571,13 @@ public void process(final InputStream rawIn) throws 
IOException {
 if (currentState.getUploadId().isEmpty()) {
 final InitiateMultipartUploadRequest 
initiateRequest =
 new 
InitiateMultipartUploadRequest(bucket, key, objectMetadata);
+if (keyId != null) {
+if 
(!context.getProperty(SIGNER_OVERRIDE).getValue().equals("AWSS3V4Signer")) {
+getLogger().error("Uploading 
with AWS:KMS requires S3V4 signature, please enable it");
+return;
--- End diff --

Same issue with return routing the flowfile to success.


> Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS
> -
>
> Key: NIFI-1769
> URL: https://issues.apache.org/jira/browse/NIFI-1769
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 0.5.1
>Reporter: Michiel Moonen
>Priority: Minor
>  Labels: newbie, patch, security
>
> Currently there is no support for SSE-KMS S3 Signature Version 4 
> Authentication. This is necessary for enhanced security features



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

[jira] [Commented] (NIFI-1769) Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1769:
--

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

https://github.com/apache/nifi/pull/1126#discussion_r83901386
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -39,47 +80,6 @@
 import java.util.concurrent.locks.Lock;
 import java.util.concurrent.locks.ReentrantLock;
 
-import com.amazonaws.services.s3.model.AmazonS3Exception;
--- End diff --

Would you please only commit changes to the imports, and not re-sort them?  
I assume your IDE is doing this to "help" you, but it makes the diffs harder to 
understand.


> Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS
> -
>
> Key: NIFI-1769
> URL: https://issues.apache.org/jira/browse/NIFI-1769
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 0.5.1
>Reporter: Michiel Moonen
>Priority: Minor
>  Labels: newbie, patch, security
>
> Currently there is no support for SSE-KMS S3 Signature Version 4 
> Authentication. This is necessary for enhanced security features



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

[jira] [Commented] (NIFI-1769) Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1769:
--

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

https://github.com/apache/nifi/pull/1126#discussion_r83904092
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -458,6 +471,13 @@ public void process(final InputStream rawIn) throws 
IOException {
 // single part upload
 //
 final PutObjectRequest request = new 
PutObjectRequest(bucket, key, in, objectMetadata);
+if (keyId != null) {
+if 
(!context.getProperty(SIGNER_OVERRIDE).getValue().equals("AWSS3V4Signer")) {
--- End diff --

Would it be enough to check that it's not V2?  I don't think we need to 
make it impossible to get wrong, as long as we make a good faith attempt to 
help them get it right.  I'm thinking of a few things - 

1. The default should now be V4, I would prefer we not force users to nail 
down their signature version
1. AWS regions and SDK versions are complicated, for example we don't check 
if your region supports V4
1. If or when AWS comes out with signature V5, we would have to update this 
field


> Add support for SSE-KMS and S3 Signature Version 4 Authentication AWS
> -
>
> Key: NIFI-1769
> URL: https://issues.apache.org/jira/browse/NIFI-1769
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 0.5.1
>Reporter: Michiel Moonen
>Priority: Minor
>  Labels: newbie, patch, security
>
> Currently there is no support for SSE-KMS S3 Signature Version 4 
> Authentication. This is necessary for enhanced security features



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

[GitHub] nifi pull request #1126: NIFI-1769: Implemented SSE with KMS.

[jvwing]

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

https://github.com/apache/nifi/pull/1126#discussion_r83901386
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -39,47 +80,6 @@
 import java.util.concurrent.locks.Lock;
 import java.util.concurrent.locks.ReentrantLock;
 
-import com.amazonaws.services.s3.model.AmazonS3Exception;
--- End diff --

Would you please only commit changes to the imports, and not re-sort them?  
I assume your IDE is doing this to "help" you, but it makes the diffs harder to 
understand.


---
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 #1126: NIFI-1769: Implemented SSE with KMS.

[jvwing]

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

https://github.com/apache/nifi/pull/1126#discussion_r83902231
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/s3/ITPutS3Object.java
 ---
@@ -50,14 +44,19 @@
 import org.junit.Ignore;
 import org.junit.Test;
 
-import com.amazonaws.AmazonClientException;
--- End diff --

Same thing again about re-sorting imports.


---
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 #1126: NIFI-1769: Implemented SSE with KMS.

[jvwing]

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

https://github.com/apache/nifi/pull/1126#discussion_r83904222
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -458,6 +471,13 @@ public void process(final InputStream rawIn) throws 
IOException {
 // single part upload
 //
 final PutObjectRequest request = new 
PutObjectRequest(bucket, key, in, objectMetadata);
+if (keyId != null) {
+if 
(!context.getProperty(SIGNER_OVERRIDE).getValue().equals("AWSS3V4Signer")) {
+getLogger().error("Uploading 
with AWS:KMS requires S3V4 signature, please enable it");
+return;
--- End diff --

The `return` here routes the flowfile to success without going to S3.  Is 
that intended?


---
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 #1126: NIFI-1769: Implemented SSE with KMS.

[jvwing]

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

https://github.com/apache/nifi/pull/1126#discussion_r83904288
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -551,6 +571,13 @@ public void process(final InputStream rawIn) throws 
IOException {
 if (currentState.getUploadId().isEmpty()) {
 final InitiateMultipartUploadRequest 
initiateRequest =
 new 
InitiateMultipartUploadRequest(bucket, key, objectMetadata);
+if (keyId != null) {
+if 
(!context.getProperty(SIGNER_OVERRIDE).getValue().equals("AWSS3V4Signer")) {
+getLogger().error("Uploading 
with AWS:KMS requires S3V4 signature, please enable it");
+return;
--- End diff --

Same issue with return routing the flowfile to success.


---
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-2914) Wrong name in ERROR message

[Brandon DeVries (JIRA)]

Brandon DeVries created NIFI-2914:
-

 Summary: Wrong name in ERROR message
 Key: NIFI-2914
 URL: https://issues.apache.org/jira/browse/NIFI-2914
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Brandon DeVries
Priority: Trivial


AbstractMongoProcessor has an ERROR message "Failed to schedule PutMongo due to 
{}"\[1].  Change to not reference PutMongo...


\[1] 
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-mongodb-bundle/nifi-mongodb-processors/src/main/java/org/apache/nifi/processors/mongodb/AbstractMongoProcessor.java#L134



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

[jira] [Updated] (NIFI-2809) Add processors for Google Cloud Storage Fetch/Put/Delete

[Frank Maritato (JIRA)]

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

Frank Maritato updated NIFI-2809:
-
Attachment: nifi-2809.patch

New patch file containing the changes from the code review:
* default values
* licenses
* unit tests
* use object instead of filename

Also, I added another processor: ListGCS for listing files in a bucket, 
optionally with a prefix.

> Add processors for Google Cloud Storage Fetch/Put/Delete
> 
>
> Key: NIFI-2809
> URL: https://issues.apache.org/jira/browse/NIFI-2809
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.1.0
>Reporter: Frank Maritato
> Attachments: gcp_bundle.patch, gcs_bundle.patch, nifi-2809.patch
>
>
> Creating a ticket to add nifi processors for Google Cloud Storage similar to 
> how the AWS S3 processors are done:
> * FetchGCSObject
> * PutGCSObject
> * DeleteGCSObject
> I have the code mostly written and will attach the patch file when complete.



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

[jira] [Commented] (NIFI-2888) Display processor fill color when sufficiently zoomed out.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2888:
--

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1133
  
Ok guysthis PR has been updated and is ready for review.


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



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

[GitHub] nifi issue #1133: [NIFI-2888] Display processor fill color when sufficiently...

[scottyaslan]

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1133
  
Ok guysthis PR has been updated and is ready for review.


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

[jira] [Created] (NIFI-2913) Nifi processeror's input form & long text

[Yari Marchetti (JIRA)]

Yari Marchetti created NIFI-2913:


 Summary: Nifi processeror's input form & long text
 Key: NIFI-2913
 URL: https://issues.apache.org/jira/browse/NIFI-2913
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Affects Versions: 1.0.0
 Environment: Chrome 53
Firefox 49.0.1
Reporter: Yari Marchetti
Priority: Minor


Hello,
I need to configure several processors with some very long text and, even if 
it's very easy to create them, I'm finding the UI for reading a little 
"unhandy". The reason is that:

- As long as the text is only one line (even if very very long), there's no 
problem: a scrolling bar is created but the resize handle available in all 
major browser is visible so I can simply resize the text area to a suitable 
dimension. Same is true horizontally (I think scroll bar kicks in after 
something like 5 or 6)

​​
- But when the text exceed the max dimension both horizontally and vertically, 
the resize handle vanish and there's no way to resize the text are anymore.

- I'm not a CSS/JS expert but as far as I can see it's all due to this line:



which, if removed, brings back the resize handle.

Could you please look into it?

Thanks,
Yari



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

[jira] [Commented] (NIFI-1662) Improve Expression Language to Enable Working with Decimals

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1662:
--

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1018
  
I'm a big ANTLR fan :) so I tried adding decimal literals to the grammar, 
feel free to take a look and use whatever you like: 
https://github.com/mattyb149/nifi/commit/9ed3fb4f17b0ec64fbe9d861ff255750c3ec7e5a


> Improve Expression Language to Enable Working with Decimals
> ---
>
> Key: NIFI-1662
> URL: https://issues.apache.org/jira/browse/NIFI-1662
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>
> Currently the math operations in Expression Language use Longs to evaluate 
> numbers. This leads to any decimal places getting truncated when performing 
> operations like divide. 
> NiFi should support working with decimals



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

[GitHub] nifi issue #1018: NIFI-1662 adding Expression Language decimal support

[mattyb149]

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1018
  
I'm a big ANTLR fan :) so I tried adding decimal literals to the grammar, 
feel free to take a look and use whatever you like: 
https://github.com/mattyb149/nifi/commit/9ed3fb4f17b0ec64fbe9d861ff255750c3ec7e5a


---
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-2912) Processor to generate a flow file from a string

[Alessio Palma (JIRA)]

Alessio Palma created NIFI-2912:
---

 Summary: Processor to generate a flow file from a string
 Key: NIFI-2912
 URL: https://issues.apache.org/jira/browse/NIFI-2912
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Alessio Palma
Priority: Minor


Currently to build a flow file from a string we need ReplaceText and 
GenerateFlowFile with a size of 0B. 
Is here a way to have use only the GenerateFlowFile processor ? 
This will be handy when you are using templates in workflows.




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

[jira] [Commented] (NIFI-2900) DateTime API Endpoints don't respect RFC 3339

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2900:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1136
  
Hey sorry, I was traveling yesterday. I don't see your most recent changes. 
Can you double check that you've pushed them?


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



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

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

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1136
  
Hey sorry, I was traveling yesterday. I don't see your most recent changes. 
Can you double check that you've pushed them?


---
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] [Reopened] (NIFI-2898) Add Processor dialog cuts off processor descriptions

[Scott Aslan (JIRA)]

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

Scott Aslan reopened NIFI-2898:
---

> Add Processor dialog cuts off processor descriptions
> 
>
> Key: NIFI-2898
> URL: https://issues.apache.org/jira/browse/NIFI-2898
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Jeff Storck
>Assignee: Scott Aslan
>Priority: Minor
> Fix For: 1.1.0
>
>
> In the Add Processor dialog, descriptions for processors like 
> ConvertJSONToSQL get cut off instead of showing a ellipses.



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

[jira] [Commented] (NIFI-2888) Display processor fill color when sufficiently zoomed out.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2888:
--

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1133
  
I will have an update to the PR later on today @pvillard31please do not 
merge yet as this PR currently only addresses the zoomed out color of the 
processors. The plan is to have all items on the canvas match their birdseye 
view colors when sufficiently zoomed out (PG's, ports and filters).


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



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