[jira] [Commented] (NIFI-2817) git branch cleanup

[Andre (JIRA)]

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

Andre commented on NIFI-2817:
-

Following branches were deleted:
ListHDFS - e0d4484ee8e7b80fe3b47d5bb132d95019253a46
NIFI-25 - 0211d0d71561fb63df4a06cd7b1a3b430b7a3e6c
NIFI-259 - 16f185245309ac3bcf9629b1c4d4dc655f18ca68
NIFI-433 - e1e1aecc8b8e6c75f260edf248f046c1557c088b
NIFI-730 - dbf0c7893fef964bfbb3a4c039c756396587ce12
NIFI-810-InputRequirement - 0636f0e731cd28299edd3a6e9db90de5045ab662
NIFI-1085 - 6add372bc142304ef25e0bafb49709654a995f08

Branches left behind as they had commits ahead of master:

NIFI-274 - bbende
NIFI-376 - mcgilman
NIFI-631 - trkurc
NIFI-640 - mcgilman
NIFI-731 - marlap14
NIFI-744 - markap14
NIFI-919 - bbende
NIFI-1073 - trkurc
NIFI-1107 - trkurc

> git branch cleanup
> --
>
> Key: NIFI-2817
> URL: https://issues.apache.org/jira/browse/NIFI-2817
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Andre
>Assignee: Andre
>
> Document the deletion of stalled git branches



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

[jira] [Created] (NIFI-2817) git branch cleanup

[Andre (JIRA)]

Andre created NIFI-2817:
---

 Summary: git branch cleanup
 Key: NIFI-2817
 URL: https://issues.apache.org/jira/browse/NIFI-2817
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Andre
Assignee: Andre


Document the deletion of stalled git branches



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

[jira] [Commented] (NIFI-2813) Appveyor build failing because M2_HOME

[Andre (JIRA)]

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

Andre commented on NIFI-2813:
-

thanks for the contribution Edgardo. 

Now that this is merged to master, time to chase the tests that are failing to 
complete during the appveyor build

> Appveyor build failing because M2_HOME
> --
>
> Key: NIFI-2813
> URL: https://issues.apache.org/jira/browse/NIFI-2813
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.1.0
>Reporter: Edgardo Vega
>Assignee: Andre
> Fix For: 1.1.0
>
>
> Appveyor was given the following error:
> **ERROR: M2_HOME is set to an invalid directory.
> M2_HOME = "C:\Program Files (x86)\Apache\Maven"
> Please set the M2_HOME variable in your environment to match the location of 
> the Maven installation**



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

[jira] [Resolved] (NIFI-2813) Appveyor build failing because M2_HOME

[Andre (JIRA)]

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

Andre resolved NIFI-2813.
-
Resolution: Fixed
  Assignee: Andre

> Appveyor build failing because M2_HOME
> --
>
> Key: NIFI-2813
> URL: https://issues.apache.org/jira/browse/NIFI-2813
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.1.0
>Reporter: Edgardo Vega
>Assignee: Andre
> Fix For: 1.1.0
>
>
> Appveyor was given the following error:
> **ERROR: M2_HOME is set to an invalid directory.
> M2_HOME = "C:\Program Files (x86)\Apache\Maven"
> Please set the M2_HOME variable in your environment to match the location of 
> the Maven installation**



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

[jira] [Commented] (NIFI-2814) Add ASL 2.0 header to appveyor settings

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2814:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1058
  
@apiri another small clean up activity.


> Add ASL 2.0 header to appveyor settings
> ---
>
> Key: NIFI-2814
> URL: https://issues.apache.org/jira/browse/NIFI-2814
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[GitHub] nifi issue #1058: NIFI-2814 - Add ASF header to AppVeyor settings file

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1058
  
@apiri another small clean up activity.


---
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-2813) Appveyor build failing because M2_HOME

[ASF subversion and git services (JIRA)]

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

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

Commit 560a835ef9845c36377f523ec2acf6f076824450 in nifi's branch refs/heads/0.x 
from Edgardo
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=560a835 ]

[NIFI-2813] Fix for invalid M2_HOME directory

This closes #1049

Signed-off-by: Andre F de Miranda 


> Appveyor build failing because M2_HOME
> --
>
> Key: NIFI-2813
> URL: https://issues.apache.org/jira/browse/NIFI-2813
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.1.0
>Reporter: Edgardo Vega
> Fix For: 1.1.0
>
>
> Appveyor was given the following error:
> **ERROR: M2_HOME is set to an invalid directory.
> M2_HOME = "C:\Program Files (x86)\Apache\Maven"
> Please set the M2_HOME variable in your environment to match the location of 
> the Maven installation**



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

[GitHub] nifi pull request #1049: [NIFI-2813] Fix for invalid M2_HOME directory in Ap...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2813) Appveyor build failing because M2_HOME

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2813:
--

Github user asfgit closed the pull request at:

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


> Appveyor build failing because M2_HOME
> --
>
> Key: NIFI-2813
> URL: https://issues.apache.org/jira/browse/NIFI-2813
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.1.0
>Reporter: Edgardo Vega
> Fix For: 1.1.0
>
>
> Appveyor was given the following error:
> **ERROR: M2_HOME is set to an invalid directory.
> M2_HOME = "C:\Program Files (x86)\Apache\Maven"
> Please set the M2_HOME variable in your environment to match the location of 
> the Maven installation**



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

[jira] [Commented] (NIFI-2813) Appveyor build failing because M2_HOME

[ASF subversion and git services (JIRA)]

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

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

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

[NIFI-2813] Fix for invalid M2_HOME directory

This closes #1049

Signed-off-by: Andre F de Miranda 


> Appveyor build failing because M2_HOME
> --
>
> Key: NIFI-2813
> URL: https://issues.apache.org/jira/browse/NIFI-2813
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.1.0
>Reporter: Edgardo Vega
> Fix For: 1.1.0
>
>
> Appveyor was given the following error:
> **ERROR: M2_HOME is set to an invalid directory.
> M2_HOME = "C:\Program Files (x86)\Apache\Maven"
> Please set the M2_HOME variable in your environment to match the location of 
> the Maven installation**



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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1057
  
@pvillard31 note to myself: Never try to hunt typos after midnight ... 
:smiley: 


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[GitHub] nifi issue #1057: NIFI-2816 - Clean typos across the code

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1057
  
@pvillard31 note to myself: Never try to hunt typos after midnight ... 
:smiley: 


---
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-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

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

https://github.com/apache/nifi/pull/1057#discussion_r80344580
  
--- Diff: 
nifi-nar-bundles/nifi-evtx-bundle/nifi-evtx-processors/src/main/java/org/apache/nifi/processors/evtx/parser/BinaryReader.java
 ---
@@ -86,9 +86,9 @@ public int read() {
 }
 
 /**
- * Returns the byte that would be read without changing the posiiton
+ * Returns the byte that would be read without changing the positon
  *
- * @return the byte that would be read without changing the posiiton
+ * @return the byte that would be read without changing the positon
--- End diff --

addressed


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

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

https://github.com/apache/nifi/pull/1057#discussion_r80344591
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-client-dto/src/main/java/org/apache/nifi/web/api/dto/ControllerConfigurationDTO.java
 ---
@@ -47,7 +47,7 @@ public void setMaxTimerDrivenThreadCount(Integer 
maxTimerDrivenThreadCount) {
  * @return maximum number of event driven thread this NiFi has 
available
  */
 @ApiModelProperty(
-value = "The maximum number of event driven threads the NiFi 
has avaiable."
+value = "The maximum number of event driven threads the NiFi 
has avaliable."
--- End diff --

addressed 


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

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

https://github.com/apache/nifi/pull/1057#discussion_r80344540
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/crypto/bcrypt/BCrypt.java
 ---
@@ -25,7 +25,7 @@
  * This password hashing system tries to thwart off-line password
  * cracking using a computationally-intensive hashing algorithm,
  * based on Bruce Schneier's Blowfish cipher. The work factor of
- * the algorithm is parameterised, so it can be increased as
+ * the algorithm is parametrised, so it can be increased as
--- End diff --

addressed


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

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

https://github.com/apache/nifi/pull/1057#discussion_r80344575
  
--- Diff: 
nifi-nar-bundles/nifi-evtx-bundle/nifi-evtx-processors/src/main/java/org/apache/nifi/processors/evtx/parser/BinaryReader.java
 ---
@@ -86,9 +86,9 @@ public int read() {
 }
 
 /**
- * Returns the byte that would be read without changing the posiiton
+ * Returns the byte that would be read without changing the positon
--- End diff --

addressed


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[GitHub] nifi pull request #1057: NIFI-2816 - Clean typos across the code

[trixpan]

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

https://github.com/apache/nifi/pull/1057#discussion_r80344591
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-client-dto/src/main/java/org/apache/nifi/web/api/dto/ControllerConfigurationDTO.java
 ---
@@ -47,7 +47,7 @@ public void setMaxTimerDrivenThreadCount(Integer 
maxTimerDrivenThreadCount) {
  * @return maximum number of event driven thread this NiFi has 
available
  */
 @ApiModelProperty(
-value = "The maximum number of event driven threads the NiFi 
has avaiable."
+value = "The maximum number of event driven threads the NiFi 
has avaliable."
--- End diff --

addressed 


---
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 #1057: NIFI-2816 - Clean typos across the code

[trixpan]

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

https://github.com/apache/nifi/pull/1057#discussion_r80344580
  
--- Diff: 
nifi-nar-bundles/nifi-evtx-bundle/nifi-evtx-processors/src/main/java/org/apache/nifi/processors/evtx/parser/BinaryReader.java
 ---
@@ -86,9 +86,9 @@ public int read() {
 }
 
 /**
- * Returns the byte that would be read without changing the posiiton
+ * Returns the byte that would be read without changing the positon
  *
- * @return the byte that would be read without changing the posiiton
+ * @return the byte that would be read without changing the positon
--- End diff --

addressed


---
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 #1057: NIFI-2816 - Clean typos across the code

[trixpan]

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

https://github.com/apache/nifi/pull/1057#discussion_r80344575
  
--- Diff: 
nifi-nar-bundles/nifi-evtx-bundle/nifi-evtx-processors/src/main/java/org/apache/nifi/processors/evtx/parser/BinaryReader.java
 ---
@@ -86,9 +86,9 @@ public int read() {
 }
 
 /**
- * Returns the byte that would be read without changing the posiiton
+ * Returns the byte that would be read without changing the positon
--- End diff --

addressed


---
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 #1057: NIFI-2816 - Clean typos across the code

[trixpan]

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

https://github.com/apache/nifi/pull/1057#discussion_r80344540
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/crypto/bcrypt/BCrypt.java
 ---
@@ -25,7 +25,7 @@
  * This password hashing system tries to thwart off-line password
  * cracking using a computationally-intensive hashing algorithm,
  * based on Bruce Schneier's Blowfish cipher. The work factor of
- * the algorithm is parameterised, so it can be increased as
+ * the algorithm is parametrised, so it can be increased as
--- End diff --

addressed


---
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-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

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

https://github.com/apache/nifi/pull/1057#discussion_r80344174
  
--- Diff: 
nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java ---
@@ -164,7 +164,7 @@ public void commit() {
  * {@link org.apache.nifi.processor.Processor#onTrigger} commits or 
rolls back the
  * session
  */
-public void clearCommited() {
+public void clearCommitted() {
--- End diff --

Good question. To be honest, I was relying on good old travis to tell.

Seems like it passes but yes, we are renaming a public method.


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[GitHub] nifi pull request #1057: NIFI-2816 - Clean typos across the code

[trixpan]

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

https://github.com/apache/nifi/pull/1057#discussion_r80344174
  
--- Diff: 
nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java ---
@@ -164,7 +164,7 @@ public void commit() {
  * {@link org.apache.nifi.processor.Processor#onTrigger} commits or 
rolls back the
  * session
  */
-public void clearCommited() {
+public void clearCommitted() {
--- End diff --

Good question. To be honest, I was relying on good old travis to tell.

Seems like it passes but yes, we are renaming a public method.


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

[GitHub] nifi issue #239: Nifi 1540 - AWS Kinesis Get and Put Processors

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/239
  
@mans2singh, I agree the licensing issues prevent it from being bundled 
with NiFi as-is.  But there might be a few options to move forward and keep the 
benefits of your work:

* Publish the processors you've already developed as a standalone NAR 
project
* Rework the processors to use the Kinesis client in the standard AWS SDK

Any other ideas?


---
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 #952: Nifi 2673: Add MERGE support on processor ConvertJSONTOSQL

[paulgibeault]

Github user paulgibeault commented on the issue:

https://github.com/apache/nifi/pull/952
  
Is there a chance of getting this pull request included in the 1.1.0 
release of NiFi?


---
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 #721: Nifi 2398 - Apache Ignite Get Processor

[mans2singh]

Github user mans2singh commented on the issue:

https://github.com/apache/nifi/pull/721
  
Hi @pvillard31 - Can you please point me to which attribute you are 
referring to since the constant (IGNITE_GET_FAILED_MISSING_KEY_MESSAGE) is a 
message not a key.
I will correct the 2nd issue that you mentioned.
Thanks 


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

[GitHub] nifi issue #239: Nifi 1540 - AWS Kinesis Get and Put Processors

[mans2singh]

Github user mans2singh commented on the issue:

https://github.com/apache/nifi/pull/239
  
@jvwing - 
I was under the impression that it could be bundled with Nifi due to AWS 
libraries licence issues.  Please let me know how Kinesis processors can be 
part of Nifi.
Thanks


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

[GitHub] nifi-minifi pull request #39: MINIFI-81 Adding a check for a valid command t...

[apiri]

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

https://github.com/apache/nifi-minifi/pull/39#discussion_r80333632
  
--- Diff: 
minifi-toolkit/minifi-toolkit-configuration/src/main/java/org/apache/nifi/minifi/toolkit/configuration/ConfigMain.java
 ---
@@ -85,8 +85,6 @@ public static void main(String[] args) {
 public static void printValidateUsage() {
 System.out.println("Validate Usage:");
 System.out.println();
-System.out.print("java ");
--- End diff --

Should this and the other java invocation remain given that the 
interpretation of arguments is handled by the script when invoked from the 
script?  This is valid in the context the class is run by itself.


---
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-2795) Enhance Cluster UI with System Diagnostics

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2795:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1042
  
I added server- and client-side modifications to pre-authorize the system 
diagnostics API call, and removed the unnecessary error handling code.


> Enhance Cluster UI with System Diagnostics
> --
>
> Key: NIFI-2795
> URL: https://issues.apache.org/jira/browse/NIFI-2795
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Attachments: cluster-01-nodes.png, cluster-02-system.png, 
> cluster-03-jvm.png, cluster-04-flowfile-store.png, 
> cluster-05-content-store.png
>
>
> The Cluster UI currently provides some basic information on each node in the 
> cluster and options for connecting and disconnecting nodes. I propose to add 
> system diagnostics information in tables, contained in multiple tabs.  
> Roughly, the tabs should cover the same content as the System Diagnostics 
> dialog already in the System UI, but in a tabular format for comparing across 
> nodes.



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

[GitHub] nifi issue #1042: NIFI-2795 Sys Diagnostics in Cluster UI

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1042
  
I added server- and client-side modifications to pre-authorize the system 
diagnostics API call, and removed the unnecessary error handling code.


---
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-2288) Authorization: Start and Stop buttons in Operate pallette are active for a user that only has view privileges to process group

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2288:
-

Assignee: Scott Aslan

> Authorization:  Start and Stop buttons in Operate pallette are active for a 
> user that only has view privileges to process group
> ---
>
> Key: NIFI-2288
> URL: https://issues.apache.org/jira/browse/NIFI-2288
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
>  Labels: UI
>
> A non-administrator user only has view privileges to a process group, however 
> the Start and Stop buttons in the Operate pallete are active and clickable, 
> when they should be inactive.
> Clicking the Start and Stop buttons doesn't do anything, which is why I 
> marked as Minor priority, but this is still confusing to the user.



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

[jira] [Commented] (NIFI-2787) PersistentProvenanceRepository rollover can fail on immense indexed attributes

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2787:
--

Github user asfgit closed the pull request at:

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


> PersistentProvenanceRepository rollover can fail on immense indexed attributes
> --
>
> Key: NIFI-2787
> URL: https://issues.apache.org/jira/browse/NIFI-2787
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
> Fix For: 1.1.0, 0.7.1
>
>
> Accidentally created an immense attribute (36,000 bytes), which I indexed 
> with nifi.provenance.repository.indexed.attributes.  Received this error.
> ERROR [Provenance Repository Rollover Thread-1] 
> o.a.n.p.PersistentProvenanceRepository Failed to rollover Provenance 
> repository due to java.lang.IllegalArgumentException: Document contains at 
> least one immense term in field="FOO" (whose UTF8 encoding is longer than the 
> max length 32766), all of which were skipped. Please correct the analyzer to 
> not produce such terms.
> Perhaps this is as simple as changing 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/main/java/org/apache/nifi/provenance/RepositoryConfiguration.java#L37
>  to 32766 to match Lucene.  Investigation & testing needed.
> For background, this Lucene ticket made exceeding the term size limit an 
> IllegalArgumentException https://issues.apache.org/jira/browse/LUCENE-5472



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

[jira] [Commented] (NIFI-2787) PersistentProvenanceRepository rollover can fail on immense indexed attributes

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2787 truncate flowfile attributes that get indexed to fit within Lucene 
limits

Signed-off-by: Joe Skora 

This closes #1043


> PersistentProvenanceRepository rollover can fail on immense indexed attributes
> --
>
> Key: NIFI-2787
> URL: https://issues.apache.org/jira/browse/NIFI-2787
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
> Fix For: 1.1.0, 0.7.1
>
>
> Accidentally created an immense attribute (36,000 bytes), which I indexed 
> with nifi.provenance.repository.indexed.attributes.  Received this error.
> ERROR [Provenance Repository Rollover Thread-1] 
> o.a.n.p.PersistentProvenanceRepository Failed to rollover Provenance 
> repository due to java.lang.IllegalArgumentException: Document contains at 
> least one immense term in field="FOO" (whose UTF8 encoding is longer than the 
> max length 32766), all of which were skipped. Please correct the analyzer to 
> not produce such terms.
> Perhaps this is as simple as changing 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/main/java/org/apache/nifi/provenance/RepositoryConfiguration.java#L37
>  to 32766 to match Lucene.  Investigation & testing needed.
> For background, this Lucene ticket made exceeding the term size limit an 
> IllegalArgumentException https://issues.apache.org/jira/browse/LUCENE-5472



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

[GitHub] nifi pull request #1043: NIFI-2787 truncate flowfile attributes that get ind...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2711) Allow extension of nifi-assembly pom to override properties

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2711:
--

GitHub user brosander reopened a pull request:

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

NIFI-2711 - Making top-level nifi-assemblies directory with nifi-asse…

…mbly and nifi-toolkit-assembly underneath it

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

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

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

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


commit 5da37f36237c5a1ea4f11756a08a39dd478d53b4
Author: Bryan Rosander 
Date:   2016-08-30T20:12:11Z

NIFI-2711 - Making top-level nifi-assemblies directory with nifi-assembly 
and nifi-toolkit-assembly underneath it




> Allow extension of nifi-assembly pom to override properties
> ---
>
> Key: NIFI-2711
> URL: https://issues.apache.org/jira/browse/NIFI-2711
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>
> As part of the tls-toolkit work, the nifi.properties filtering was moved to 
> nifi-resources.  This didn't take into account usecases where overriding the 
> nifi.properties in an assembly was desired by those extending our assembly.



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

[GitHub] nifi pull request #972: NIFI-2711 - Making top-level nifi-assemblies directo...

[brosander]

GitHub user brosander reopened a pull request:

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

NIFI-2711 - Making top-level nifi-assemblies directory with nifi-asse…

…mbly and nifi-toolkit-assembly underneath it

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

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

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

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


commit 5da37f36237c5a1ea4f11756a08a39dd478d53b4
Author: Bryan Rosander 
Date:   2016-08-30T20:12:11Z

NIFI-2711 - Making top-level nifi-assemblies directory with nifi-assembly 
and nifi-toolkit-assembly underneath it




---
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-2711) Allow extension of nifi-assembly pom to override properties

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2711:
--

Github user brosander closed the pull request at:

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


> Allow extension of nifi-assembly pom to override properties
> ---
>
> Key: NIFI-2711
> URL: https://issues.apache.org/jira/browse/NIFI-2711
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>
> As part of the tls-toolkit work, the nifi.properties filtering was moved to 
> nifi-resources.  This didn't take into account usecases where overriding the 
> nifi.properties in an assembly was desired by those extending our assembly.



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

[GitHub] nifi pull request #972: NIFI-2711 - Making top-level nifi-assemblies directo...

[brosander]

Github user brosander closed the pull request at:

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


---
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-2711) Allow extension of nifi-assembly pom to override properties

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2711:
--

GitHub user brosander reopened a pull request:

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

NIFI-2711 - Making top-level nifi-assemblies directory with nifi-asse…

…mbly and nifi-toolkit-assembly underneath it

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

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

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

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


commit a137e2ab1333cdee0e09e9a0807ae484a480ff22
Author: Bryan Rosander 
Date:   2016-08-30T20:12:11Z

NIFI-2711 - Making top-level nifi-assemblies directory with nifi-assembly 
and nifi-toolkit-assembly underneath it




> Allow extension of nifi-assembly pom to override properties
> ---
>
> Key: NIFI-2711
> URL: https://issues.apache.org/jira/browse/NIFI-2711
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>
> As part of the tls-toolkit work, the nifi.properties filtering was moved to 
> nifi-resources.  This didn't take into account usecases where overriding the 
> nifi.properties in an assembly was desired by those extending our assembly.



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

[GitHub] nifi pull request #972: NIFI-2711 - Making top-level nifi-assemblies directo...

[brosander]

GitHub user brosander reopened a pull request:

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

NIFI-2711 - Making top-level nifi-assemblies directory with nifi-asse…

…mbly and nifi-toolkit-assembly underneath it

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

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

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

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


commit a137e2ab1333cdee0e09e9a0807ae484a480ff22
Author: Bryan Rosander 
Date:   2016-08-30T20:12:11Z

NIFI-2711 - Making top-level nifi-assemblies directory with nifi-assembly 
and nifi-toolkit-assembly underneath it




---
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-2711) Allow extension of nifi-assembly pom to override properties

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2711:
--

Github user brosander closed the pull request at:

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


> Allow extension of nifi-assembly pom to override properties
> ---
>
> Key: NIFI-2711
> URL: https://issues.apache.org/jira/browse/NIFI-2711
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>
> As part of the tls-toolkit work, the nifi.properties filtering was moved to 
> nifi-resources.  This didn't take into account usecases where overriding the 
> nifi.properties in an assembly was desired by those extending our assembly.



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

[GitHub] nifi pull request #972: NIFI-2711 - Making top-level nifi-assemblies directo...

[brosander]

Github user brosander closed the pull request at:

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


---
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-2787) PersistentProvenanceRepository rollover can fail on immense indexed attributes

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2787 truncate flowfile attributes that get indexed to fit within Lucene 
limits

* jskora adjusted for minor 0.x vs 1.x differences in 
TestPersistentProvenanceRepository class.

Signed-off-by: Joe Skora 


> PersistentProvenanceRepository rollover can fail on immense indexed attributes
> --
>
> Key: NIFI-2787
> URL: https://issues.apache.org/jira/browse/NIFI-2787
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
> Fix For: 1.1.0, 0.7.1
>
>
> Accidentally created an immense attribute (36,000 bytes), which I indexed 
> with nifi.provenance.repository.indexed.attributes.  Received this error.
> ERROR [Provenance Repository Rollover Thread-1] 
> o.a.n.p.PersistentProvenanceRepository Failed to rollover Provenance 
> repository due to java.lang.IllegalArgumentException: Document contains at 
> least one immense term in field="FOO" (whose UTF8 encoding is longer than the 
> max length 32766), all of which were skipped. Please correct the analyzer to 
> not produce such terms.
> Perhaps this is as simple as changing 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/main/java/org/apache/nifi/provenance/RepositoryConfiguration.java#L37
>  to 32766 to match Lucene.  Investigation & testing needed.
> For background, this Lucene ticket made exceeding the term size limit an 
> IllegalArgumentException https://issues.apache.org/jira/browse/LUCENE-5472



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

[jira] [Updated] (NIFI-2788) Cluster icon in the menu doesn't have a consistent size

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-2788:
--
Fix Version/s: 1.1.0

> Cluster icon in the menu doesn't have a consistent size
> ---
>
> Key: NIFI-2788
> URL: https://issues.apache.org/jira/browse/NIFI-2788
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: OSX, Chrome
>Reporter: Andrew Grande
>Assignee: Scott Aslan
>Priority: Trivial
> Fix For: 1.1.0
>
> Attachments: screenshot.png
>
>
> The global menu cluster icon has incorrect size, the Cluster menu item is 
> shifted to the right as a result.



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

[jira] [Commented] (NIFI-2788) Cluster icon in the menu doesn't have a consistent size

[ASF subversion and git services (JIRA)]

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

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

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

[NIFI-2788] update global hamburger menu to have fixed width icons and align 
text. This closes #1041


> Cluster icon in the menu doesn't have a consistent size
> ---
>
> Key: NIFI-2788
> URL: https://issues.apache.org/jira/browse/NIFI-2788
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: OSX, Chrome
>Reporter: Andrew Grande
>Assignee: Scott Aslan
>Priority: Trivial
> Attachments: screenshot.png
>
>
> The global menu cluster icon has incorrect size, the Cluster menu item is 
> shifted to the right as a result.



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

[jira] [Commented] (NIFI-2636) UnpackContent has concurrent thread safety issue, causes flowfiles to fail

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2636:
--

Github user mosermw closed the pull request at:

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


> UnpackContent has concurrent thread safety issue, causes flowfiles to fail
> --
>
> Key: NIFI-2636
> URL: https://issues.apache.org/jira/browse/NIFI-2636
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
> Fix For: 1.1.0, 0.8.0
>
>
> Shortly after merging NIFI-2611 I took a last look at the code and noticed 
> that each onTrigger() call, when the Packaging Format property is set to "use 
> mime.type attribute", that the class instance variable "private Unpacker 
> unpacker" can change.  When UnpackContent is set to > 1 concurrent task, this 
> isn't thread safe.  Thread A can set the unpacker to the TarUnpacker, but 
> before it gets a chance to unpack its tar file, Thread B changes the unpacker 
> to a FlowFileUnpackagerV3 which causes Thread A to fail its unpack.



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

[GitHub] nifi pull request #923: NIFI-2636 resolve thread safety problem in UnpackCon...

[mosermw]

Github user mosermw closed the pull request at:

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


---
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-2636) UnpackContent has concurrent thread safety issue, causes flowfiles to fail

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2636:
--

Github user mosermw commented on the issue:

https://github.com/apache/nifi/pull/923
  
Thanks @jskora.


> UnpackContent has concurrent thread safety issue, causes flowfiles to fail
> --
>
> Key: NIFI-2636
> URL: https://issues.apache.org/jira/browse/NIFI-2636
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
> Fix For: 1.1.0, 0.8.0
>
>
> Shortly after merging NIFI-2611 I took a last look at the code and noticed 
> that each onTrigger() call, when the Packaging Format property is set to "use 
> mime.type attribute", that the class instance variable "private Unpacker 
> unpacker" can change.  When UnpackContent is set to > 1 concurrent task, this 
> isn't thread safe.  Thread A can set the unpacker to the TarUnpacker, but 
> before it gets a chance to unpack its tar file, Thread B changes the unpacker 
> to a FlowFileUnpackagerV3 which causes Thread A to fail its unpack.



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

[GitHub] nifi issue #923: NIFI-2636 resolve thread safety problem in UnpackContent

[mosermw]

Github user mosermw commented on the issue:

https://github.com/apache/nifi/pull/923
  
Thanks @jskora.


---
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-2815) Cannot change script engine in InvokeScriptedProcessor

[Pierre Villard (JIRA)]

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

Pierre Villard updated NIFI-2815:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Cannot change script engine in InvokeScriptedProcessor
> --
>
> Key: NIFI-2815
> URL: https://issues.apache.org/jira/browse/NIFI-2815
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> Due to a regression introduced in NIFI-2665, the script engine for an 
> InvokeScriptedProcessor is instantiated only once. For instances already in 
> the flow, the Script Engine property setting will be honored, but it cannot 
> be changed. For new InvokeScriptedProcessor instances, the script engine will 
> be set to ECMAScript and also cannot be changed.
> Seems that before NIFI-2665, script engine setup was happening too often, now 
> it is not happening enough. The script engine should be reset when the 
> property has been modified.
> A workaround is to change the processor to the way you want it, then save it 
> as a template, then delete the original and re-load it from the template.



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

[jira] [Commented] (NIFI-2815) Cannot change script engine in InvokeScriptedProcessor

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2815: Fixed InvokeScriptedProcessor to allow changes to script engine type

This closes #1055.


> Cannot change script engine in InvokeScriptedProcessor
> --
>
> Key: NIFI-2815
> URL: https://issues.apache.org/jira/browse/NIFI-2815
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> Due to a regression introduced in NIFI-2665, the script engine for an 
> InvokeScriptedProcessor is instantiated only once. For instances already in 
> the flow, the Script Engine property setting will be honored, but it cannot 
> be changed. For new InvokeScriptedProcessor instances, the script engine will 
> be set to ECMAScript and also cannot be changed.
> Seems that before NIFI-2665, script engine setup was happening too often, now 
> it is not happening enough. The script engine should be reset when the 
> property has been modified.
> A workaround is to change the processor to the way you want it, then save it 
> as a template, then delete the original and re-load it from the template.



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

[GitHub] nifi pull request #1055: NIFI-2815: Fixed InvokeScriptedProcessor to allow c...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2815) Cannot change script engine in InvokeScriptedProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2815:
--

Github user asfgit closed the pull request at:

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


> Cannot change script engine in InvokeScriptedProcessor
> --
>
> Key: NIFI-2815
> URL: https://issues.apache.org/jira/browse/NIFI-2815
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> Due to a regression introduced in NIFI-2665, the script engine for an 
> InvokeScriptedProcessor is instantiated only once. For instances already in 
> the flow, the Script Engine property setting will be honored, but it cannot 
> be changed. For new InvokeScriptedProcessor instances, the script engine will 
> be set to ECMAScript and also cannot be changed.
> Seems that before NIFI-2665, script engine setup was happening too often, now 
> it is not happening enough. The script engine should be reset when the 
> property has been modified.
> A workaround is to change the processor to the way you want it, then save it 
> as a template, then delete the original and re-load it from the template.



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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

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

https://github.com/apache/nifi/pull/1057#discussion_r80288218
  
--- Diff: 
nifi-nar-bundles/nifi-evtx-bundle/nifi-evtx-processors/src/main/java/org/apache/nifi/processors/evtx/parser/BinaryReader.java
 ---
@@ -86,9 +86,9 @@ public int read() {
 }
 
 /**
- * Returns the byte that would be read without changing the posiiton
+ * Returns the byte that would be read without changing the positon
--- End diff --

position


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

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

https://github.com/apache/nifi/pull/1057#discussion_r80288960
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/crypto/bcrypt/BCrypt.java
 ---
@@ -25,7 +25,7 @@
  * This password hashing system tries to thwart off-line password
  * cracking using a computationally-intensive hashing algorithm,
  * based on Bruce Schneier's Blowfish cipher. The work factor of
- * the algorithm is parameterised, so it can be increased as
+ * the algorithm is parametrised, so it can be increased as
--- End diff --

parametrized 


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

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

https://github.com/apache/nifi/pull/1057#discussion_r80288407
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-client-dto/src/main/java/org/apache/nifi/web/api/dto/ControllerConfigurationDTO.java
 ---
@@ -47,7 +47,7 @@ public void setMaxTimerDrivenThreadCount(Integer 
maxTimerDrivenThreadCount) {
  * @return maximum number of event driven thread this NiFi has 
available
  */
 @ApiModelProperty(
-value = "The maximum number of event driven threads the NiFi 
has avaiable."
+value = "The maximum number of event driven threads the NiFi 
has avaliable."
--- End diff --

available


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[GitHub] nifi issue #1055: NIFI-2815: Fixed InvokeScriptedProcessor to allow changes ...

[pvillard31]

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1055
  
+1 merging into master


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

[jira] [Commented] (NIFI-2815) Cannot change script engine in InvokeScriptedProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2815:
--

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1055
  
+1 merging into master


> Cannot change script engine in InvokeScriptedProcessor
> --
>
> Key: NIFI-2815
> URL: https://issues.apache.org/jira/browse/NIFI-2815
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> Due to a regression introduced in NIFI-2665, the script engine for an 
> InvokeScriptedProcessor is instantiated only once. For instances already in 
> the flow, the Script Engine property setting will be honored, but it cannot 
> be changed. For new InvokeScriptedProcessor instances, the script engine will 
> be set to ECMAScript and also cannot be changed.
> Seems that before NIFI-2665, script engine setup was happening too often, now 
> it is not happening enough. The script engine should be reset when the 
> property has been modified.
> A workaround is to change the processor to the way you want it, then save it 
> as a template, then delete the original and re-load it from the template.



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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

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

https://github.com/apache/nifi/pull/1057#discussion_r80288233
  
--- Diff: 
nifi-nar-bundles/nifi-evtx-bundle/nifi-evtx-processors/src/main/java/org/apache/nifi/processors/evtx/parser/BinaryReader.java
 ---
@@ -86,9 +86,9 @@ public int read() {
 }
 
 /**
- * Returns the byte that would be read without changing the posiiton
+ * Returns the byte that would be read without changing the positon
  *
- * @return the byte that would be read without changing the posiiton
+ * @return the byte that would be read without changing the positon
--- End diff --

position


> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[GitHub] nifi pull request #1057: NIFI-2816 - Clean typos across the code

[pvillard31]

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

https://github.com/apache/nifi/pull/1057#discussion_r80288407
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-client-dto/src/main/java/org/apache/nifi/web/api/dto/ControllerConfigurationDTO.java
 ---
@@ -47,7 +47,7 @@ public void setMaxTimerDrivenThreadCount(Integer 
maxTimerDrivenThreadCount) {
  * @return maximum number of event driven thread this NiFi has 
available
  */
 @ApiModelProperty(
-value = "The maximum number of event driven threads the NiFi 
has avaiable."
+value = "The maximum number of event driven threads the NiFi 
has avaliable."
--- End diff --

available


---
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 #1057: NIFI-2816 - Clean typos across the code

[pvillard31]

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

https://github.com/apache/nifi/pull/1057#discussion_r80288960
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/crypto/bcrypt/BCrypt.java
 ---
@@ -25,7 +25,7 @@
  * This password hashing system tries to thwart off-line password
  * cracking using a computationally-intensive hashing algorithm,
  * based on Bruce Schneier's Blowfish cipher. The work factor of
- * the algorithm is parameterised, so it can be increased as
+ * the algorithm is parametrised, so it can be increased as
--- End diff --

parametrized 


---
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 #1057: NIFI-2816 - Clean typos across the code

[pvillard31]

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

https://github.com/apache/nifi/pull/1057#discussion_r80288347
  
--- Diff: 
nifi-mock/src/main/java/org/apache/nifi/util/MockProcessSession.java ---
@@ -164,7 +164,7 @@ public void commit() {
  * {@link org.apache.nifi.processor.Processor#onTrigger} commits or 
rolls back the
  * session
  */
-public void clearCommited() {
+public void clearCommitted() {
--- End diff --

Is it a safe change?


---
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 #1057: NIFI-2816 - Clean typos across the code

[pvillard31]

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

https://github.com/apache/nifi/pull/1057#discussion_r80288218
  
--- Diff: 
nifi-nar-bundles/nifi-evtx-bundle/nifi-evtx-processors/src/main/java/org/apache/nifi/processors/evtx/parser/BinaryReader.java
 ---
@@ -86,9 +86,9 @@ public int read() {
 }
 
 /**
- * Returns the byte that would be read without changing the posiiton
+ * Returns the byte that would be read without changing the positon
--- End diff --

position


---
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 #1057: NIFI-2816 - Clean typos across the code

[pvillard31]

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

https://github.com/apache/nifi/pull/1057#discussion_r80288233
  
--- Diff: 
nifi-nar-bundles/nifi-evtx-bundle/nifi-evtx-processors/src/main/java/org/apache/nifi/processors/evtx/parser/BinaryReader.java
 ---
@@ -86,9 +86,9 @@ public int read() {
 }
 
 /**
- * Returns the byte that would be read without changing the posiiton
+ * Returns the byte that would be read without changing the positon
  *
- * @return the byte that would be read without changing the posiiton
+ * @return the byte that would be read without changing the positon
--- End diff --

position


---
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-2636) UnpackContent has concurrent thread safety issue, causes flowfiles to fail

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2636 resolve thread safety problem in UnpackContent

Signed-off-by: Joe Skora 


> UnpackContent has concurrent thread safety issue, causes flowfiles to fail
> --
>
> Key: NIFI-2636
> URL: https://issues.apache.org/jira/browse/NIFI-2636
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Michael Moser
>Assignee: Michael Moser
> Fix For: 1.1.0, 0.8.0
>
>
> Shortly after merging NIFI-2611 I took a last look at the code and noticed 
> that each onTrigger() call, when the Packaging Format property is set to "use 
> mime.type attribute", that the class instance variable "private Unpacker 
> unpacker" can change.  When UnpackContent is set to > 1 concurrent task, this 
> isn't thread safe.  Thread A can set the unpacker to the TarUnpacker, but 
> before it gets a chance to unpack its tar file, Thread B changes the unpacker 
> to a FlowFileUnpackagerV3 which causes Thread A to fail its unpack.



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

[jira] [Commented] (NIFI-2816) The great typo cleanup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2816:
--

GitHub user trixpan opened a pull request:

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

NIFI-2816 - Clean typos across the code

part 1 of typo hunting

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

$ git pull https://github.com/trixpan/nifi typos

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

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


commit 9e53a083fc5e29693f3b3953f925e4cb9b6c5bd3
Author: Andre F de Miranda 
Date:   2016-09-23T16:32:53Z

NIFI-2816 - Clean typos across the code




> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




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

[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=15516937#comment-15516937
 ] 

ASF GitHub Bot commented on NIFI-2812:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1047
  
@fidget83 the JARs should not be unified, instead only the appropriate JARs 
should go into each directory. Would you mind amending your commit?

Kind regards


> 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)

[GitHub] nifi pull request #1057: NIFI-2816 - Clean typos across the code

[trixpan]

GitHub user trixpan opened a pull request:

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

NIFI-2816 - Clean typos across the code

part 1 of typo hunting

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

$ git pull https://github.com/trixpan/nifi typos

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

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


commit 9e53a083fc5e29693f3b3953f925e4cb9b6c5bd3
Author: Andre F de Miranda 
Date:   2016-09-23T16:32:53Z

NIFI-2816 - Clean typos across the code




---
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-2816) The great typo cleanup

[Andre (JIRA)]

Andre created NIFI-2816:
---

 Summary: The great typo cleanup
 Key: NIFI-2816
 URL: https://issues.apache.org/jira/browse/NIFI-2816
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Andre
Assignee: Andre






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

[jira] [Commented] (NIFI-2783) Command line site-to-site client in toolkit would be useful

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2783:
--

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/1056
  
Usage and examples can be displayed by running s2s.sh -h


> Command line site-to-site client in toolkit would be useful
> ---
>
> Key: NIFI-2783
> URL: https://issues.apache.org/jira/browse/NIFI-2783
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Bryan Rosander
>
> A command line site-to-site client in the toolkit would be beneficial in 
> several scenarios:
> 1. Easily pipe data into, out of NiFi flows using command line utilities or 
> other (non-java) programs makes integrating other tools with NiFi trivial
> 2. Easier to debug site-to-site issues when only one NiFi instance is 
> involved in the troubleshooting process
> 3. Dev testing site-to-site is easier command line reproduction of 
> issues/validation of functionality



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

[jira] [Commented] (NIFI-2783) Command line site-to-site client in toolkit would be useful

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2783:
--

GitHub user brosander reopened a pull request:

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

NIFI-2783 - Site-to-site command line client



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

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

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

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


commit 2ae3e59989d548e77d14b82248246bc8e2ad8ba4
Author: Bryan Rosander 
Date:   2016-09-23T15:32:05Z

NIFI-2783 - Site-to-site command line client

commit 805772df3c40b50fbf5d7c58c8be1d43db4e42d4
Author: Bryan Rosander 
Date:   2016-09-23T16:12:11Z

NIFI-2783 - s2s.sh shell script warnings -> stderr, usage improvement with 
examples




> Command line site-to-site client in toolkit would be useful
> ---
>
> Key: NIFI-2783
> URL: https://issues.apache.org/jira/browse/NIFI-2783
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Bryan Rosander
>
> A command line site-to-site client in the toolkit would be beneficial in 
> several scenarios:
> 1. Easily pipe data into, out of NiFi flows using command line utilities or 
> other (non-java) programs makes integrating other tools with NiFi trivial
> 2. Easier to debug site-to-site issues when only one NiFi instance is 
> involved in the troubleshooting process
> 3. Dev testing site-to-site is easier command line reproduction of 
> issues/validation of functionality



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

[GitHub] nifi pull request #1056: NIFI-2783 - Site-to-site command line client

[brosander]

GitHub user brosander reopened a pull request:

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

NIFI-2783 - Site-to-site command line client



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

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

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

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


commit 2ae3e59989d548e77d14b82248246bc8e2ad8ba4
Author: Bryan Rosander 
Date:   2016-09-23T15:32:05Z

NIFI-2783 - Site-to-site command line client

commit 805772df3c40b50fbf5d7c58c8be1d43db4e42d4
Author: Bryan Rosander 
Date:   2016-09-23T16:12:11Z

NIFI-2783 - s2s.sh shell script warnings -> stderr, usage improvement with 
examples




---
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-2783) Command line site-to-site client in toolkit would be useful

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2783:
--

Github user brosander closed the pull request at:

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


> Command line site-to-site client in toolkit would be useful
> ---
>
> Key: NIFI-2783
> URL: https://issues.apache.org/jira/browse/NIFI-2783
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Bryan Rosander
>
> A command line site-to-site client in the toolkit would be beneficial in 
> several scenarios:
> 1. Easily pipe data into, out of NiFi flows using command line utilities or 
> other (non-java) programs makes integrating other tools with NiFi trivial
> 2. Easier to debug site-to-site issues when only one NiFi instance is 
> involved in the troubleshooting process
> 3. Dev testing site-to-site is easier command line reproduction of 
> issues/validation of functionality



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

[GitHub] nifi pull request #1056: NIFI-2783 - Site-to-site command line client

[brosander]

Github user brosander closed the pull request at:

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


---
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-2815) Cannot change script engine in InvokeScriptedProcessor

[Matt Burgess (JIRA)]

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

Matt Burgess updated NIFI-2815:
---
Description: 
Due to a regression introduced in NIFI-2665, the script engine for an 
InvokeScriptedProcessor is instantiated only once. For instances already in the 
flow, the Script Engine property setting will be honored, but it cannot be 
changed. For new InvokeScriptedProcessor instances, the script engine will be 
set to ECMAScript and also cannot be changed.

Seems that before NIFI-2665, script engine setup was happening too often, now 
it is not happening enough. The script engine should be reset when the property 
has been modified.

A workaround is to change the processor to the way you want it, then save it as 
a template, then delete the original and re-load it from the template.

  was:
Due to a regression introduced in NIFI-2665, the script engine for an 
InvokeScriptedProcessor is instantiated only once. For instances already in the 
flow, the Script Engine property setting will be honored, but it cannot be 
changed. For new InvokeScriptedProcessor instances, the script engine will be 
set to ECMAScript and also cannot be changed.

Seems that before NIFI-2665, script engine setup was happening too often, now 
it is not happening enough. The script engine should be reset when the property 
has been modified.


> Cannot change script engine in InvokeScriptedProcessor
> --
>
> Key: NIFI-2815
> URL: https://issues.apache.org/jira/browse/NIFI-2815
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> Due to a regression introduced in NIFI-2665, the script engine for an 
> InvokeScriptedProcessor is instantiated only once. For instances already in 
> the flow, the Script Engine property setting will be honored, but it cannot 
> be changed. For new InvokeScriptedProcessor instances, the script engine will 
> be set to ECMAScript and also cannot be changed.
> Seems that before NIFI-2665, script engine setup was happening too often, now 
> it is not happening enough. The script engine should be reset when the 
> property has been modified.
> A workaround is to change the processor to the way you want it, then save it 
> as a template, then delete the original and re-load it from the template.



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

[jira] [Commented] (NIFI-2072) Support named captures in ExtractText

[Joey Frazee (JIRA)]

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

Joey Frazee commented on NIFI-2072:
---

[~pvillard] Yeah, I honestly just assumed that would have been there in the 
Pattern and/or Matcher. I do want to ask, though, from a usability perspective, 
if getting a bit nasty might be justified here?

> Support named captures in ExtractText
> -
>
> Key: NIFI-2072
> URL: https://issues.apache.org/jira/browse/NIFI-2072
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>
> ExtractText currently captures and creates attributes using numeric indices 
> (e.g, attribute.name.0, attribute.name.1, etc.) whether or not the capture 
> groups are named, i.e., patterns like (?\w+).
> In addition to being more faithful to the provided regexes, named captures 
> could help simplify data flows because you wouldn't have to add superfluous 
> UpdateAttribute steps which are just renaming the indexed captures to more 
> interpretable names.



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

[jira] [Commented] (NIFI-2815) Cannot change script engine in InvokeScriptedProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2815:
--

Github user brosander commented on the issue:

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


> Cannot change script engine in InvokeScriptedProcessor
> --
>
> Key: NIFI-2815
> URL: https://issues.apache.org/jira/browse/NIFI-2815
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> Due to a regression introduced in NIFI-2665, the script engine for an 
> InvokeScriptedProcessor is instantiated only once. For instances already in 
> the flow, the Script Engine property setting will be honored, but it cannot 
> be changed. For new InvokeScriptedProcessor instances, the script engine will 
> be set to ECMAScript and also cannot be changed.
> Seems that before NIFI-2665, script engine setup was happening too often, now 
> it is not happening enough. The script engine should be reset when the 
> property has been modified.



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

[GitHub] nifi issue #239: Nifi 1540 - AWS Kinesis Get and Put Processors

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/239
  
@mans2singh, do you plan to continue working on this PR?  If not, would you 
please close it? 


---
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=15516740#comment-15516740
 ] 

ASF GitHub Bot commented on NIFI-2812:
--

Github user fidget83 commented on the issue:

https://github.com/apache/nifi/pull/1047
  
@trixpan, I just unified the list of jars in rpm and in created 
.tar.gz.file. I didn't analyze necessary of each jar, but with this set nifi 
works :)


> 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] [Updated] (NIFI-2815) Cannot change script engine in InvokeScriptedProcessor

[Matt Burgess (JIRA)]

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

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

> Cannot change script engine in InvokeScriptedProcessor
> --
>
> Key: NIFI-2815
> URL: https://issues.apache.org/jira/browse/NIFI-2815
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> Due to a regression introduced in NIFI-2665, the script engine for an 
> InvokeScriptedProcessor is instantiated only once. For instances already in 
> the flow, the Script Engine property setting will be honored, but it cannot 
> be changed. For new InvokeScriptedProcessor instances, the script engine will 
> be set to ECMAScript and also cannot be changed.
> Seems that before NIFI-2665, script engine setup was happening too often, now 
> it is not happening enough. The script engine should be reset when the 
> property has been modified.



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

[jira] [Resolved] (NIFI-2810) Allow Content Type to be set in PutS3Object processor

[Pierre Villard (JIRA)]

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

Pierre Villard resolved NIFI-2810.
--
Resolution: Fixed

Visually verified code.
Full build with contrib-check and tested with simple workflow.
Merged into master. Thanks [~evega]!

> Allow Content Type to be set in PutS3Object processor
> -
>
> Key: NIFI-2810
> URL: https://issues.apache.org/jira/browse/NIFI-2810
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Edgardo Vega
>Priority: Minor
> Fix For: 1.1.0
>
>
> The PutS3 Processor does not allow you to set the Content Type. Add this 
> ability in this processor



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

[jira] [Commented] (NIFI-2810) Allow Content Type to be set in PutS3Object processor

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2810 Allow Content Type to be set in PutS3Object processor

This closes #1034.


> Allow Content Type to be set in PutS3Object processor
> -
>
> Key: NIFI-2810
> URL: https://issues.apache.org/jira/browse/NIFI-2810
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Edgardo Vega
>Priority: Minor
> Fix For: 1.1.0
>
>
> The PutS3 Processor does not allow you to set the Content Type. Add this 
> ability in this processor



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

[GitHub] nifi pull request #1034: [NIFI-2810] Allow Content Type to be set in PutS3Ob...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2810) Allow Content Type to be set in PutS3Object processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2810:
--

Github user asfgit closed the pull request at:

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


> Allow Content Type to be set in PutS3Object processor
> -
>
> Key: NIFI-2810
> URL: https://issues.apache.org/jira/browse/NIFI-2810
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Edgardo Vega
>Priority: Minor
> Fix For: 1.1.0
>
>
> The PutS3 Processor does not allow you to set the Content Type. Add this 
> ability in this processor



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

[GitHub] nifi-minifi pull request #39: MINIFI-81 Adding a check for a valid command t...

[JPercivall]

GitHub user JPercivall opened a pull request:

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

MINIFI-81 Adding a check for a valid command to the config.sh toolkit…

… script

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

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

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

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


commit 189a5ee21012a5b0c67ecc6a29dd91df6615a1d9
Author: Joseph Percivall 
Date:   2016-09-23T15:11:41Z

MINIFI-81 Adding a check for a valid command to the config.sh toolkit script




---
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-2815) Cannot change script engine in InvokeScriptedProcessor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2815:
--

GitHub user mattyb149 opened a pull request:

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

NIFI-2815: Fixed InvokeScriptedProcessor to allow changes to script engine 
type



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

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

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

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


commit 6803255505fb845cd999b9704f06db55a54083d8
Author: Matt Burgess 
Date:   2016-09-23T15:04:51Z

NIFI-2815: Fixed InvokeScriptedProcessor to allow changes to script engine 
type




> Cannot change script engine in InvokeScriptedProcessor
> --
>
> Key: NIFI-2815
> URL: https://issues.apache.org/jira/browse/NIFI-2815
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> Due to a regression introduced in NIFI-2665, the script engine for an 
> InvokeScriptedProcessor is instantiated only once. For instances already in 
> the flow, the Script Engine property setting will be honored, but it cannot 
> be changed. For new InvokeScriptedProcessor instances, the script engine will 
> be set to ECMAScript and also cannot be changed.
> Seems that before NIFI-2665, script engine setup was happening too often, now 
> it is not happening enough. The script engine should be reset when the 
> property has been modified.



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

[GitHub] nifi pull request #1055: NIFI-2815: Fixed InvokeScriptedProcessor to allow c...

[mattyb149]

GitHub user mattyb149 opened a pull request:

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

NIFI-2815: Fixed InvokeScriptedProcessor to allow changes to script engine 
type



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

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

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

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


commit 6803255505fb845cd999b9704f06db55a54083d8
Author: Matt Burgess 
Date:   2016-09-23T15:04:51Z

NIFI-2815: Fixed InvokeScriptedProcessor to allow changes to script engine 
type




---
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-2815) Cannot change script engine in InvokeScriptedProcessor

[Matt Burgess (JIRA)]

Matt Burgess created NIFI-2815:
--

 Summary: Cannot change script engine in InvokeScriptedProcessor
 Key: NIFI-2815
 URL: https://issues.apache.org/jira/browse/NIFI-2815
 Project: Apache NiFi
  Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Matt Burgess
Assignee: Matt Burgess
 Fix For: 1.1.0


Due to a regression introduced in NIFI-2665, the script engine for an 
InvokeScriptedProcessor is instantiated only once. For instances already in the 
flow, the Script Engine property setting will be honored, but it cannot be 
changed. For new InvokeScriptedProcessor instances, the script engine will be 
set to ECMAScript and also cannot be changed.

Seems that before NIFI-2665, script engine setup was happening too often, now 
it is not happening enough. The script engine should be reset when the property 
has been modified.



--
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: gcs_bundle.patch

Initial patch for review. Integration tests included. Please review and let me 
know what changes need to be made. Thanks!

> 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: gcs_bundle.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-2810) Allow Content Type to be set in PutS3Object processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2810:
--

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

https://github.com/apache/nifi/pull/1034#discussion_r80259616
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -132,6 +132,19 @@
 .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
 .build();
 
+public static final PropertyDescriptor CONTENT_TYPE = new 
PropertyDescriptor.Builder()
+.name("Content Type")
+.description("Sets the Content-Type HTTP header indicating the 
type of content stored in the associated " +
+"object. The value of this header is a standard MIME 
type.\n" +
+"AWS S3 Java client will attempt to determine the correct 
content type if one hasn't been set" +
+" yet. Users are responsible for ensuring a suitable 
content type is set when uploading streams. If " +
+"no content type is provided and cannot be determined by 
the filename, the default content type " +
+"\"application/octet-stream\" will be used.")
--- End diff --

OK yeah, understood!


> Allow Content Type to be set in PutS3Object processor
> -
>
> Key: NIFI-2810
> URL: https://issues.apache.org/jira/browse/NIFI-2810
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Edgardo Vega
>Priority: Minor
> Fix For: 1.1.0
>
>
> The PutS3 Processor does not allow you to set the Content Type. Add this 
> ability in this processor



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

[GitHub] nifi pull request #1034: [NIFI-2810] Allow Content Type to be set in PutS3Ob...

[pvillard31]

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

https://github.com/apache/nifi/pull/1034#discussion_r80259616
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -132,6 +132,19 @@
 .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
 .build();
 
+public static final PropertyDescriptor CONTENT_TYPE = new 
PropertyDescriptor.Builder()
+.name("Content Type")
+.description("Sets the Content-Type HTTP header indicating the 
type of content stored in the associated " +
+"object. The value of this header is a standard MIME 
type.\n" +
+"AWS S3 Java client will attempt to determine the correct 
content type if one hasn't been set" +
+" yet. Users are responsible for ensuring a suitable 
content type is set when uploading streams. If " +
+"no content type is provided and cannot be determined by 
the filename, the default content type " +
+"\"application/octet-stream\" will be used.")
--- End diff --

OK yeah, understood!


---
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=15516597#comment-15516597
 ] 

ASF GitHub Bot commented on NIFI-2812:
--

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

https://github.com/apache/nifi/pull/1047#discussion_r80253235
  
--- Diff: nifi-assembly/pom.xml ---
@@ -505,11 +510,18 @@ language governing permissions and limitations under 
the License. -->
 
/opt/nifi/nifi-${project.version}/lib
 
 
+
net.minidev:asm
--- End diff --

are you sure this is necessary?


> 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-2810) Allow Content Type to be set in PutS3Object processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2810:
--

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

https://github.com/apache/nifi/pull/1034#discussion_r80255627
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/s3/ITPutS3Object.java
 ---
@@ -238,6 +238,26 @@ public void testMetaData() throws IOException {
 }
 
 @Test
+public void testContentType() throws IOException {
+PutS3Object processor = new PutS3Object();
+final TestRunner runner = TestRunners.newTestRunner(processor);
+
+runner.setProperty(PutS3Object.CREDENTIALS_FILE, CREDENTIALS_FILE);
+runner.setProperty(PutS3Object.REGION, REGION);
+runner.setProperty(PutS3Object.BUCKET, BUCKET_NAME);
+runner.setProperty(PutS3Object.CONTENT_TYPE, "text/plain");
+
+runner.enqueue(getResourcePath(SAMPLE_FILE_RESOURCE_NAME));
+
+runner.run();
+
+runner.assertAllFlowFilesTransferred(PutS3Object.REL_SUCCESS, 1);
+List flowFiles = 
runner.getFlowFilesForRelationship(PutS3Object.REL_SUCCESS);
+MockFlowFile ff1 = flowFiles.get(0);
+ff1.assertAttributeEquals(PutS3Object.S3_CONTENT_TYPE, 
"text/plain");
--- End diff --

Done


> Allow Content Type to be set in PutS3Object processor
> -
>
> Key: NIFI-2810
> URL: https://issues.apache.org/jira/browse/NIFI-2810
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Edgardo Vega
>Priority: Minor
> Fix For: 1.1.0
>
>
> The PutS3 Processor does not allow you to set the Content Type. Add this 
> ability in this processor



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

[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=15516600#comment-15516600
 ] 

ASF GitHub Bot commented on NIFI-2812:
--

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

https://github.com/apache/nifi/pull/1047#discussion_r80255200
  
--- Diff: nifi-assembly/pom.xml ---
@@ -505,11 +510,18 @@ language governing permissions and limitations under 
the License. -->
 
/opt/nifi/nifi-${project.version}/lib
 
 
+
net.minidev:asm
+
asm:asm
+
org.bouncycastle:bcpkix-jdk15on
+
com.fasterxml.jackson.core:jackson-annotations
+
com.fasterxml.jackson.core:jackson-core
+
com.fasterxml.jackson.core:jackson-databind
--- End diff --

seems to be absent from tar file? Sure it is required?


> 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-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=15516602#comment-15516602
 ] 

ASF GitHub Bot commented on NIFI-2812:
--

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

https://github.com/apache/nifi/pull/1047#discussion_r80255224
  
--- Diff: nifi-assembly/pom.xml ---
@@ -505,11 +510,18 @@ language governing permissions and limitations under 
the License. -->
 
/opt/nifi/nifi-${project.version}/lib
 
 
+
net.minidev:asm
+
asm:asm
+
org.bouncycastle:bcpkix-jdk15on
+
com.fasterxml.jackson.core:jackson-annotations
+
com.fasterxml.jackson.core:jackson-core
+
com.fasterxml.jackson.core:jackson-databind
+
com.jayway.jsonpath:json-path
--- End diff --

seems to be absent from tar file? Sure it is required?


> 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-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=15516601#comment-15516601
 ] 

ASF GitHub Bot commented on NIFI-2812:
--

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

https://github.com/apache/nifi/pull/1047#discussion_r80255144
  
--- Diff: nifi-assembly/pom.xml ---
@@ -505,11 +510,18 @@ language governing permissions and limitations under 
the License. -->
 
/opt/nifi/nifi-${project.version}/lib
 
 
+
net.minidev:asm
+
asm:asm
+
org.bouncycastle:bcpkix-jdk15on
+
com.fasterxml.jackson.core:jackson-annotations
--- End diff --

seems to be absent from tar file? Sure it is required?


> 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-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=15516599#comment-15516599
 ] 

ASF GitHub Bot commented on NIFI-2812:
--

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

https://github.com/apache/nifi/pull/1047#discussion_r80255251
  
--- Diff: nifi-assembly/pom.xml ---
@@ -505,11 +510,18 @@ language governing permissions and limitations under 
the License. -->
 
/opt/nifi/nifi-${project.version}/lib
 
 
+
net.minidev:asm
+
asm:asm
+
org.bouncycastle:bcpkix-jdk15on
+
com.fasterxml.jackson.core:jackson-annotations
+
com.fasterxml.jackson.core:jackson-core
+
com.fasterxml.jackson.core:jackson-databind
+
com.jayway.jsonpath:json-path
+
net.minidev:json-smart
--- End diff --

seems to be absent from tar file? Sure it is required?


> 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-2810) Allow Content Type to be set in PutS3Object processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2810:
--

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

https://github.com/apache/nifi/pull/1034#discussion_r80255599
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/PutS3Object.java
 ---
@@ -132,6 +132,19 @@
 .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
 .build();
 
+public static final PropertyDescriptor CONTENT_TYPE = new 
PropertyDescriptor.Builder()
+.name("Content Type")
--- End diff --

Done


> Allow Content Type to be set in PutS3Object processor
> -
>
> Key: NIFI-2810
> URL: https://issues.apache.org/jira/browse/NIFI-2810
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Edgardo Vega
>Priority: Minor
> Fix For: 1.1.0
>
>
> The PutS3 Processor does not allow you to set the Content Type. Add this 
> ability in this processor



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

[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=15516598#comment-15516598
 ] 

ASF GitHub Bot commented on NIFI-2812:
--

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

https://github.com/apache/nifi/pull/1047#discussion_r80255166
  
--- Diff: nifi-assembly/pom.xml ---
@@ -505,11 +510,18 @@ language governing permissions and limitations under 
the License. -->
 
/opt/nifi/nifi-${project.version}/lib
 
 
+
net.minidev:asm
+
asm:asm
+
org.bouncycastle:bcpkix-jdk15on
+
com.fasterxml.jackson.core:jackson-annotations
+
com.fasterxml.jackson.core:jackson-core
--- End diff --

seems to be absent from tar file? Sure it is required?


> 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-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=15516596#comment-15516596
 ] 

ASF GitHub Bot commented on NIFI-2812:
--

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

https://github.com/apache/nifi/pull/1047#discussion_r80253174
  
--- Diff: nifi-assembly/pom.xml ---
@@ -505,11 +510,18 @@ language governing permissions and limitations under 
the License. -->
 
/opt/nifi/nifi-${project.version}/lib
 
 
+
net.minidev:asm
+
asm:asm
--- End diff --

are you sure this is necessary?


> 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)

[GitHub] nifi pull request #1034: [NIFI-2810] Allow Content Type to be set in PutS3Ob...

[vegaed]

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

https://github.com/apache/nifi/pull/1034#discussion_r80255627
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/s3/ITPutS3Object.java
 ---
@@ -238,6 +238,26 @@ public void testMetaData() throws IOException {
 }
 
 @Test
+public void testContentType() throws IOException {
+PutS3Object processor = new PutS3Object();
+final TestRunner runner = TestRunners.newTestRunner(processor);
+
+runner.setProperty(PutS3Object.CREDENTIALS_FILE, CREDENTIALS_FILE);
+runner.setProperty(PutS3Object.REGION, REGION);
+runner.setProperty(PutS3Object.BUCKET, BUCKET_NAME);
+runner.setProperty(PutS3Object.CONTENT_TYPE, "text/plain");
+
+runner.enqueue(getResourcePath(SAMPLE_FILE_RESOURCE_NAME));
+
+runner.run();
+
+runner.assertAllFlowFilesTransferred(PutS3Object.REL_SUCCESS, 1);
+List flowFiles = 
runner.getFlowFilesForRelationship(PutS3Object.REL_SUCCESS);
+MockFlowFile ff1 = flowFiles.get(0);
+ff1.assertAttributeEquals(PutS3Object.S3_CONTENT_TYPE, 
"text/plain");
--- End diff --

Done


---
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.
---