[jira] [Commented] (NIFI-2608) Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2608:
---

Have verified that the threads Kafka spawns are seeing the 
NarThreadContextClasslaoder as the current context class loader of those 
threads.  As a result there is nothing for them to bind to in terms of a 
specific NarClassloader.  Looks like we know precisely which NarClassLoader we 
should use when going to a given component so we can be far more precise.  Need 
to understand why we're not already doing this.  But will run some experiments.

> Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients
> ---
>
> Key: NIFI-2608
> URL: https://issues.apache.org/jira/browse/NIFI-2608
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Oleg Zhurakousky
>Assignee: Joseph Witt
>Priority: Critical
> Fix For: 1.0.0
>
>
> KafkaConsumer went fro thread-safe in 0.8 to not-thread-safe in 0.9 which was 
> overlooked while implementing new ConsumeKafka processor which relied on 0.9 
> Client API.



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

[jira] [Commented] (NIFI-2608) Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2608:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/930
  
Update on weird behavior with subclassing.  Turns out I can run either 0.9 
or 0.10.  Whichever runs first wins.  There is clearly something going on with 
classloading.  Looking into Kafka source code and what we're doing as well.


> Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients
> ---
>
> Key: NIFI-2608
> URL: https://issues.apache.org/jira/browse/NIFI-2608
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Oleg Zhurakousky
>Assignee: Joseph Witt
>Priority: Critical
> Fix For: 1.0.0
>
>
> KafkaConsumer went fro thread-safe in 0.8 to not-thread-safe in 0.9 which was 
> overlooked while implementing new ConsumeKafka processor which relied on 0.9 
> Client API.



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

[GitHub] nifi issue #930: NIFI-2608 reworked consumer to match API. Added support for...

[joewitt]

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/930
  
Update on weird behavior with subclassing.  Turns out I can run either 0.9 
or 0.10.  Whichever runs first wins.  There is clearly something going on with 
classloading.  Looking into Kafka source code and what we're doing as well.


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

[jira] [Commented] (NIFI-2603) Bringing Some UI Color Back

[Peter Wicks (JIRA)]

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

Peter Wicks commented on NIFI-2603:
---

[~scottyaslan] I've done all the work for the changes in my screenshots. Can 
you take a look and provide feedback?
https://github.com/patricker/nifi/tree/NIFI-2603

This is absolutely a first pass.  Lets talk it over and come up with the right 
approach.  I have no issues continuing to make changes for this ticket.

> Bringing Some UI Color Back
> ---
>
> Key: NIFI-2603
> URL: https://issues.apache.org/jira/browse/NIFI-2603
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Peter Wicks
>Priority: Minor
>
> In the new 1.0 UI all of the colors associated with status (except the orange 
> triangle) are gone; replaced with a dark gray color.
> I propose bringing back color.  The screenshots are in the format of before 
> on the top and after on the bottom, except were labeled in the picture itself:
>  - Top Status Menu: https://goo.gl/photos/se1JnvhRwU7N4Fap7
>  - Process Group: https://goo.gl/photos/dqjG4KvC6xqxQfgT7
>  - Processes (Running/Stopped/Invalid): 
> https://goo.gl/photos/dSS8vgE2RkrXtc77A
>  - Operate Play/Stop buttons (only on mouse hover): 
> https://goo.gl/photos/Am5SUEEn7G9RjmMe6
>  - Processor/Processor Group Context Menu: 
> https://goo.gl/photos/Jq3qFg4ezaN91qms5
> This is not a "100% done, I've covered everything" before/after list.  I know 
> I need to do the NiFi summary page also at the minimum.



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

[jira] [Commented] (NIFI-2603) Bringing Some UI Color Back

[Scott Aslan (JIRA)]

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

Scott Aslan commented on NIFI-2603:
---

Peter,

Thanks for the screen shots depicting the changes you are proposing! I have 
done some analysis for this effort and it seems a bit more involved than just 
updating some CSS as we would probably want to conditionally show some color. I 
would say we should open this up for more discussion and welcome any other 
input pertaining to this. I'd be happy to pick this up but I think we need to 
ensure we are being consistent with the coloring throughout the app and as such 
I would say we should probably mark this for 1.1. 

> Bringing Some UI Color Back
> ---
>
> Key: NIFI-2603
> URL: https://issues.apache.org/jira/browse/NIFI-2603
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Peter Wicks
>Priority: Minor
>
> In the new 1.0 UI all of the colors associated with status (except the orange 
> triangle) are gone; replaced with a dark gray color.
> I propose bringing back color.  The screenshots are in the format of before 
> on the top and after on the bottom, except were labeled in the picture itself:
>  - Top Status Menu: https://goo.gl/photos/se1JnvhRwU7N4Fap7
>  - Process Group: https://goo.gl/photos/dqjG4KvC6xqxQfgT7
>  - Processes (Running/Stopped/Invalid): 
> https://goo.gl/photos/dSS8vgE2RkrXtc77A
>  - Operate Play/Stop buttons (only on mouse hover): 
> https://goo.gl/photos/Am5SUEEn7G9RjmMe6
>  - Processor/Processor Group Context Menu: 
> https://goo.gl/photos/Jq3qFg4ezaN91qms5
> This is not a "100% done, I've covered everything" before/after list.  I know 
> I need to do the NiFi summary page also at the minimum.



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

[jira] [Commented] (NIFI-2608) Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2608:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/930
  
Quick update... I was finally able to get a Kerberos environment setup and 
did a successful test with SASL, so that covers the 0.9.0 client against the 
0.9.0 broker, with PLAINTEXT, SSL, and SASL.

I'm planning to do the same tests with the 0.10 client and 0.10 broker 
tomorrow. 
So far things are looking good though!


> Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients
> ---
>
> Key: NIFI-2608
> URL: https://issues.apache.org/jira/browse/NIFI-2608
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Oleg Zhurakousky
>Assignee: Joseph Witt
>Priority: Critical
> Fix For: 1.0.0
>
>
> KafkaConsumer went fro thread-safe in 0.8 to not-thread-safe in 0.9 which was 
> overlooked while implementing new ConsumeKafka processor which relied on 0.9 
> Client API.



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

[GitHub] nifi issue #930: NIFI-2608 reworked consumer to match API. Added support for...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/930
  
Quick update... I was finally able to get a Kerberos environment setup and 
did a successful test with SASL, so that covers the 0.9.0 client against the 
0.9.0 broker, with PLAINTEXT, SSL, and SASL.

I'm planning to do the same tests with the 0.10 client and 0.10 broker 
tomorrow. 
So far things are looking good though!


---
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-2608) Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2608:
---

Some gremlin still lurking for the 0.10 client.  Working on it now.

{quote}
2016-08-24 22:14:14,499 ERROR [Timer-Driven Process Thread-10] 
o.a.n.p.kafka.pubsub.ConsumeKafka_0_10
org.apache.kafka.common.KafkaException: Failed to construct kafka consumer
at 
org.apache.kafka.clients.consumer.KafkaConsumer.(KafkaConsumer.java:702) 
~[na:na]
at 
org.apache.kafka.clients.consumer.KafkaConsumer.(KafkaConsumer.java:557) 
~[na:na]
at 
org.apache.kafka.clients.consumer.KafkaConsumer.(KafkaConsumer.java:540) 
~[na:na]
at 
org.apache.nifi.processors.kafka.pubsub.ConsumerPool.createKafkaConsumer(ConsumerPool.java:102)
 ~[na:na]
at 
org.apache.nifi.processors.kafka.pubsub.ConsumerPool.createConsumer(ConsumerPool.java:106)
 ~[na:na]
at 
org.apache.nifi.processors.kafka.pubsub.ConsumerPool.obtainConsumer(ConsumerPool.java:98)
 ~[na:na]
at 
org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10.onTrigger(ConsumeKafka_0_10.java:233)
 ~[na:na]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 ~[nifi-api-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1064)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_66]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_66]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_66]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_66]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_66]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_66]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_66]
Caused by: org.apache.kafka.common.KafkaException: 
org.apache.kafka.common.serialization.ByteArrayDeserializer is not an instance 
of org.apache.kafka.common.serialization.Deserializer
at 
org.apache.kafka.common.config.AbstractConfig.getConfiguredInstance(AbstractConfig.java:203)
 ~[na:na]
at 
org.apache.kafka.clients.consumer.KafkaConsumer.(KafkaConsumer.java:663) 
~[na:na]
... 18 common frames omitted
{quote}

> Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients
> ---
>
> Key: NIFI-2608
> URL: https://issues.apache.org/jira/browse/NIFI-2608
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Oleg Zhurakousky
>Assignee: Joseph Witt
>Priority: Critical
> Fix For: 1.0.0
>
>
> KafkaConsumer went fro thread-safe in 0.8 to not-thread-safe in 0.9 which was 
> overlooked while implementing new ConsumeKafka processor which relied on 0.9 
> Client API.



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

[jira] [Commented] (NIFI-2658) JS error when viewing bulletins that a user is not authorized to view

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2658:
--

GitHub user scottyaslan opened a pull request:

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

[NIFI-2658] Use bulletinEntity id instead of bulletin id since the i…

…ds match but bulletinEntities do not get bulletin objects if user is not 
authorized

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

$ git pull https://github.com/scottyaslan/nifi devBranch

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

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


commit abb349a62f26338b73db174e8004d60262138d0c
Author: Scott Aslan 
Date:   2016-08-25T02:59:28Z

[NIFI-2658] Use bulletinEntity id instead of bulleting id since the ids 
match but bulletinEntities do not get bulletin objects if user is not authorized




> JS error when viewing bulletins that a user is not authorized to view
> -
>
> Key: NIFI-2658
> URL: https://issues.apache.org/jira/browse/NIFI-2658
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>
> nf-bulletin-board.js?1.0.0-SNAPSHOT:391 Uncaught TypeError: Cannot read 
> property 'id' of undefined



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

[GitHub] nifi pull request #938: [NIFI-2658] Use bulletinEntity id instead of bulleti...

[scottyaslan]

GitHub user scottyaslan opened a pull request:

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

[NIFI-2658] Use bulletinEntity id instead of bulletin id since the i…

…ds match but bulletinEntities do not get bulletin objects if user is not 
authorized

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

$ git pull https://github.com/scottyaslan/nifi devBranch

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

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


commit abb349a62f26338b73db174e8004d60262138d0c
Author: Scott Aslan 
Date:   2016-08-25T02:59:28Z

[NIFI-2658] Use bulletinEntity id instead of bulleting id since the ids 
match but bulletinEntities do not get bulletin objects if user is not authorized




---
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-2658) JS error when viewing bulletins that a user is not authorized to view

[Scott Aslan (JIRA)]

Scott Aslan created NIFI-2658:
-

 Summary: JS error when viewing bulletins that a user is not 
authorized to view
 Key: NIFI-2658
 URL: https://issues.apache.org/jira/browse/NIFI-2658
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Scott Aslan
Assignee: Scott Aslan
 Fix For: 1.0.0


nf-bulletin-board.js?1.0.0-SNAPSHOT:391 Uncaught TypeError: Cannot read 
property 'id' of undefined



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

[jira] [Commented] (NIFI-2651) Remote Process Group does not stop immediately when using HTTP-based Site-to-Site

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2651:
--

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/937
  
@markap14 Thanks for catching this! I'm going to review this.


> Remote Process Group does not stop immediately when using HTTP-based 
> Site-to-Site
> -
>
> Key: NIFI-2651
> URL: https://issues.apache.org/jira/browse/NIFI-2651
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HTTP_Site-to-Site_with_Large_Data_Chunks.xml
>
>
> If we stop a Remote Process Group that is using the RAW Site-to-Site 
> protocol, it stops immediately, interrupting any transaction that is in 
> progress. If we stop a Remote Process Group that is using HTTP Site-to-Site 
> Protocol, though, the RPG waits until the current transactions have finished.



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

[GitHub] nifi issue #937: NIFI-2651: Ensure that when we disable transmission on an R...

[ijokarumawak]

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/937
  
@markap14 Thanks for catching this! I'm going to review this.


---
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-2635) REST API - Ensure phase two came from same user as phase one

[Joseph Percivall (JIRA)]

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

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

> REST API - Ensure phase two came from same user as phase one
> 
>
> Key: NIFI-2635
> URL: https://issues.apache.org/jira/browse/NIFI-2635
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Mutable requests are processed via a two phase commit. Need to ensure that 
> phase two comes from the same user as phase one.



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

[jira] [Updated] (NIFI-2633) REST API - Docs for request body missing for Start/Stop Process Group

[Joseph Percivall (JIRA)]

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

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

resolved via commit c2bfc4ef245d5c95dc103139cf386896d6ec3023

https://github.com/apache/nifi/commit/c2bfc4ef245d5c95dc103139cf386896d6ec3023

> REST API - Docs for request body missing for Start/Stop Process Group
> -
>
> Key: NIFI-2633
> URL: https://issues.apache.org/jira/browse/NIFI-2633
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> Need to ensure the documentation for the request body of the endpoint for 
> starting/stopping a Process Group is included.



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

[jira] [Commented] (NIFI-2635) REST API - Ensure phase two came from same user as phase one

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2635: - Re-using the original request during the second phase of the two 
phase commit. - Forwarding requests to the coordinator when received by a node.

This closes #933

Signed-off-by: jpercivall 


> REST API - Ensure phase two came from same user as phase one
> 
>
> Key: NIFI-2635
> URL: https://issues.apache.org/jira/browse/NIFI-2635
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Mutable requests are processed via a two phase commit. Need to ensure that 
> phase two comes from the same user as phase one.



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

[GitHub] nifi pull request #933: NiFi-2635 Cluster - Two phase commit

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #933: NiFi-2635 Cluster - Two phase commit

[JPercivall]

Github user JPercivall commented on the issue:

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

Visually verified the code (checked every PUT POST and DELETE that it used 
the new way method call) and did a contrib check build rebased to master. In a 
3 node secure cluster, I believe I tested every possible mutable request and 
all worked as expected. Also booted up a standealone instance to verify that 
still worked. Thanks @mcgilman, I will squash and merge.


---
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-2591) PutSQL has no handling for Binary data types

[Matt Burgess (JIRA)]

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

Matt Burgess updated NIFI-2591:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Resolved via Apache commit 1ad40c929dafa8bba0db314f1a5a83845d8cec4b, waiting 
for mirror into GitHub for closure of PR

> PutSQL has no handling for Binary data types
> 
>
> Key: NIFI-2591
> URL: https://issues.apache.org/jira/browse/NIFI-2591
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Peter Wicks
> Fix For: 1.0.0
>
>
> PutSQL does not call out binary types for any special treatment, so they end 
> up being routed through stmt.setObject.
> The problem is that upstream processors have formatted the binary data as a 
> string and the JDBC driver doesn't know what to do with a string going into a 
> binary field.
> Investigation into the AvroToJSON processor shows that if users are trying to 
> load data exported from a source system as Avro Binary that Avro encodes the 
> binary data into ASCII (One byte per character).



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

[jira] [Commented] (NIFI-2525) HTTP Site-to-Site fails with java.nio.channels.AsynchronousCloseException when sending through proxy that requires authentication

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2525:
--

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/915
  
@markap14 Thanks for reviewing the code! @YolandaMDavis Thanks for the 
functional test and detailed test result report!


> HTTP Site-to-Site fails with java.nio.channels.AsynchronousCloseException 
> when sending through proxy that requires authentication
> -
>
> Key: NIFI-2525
> URL: https://issues.apache.org/jira/browse/NIFI-2525
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Fix For: 1.0.0
>
>
> Pulling data using Remote Process Group from output port works.
> However, pushing data using Remote Process Group to input port fails with 
> AsynchronousCloseException.
> A RPG sends data via POST, then a proxy server returns 407: proxy auth 
> required. After this, the RPG should resend the request with credential, but 
> the data channel is already closed.
> Currently, it uses chunked encoding so that it can stream data to send. 
> Sending actual data twice won't be efficient. We need to do the 
> authentication before start reading flow-file stream.



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

[GitHub] nifi issue #915: NIFI-2525: Fix Proxy auth issue with async send.

[ijokarumawak]

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/915
  
@markap14 Thanks for reviewing the code! @YolandaMDavis Thanks for the 
functional test and detailed test result report!


---
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-2657) Allow auto-terminate missing relationships from context menu

[Andy LoPresto (JIRA)]

Andy LoPresto created NIFI-2657:
---

 Summary: Allow auto-terminate missing relationships from context 
menu
 Key: NIFI-2657
 URL: https://issues.apache.org/jira/browse/NIFI-2657
 Project: Apache NiFi
  Issue Type: New Feature
  Components: Core UI
Affects Versions: 1.0.0
Reporter: Andy LoPresto
Priority: Trivial


I don't know if this is an issue for anyone else, but my workflow often 
consists of:

* Add processor to workspace
* Configure properties of processor
* Close processor dialog
* Connect processor to destination
* _Note that processor state is still in error mode_
* Re-open processor properties
* Switch back from {{properties}} to {{settings}} tab
* Auto-terminate success/failure relationship as necessary

I think a processor context menu entry "Auto-terminate unconnected 
relationships" would be very useful. If people feel this could violate the 
Principle of Least Surprise, explicit entries for "... success relationship" 
and "... failure relationship" are also possibilities. 



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

[jira] [Commented] (NIFI-2608) Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2608:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/930
  
I've been reviewing this... so far I have tested ConsumeKafka and 
PublishKafka (0.9.0) against an Apache Kafka 0.9.0 broker, with PLAINTEXT and 
also with SSL, and both appear to be working well. Trying to setup a Kerberos 
scenario to test SASL.


> Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients
> ---
>
> Key: NIFI-2608
> URL: https://issues.apache.org/jira/browse/NIFI-2608
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Oleg Zhurakousky
>Assignee: Joseph Witt
>Priority: Critical
> Fix For: 1.0.0
>
>
> KafkaConsumer went fro thread-safe in 0.8 to not-thread-safe in 0.9 which was 
> overlooked while implementing new ConsumeKafka processor which relied on 0.9 
> Client API.



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

[GitHub] nifi issue #930: NIFI-2608 reworked consumer to match API. Added support for...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/930
  
I've been reviewing this... so far I have tested ConsumeKafka and 
PublishKafka (0.9.0) against an Apache Kafka 0.9.0 broker, with PLAINTEXT and 
also with SSL, and both appear to be working well. Trying to setup a Kerberos 
scenario to test SASL.


---
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-2656) Allow bootstrap process to prompt for password/key

[Andy LoPresto (JIRA)]

Andy LoPresto created NIFI-2656:
---

 Summary: Allow bootstrap process to prompt for password/key
 Key: NIFI-2656
 URL: https://issues.apache.org/jira/browse/NIFI-2656
 Project: Apache NiFi
  Issue Type: New Feature
  Components: Configuration, Core Framework
Affects Versions: 1.0.0
Reporter: Andy LoPresto
Priority: Minor


The bootstrap process {{RunNiFi.java}} is currently responsible for reading the 
key from {{bootstrap.conf}} and sending it to the running NiFi process 
{{NiFi.java}} to be used for sensitive property decryption. This exposes the 
key in two places:

* Plaintext in {{bootstrap.conf}}
* In the process invocation

Running the following command ({{ps -aef | grep -i nifi}}) will result in the 
following output:

{code}
...
  501 11597 11596   0  6:51PM ttys0010:08.55 
/Users/alopresto/.jenv/versions/1.8/bin/java -classpath 
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./conf:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/bcprov-jdk15on-1.54.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/commons-lang3-3.4.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/jcl-over-slf4j-1.7.12.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/jul-to-slf4j-1.7.12.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/log4j-over-slf4j-1.7.12.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/logback-classic-1.1.3.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/logback-core-1.1.3.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-api-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-documentation-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-framework-api-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-nar-utils-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-properties-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-properties-loader-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/nifi-runtime-1.0.0-SNAPSHOT.jar:/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./lib/slf4j-api-1.7.12.jar
 -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m 
-Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true 
-Djava.awt.headless=true -XX:+UseG1GC 
-Djava.protocol.handler.pkgs=sun.net.www.protocol 
-Dnifi.properties.file.path=/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/./conf/nifi.properties
 -Dnifi.bootstrap.listen.port=58213 -Dapp=NiFi 
-Dorg.apache.nifi.bootstrap.config.log.dir=/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.0.0-SNAPSHOT-bin/nifi-1.0.0-SNAPSHOT/logs
 org.apache.nifi.NiFi -k 
0123456789ABCDEFFEDCBA98765432100123456789ABCDEFFEDCBA9876543210
...
{code}

To allow for a more secure invocation, the NiFi process could pause and prompt 
for the password/key entry in a secure console if it is not provided in the 
invocation arguments from bootstrap (or if a special flag is provided). While 
this would require manual intervention to start the process, it would not be 
default behavior. 



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

[jira] [Updated] (NIFI-2608) Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2608:
--
Status: Patch Available  (was: In Progress)

> Align Consume Kafka with Kafka 0.9 unified API and support 0.10 clients
> ---
>
> Key: NIFI-2608
> URL: https://issues.apache.org/jira/browse/NIFI-2608
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Oleg Zhurakousky
>Assignee: Joseph Witt
>Priority: Critical
> Fix For: 1.0.0
>
>
> KafkaConsumer went fro thread-safe in 0.8 to not-thread-safe in 0.9 which was 
> overlooked while implementing new ConsumeKafka processor which relied on 0.9 
> Client API.



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

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

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2653:

Component/s: Tools and Build

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



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

[jira] [Updated] (NIFI-2644) Windows file permissions and line endings cause tests to fail

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2644:

Component/s: Configuration

> Windows file permissions and line endings cause tests to fail
> -
>
> Key: NIFI-2644
> URL: https://issues.apache.org/jira/browse/NIFI-2644
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Minor
> Fix For: 1.1.0
>
>
> The {{ConfigEncryptionToolTest}} has three tests which fail on Windows -- two 
> due to Windows not being able to modify the file permissions in order to 
> cause the expected {{IOException}} to be thrown, and one because the 
> serialized {{nifi.properties}} has different line endings than expected. 
> These are not blockers for 1.0.0 because they assert only failure scenarios 
> and will not impede the actual behavior of the tool. 
> We can re-investigate for 1.1.0. 
> {code}
> [INFO] Scanning for projects...
> [INFO] Inspecting build with total of 1 modules...
> [INFO] Installing Nexus Staging features:
> [INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
> nexus-staging-maven-plugin
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building nifi-toolkit-encrypt-config 1.0.0-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Deleting 
> C:\Users\Joe\AppData\Local\Programs\Git\nifi\nifi-toolkit\nifi-toolkit-encrypt-config\target
> [INFO] 
> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] 
> [INFO] --- build-helper-maven-plugin:1.5:add-source (add-source) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Source directory: 
> C:\Users\Joe\AppData\Local\Programs\Git\nifi\nifi-toolkit\nifi-toolkit-encrypt-config\src\main\groovy
>  added.
> [INFO] 
> [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] 
> [INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 6 source files to 
> C:\Users\Joe\AppData\Local\Programs\Git\nifi\nifi-toolkit\nifi-toolkit-encrypt-config\target\classes
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:compile (default) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
> [INFO] Found location 
> 
>  for className 
> [INFO] no javaAgentClass seems to be set
> [INFO] Compiling in a forked process using 
> C:\Users\Joe\.m2\repository\org\codehaus\groovy\groovy-eclipse-batch\2.4.3-01\groovy-eclipse-batch-2.4.3-01.jar
> [INFO] 
> [INFO] --- build-helper-maven-plugin:1.5:add-test-source (add-test-source) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Test Source directory: 
> C:\Users\Joe\AppData\Local\Programs\Git\nifi\nifi-toolkit\nifi-toolkit-encrypt-config\src\test\groovy
>  added.
> [INFO] 
> [INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 10 resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:testCompile (groovy-tests) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
> [INFO] Found location 
> 
>  for className 
> [INFO] no javaAgentClass seems to be set
> [INFO] Compiling in a forked process using 
> C:\Users\Joe\.m2\repository\org\codehaus\groovy\groovy-eclipse-batch\2.4.3-01\groovy-eclipse-batch-2.4.3-01.jar
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:testCompile (default) @ 
> 

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

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2652:

Component/s: Tools and Build

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



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

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

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-2654:

Component/s: Tools and Build

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



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

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

[Andy LoPresto (JIRA)]

Andy LoPresto created NIFI-2655:
---

 Summary: Encrypted config tool should handle absence of "-n" flag
 Key: NIFI-2655
 URL: https://issues.apache.org/jira/browse/NIFI-2655
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Configuration, Tools and Build
Affects Versions: 1.0.0
Reporter: Andy LoPresto
Priority: Minor


The {{encrypt-config}} tool will fail if the source {{-n nifi.properties}} flag 
is not present. However, it first looks for {{./conf/nifi.properties}} before 
failing. Either {{-n}} should be a required flag or a default 
{{nifi.properties}} template file should be populated within the tool. 



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

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

[Andy LoPresto (JIRA)]

Andy LoPresto created NIFI-2654:
---

 Summary: Encrypted configs should handle login identity provider 
configs
 Key: NIFI-2654
 URL: https://issues.apache.org/jira/browse/NIFI-2654
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Configuration
Affects Versions: 1.0.0
Reporter: Andy LoPresto


The encrypted configuration tool and internal logic to load unprotected values 
should handle sensitive values contained in the login identity providers (like 
LDAP Manager Password).



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

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

[Andy LoPresto (JIRA)]

Andy LoPresto created NIFI-2653:
---

 Summary: Encrypted configs should handle variable registry
 Key: NIFI-2653
 URL: https://issues.apache.org/jira/browse/NIFI-2653
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Configuration
Affects Versions: 1.0.0
Reporter: Andy LoPresto


The encrypted configuration tool and internal logic to load unprotected values 
should handle sensitive values contained in the variable registry (perhaps with 
a unique/derived key for external containers). 



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

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

[Andy LoPresto (JIRA)]

Andy LoPresto created NIFI-2652:
---

 Summary: Handle multiple invocations of the encrypt-config tool
 Key: NIFI-2652
 URL: https://issues.apache.org/jira/browse/NIFI-2652
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Configuration
Affects Versions: 1.0.0
Reporter: Andy LoPresto
Assignee: Andy LoPresto
 Fix For: 1.1.0


A discussion between [~jtstorck] and myself led to some possible scenarios with 
the {{encrypt-config}} tool. If a user invokes the tool multiple times on the 
same input files (updating in place), what should happen?

Currently:

The tool will not operate on any already-protected properties. So sensitive 
properties present and unprotected would be protected by the first invocation. 
If, before the second invocation, new sensitive values were provided in the 
{{nifi.properties}} file, they would be protected by the second invocation. If 
the user provides the same key/password as the first invocation, all properties 
would be encrypted with the same key. However, if a different key/password were 
used, the properties encrypted on the second invocation would be protected with 
a different key, and the new key would overwrite the key in the 
{{bootstrap.conf}} file, rendering the first set of properties unrecoverable. 

Possible solutions:

On invocation of the tool, it first tries to read the existing key from 
{{bootstrap.conf}}. If no key is present, operate as normal. 

* Possibly require second entry of the key/password for confirmation to ensure 
it was not mistyped

If a key *is* present (one of the following):

* (Derive if necessary and) validate the key against the existing key and if it 
does not match, fail to run
* Decrypt any existing encrypted properties with the persisted key and 
re-encrypt all sensitive properties with the new key

The second option does not require the same key/password to be used repeatedly 
and also provides a mechanism for key migration/rollover. 



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

[jira] [Commented] (NIFI-2591) PutSQL has no handling for Binary data types

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2591:
--

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/883
  
+1 LGTM, tested all the logic. Thanks for the great contribution! Merging 
to master


> PutSQL has no handling for Binary data types
> 
>
> Key: NIFI-2591
> URL: https://issues.apache.org/jira/browse/NIFI-2591
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Peter Wicks
> Fix For: 1.0.0
>
>
> PutSQL does not call out binary types for any special treatment, so they end 
> up being routed through stmt.setObject.
> The problem is that upstream processors have formatted the binary data as a 
> string and the JDBC driver doesn't know what to do with a string going into a 
> binary field.
> Investigation into the AvroToJSON processor shows that if users are trying to 
> load data exported from a source system as Avro Binary that Avro encodes the 
> binary data into ASCII (One byte per character).



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

[jira] [Updated] (NIFI-2591) PutSQL has no handling for Binary data types

[Matt Burgess (JIRA)]

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

Matt Burgess updated NIFI-2591:
---
Fix Version/s: 1.0.0

> PutSQL has no handling for Binary data types
> 
>
> Key: NIFI-2591
> URL: https://issues.apache.org/jira/browse/NIFI-2591
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Peter Wicks
> Fix For: 1.0.0
>
>
> PutSQL does not call out binary types for any special treatment, so they end 
> up being routed through stmt.setObject.
> The problem is that upstream processors have formatted the binary data as a 
> string and the JDBC driver doesn't know what to do with a string going into a 
> binary field.
> Investigation into the AvroToJSON processor shows that if users are trying to 
> load data exported from a source system as Avro Binary that Avro encodes the 
> binary data into ASCII (One byte per character).



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

[GitHub] nifi issue #883: NIFI-2591 - PutSQL has no handling for Binary data types

[mattyb149]

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/883
  
+1 LGTM, tested all the logic. Thanks for the great contribution! Merging 
to master


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

[jira] [Resolved] (NIFI-2650) nifi-toolkit-tls build fails when parallel with new local repo

[Joseph Percivall (JIRA)]

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

Joseph Percivall resolved NIFI-2650.

Resolution: Fixed
  Assignee: Bryan Rosander

> nifi-toolkit-tls build fails when parallel with new local repo
> --
>
> Key: NIFI-2650
> URL: https://issues.apache.org/jira/browse/NIFI-2650
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
> Fix For: 1.0.0
>
>
> If you remove your ~/.m2 folder and run a parallel build from the root, the 
> nifi-toolkit-tls build will run before nifi-resources has published its 
> artifact.  This results in a failed build.



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

[jira] [Commented] (NIFI-2650) nifi-toolkit-tls build fails when parallel with new local repo

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2650:
--

Github user asfgit closed the pull request at:

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


> nifi-toolkit-tls build fails when parallel with new local repo
> --
>
> Key: NIFI-2650
> URL: https://issues.apache.org/jira/browse/NIFI-2650
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Bryan Rosander
> Fix For: 1.0.0
>
>
> If you remove your ~/.m2 folder and run a parallel build from the root, the 
> nifi-toolkit-tls build will run before nifi-resources has published its 
> artifact.  This results in a failed build.



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

[jira] [Commented] (NIFI-2650) nifi-toolkit-tls build fails when parallel with new local repo

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2650 - Adding dependency on nifi-resources to match maven-dependency-plugin

This closes #936

Signed-off-by: jpercivall 


> nifi-toolkit-tls build fails when parallel with new local repo
> --
>
> Key: NIFI-2650
> URL: https://issues.apache.org/jira/browse/NIFI-2650
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Bryan Rosander
> Fix For: 1.0.0
>
>
> If you remove your ~/.m2 folder and run a parallel build from the root, the 
> nifi-toolkit-tls build will run before nifi-resources has published its 
> artifact.  This results in a failed build.



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

[GitHub] nifi pull request #936: NIFI-2650 - Adding dependency on nifi-resources to m...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #936: NIFI-2650 - Adding dependency on nifi-resources to match ma...

[JPercivall]

Github user JPercivall commented on the issue:

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

Visually verified change and did a concurrent contrib check build after 
wiping my m2 repo, which worked as expected. Thanks @brosander I will merge it 
in.


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

[jira] [Updated] (NIFI-2651) Remote Process Group does not stop immediately when using HTTP-based Site-to-Site

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2651:
-
Status: Patch Available  (was: Open)

> Remote Process Group does not stop immediately when using HTTP-based 
> Site-to-Site
> -
>
> Key: NIFI-2651
> URL: https://issues.apache.org/jira/browse/NIFI-2651
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HTTP_Site-to-Site_with_Large_Data_Chunks.xml
>
>
> If we stop a Remote Process Group that is using the RAW Site-to-Site 
> protocol, it stops immediately, interrupting any transaction that is in 
> progress. If we stop a Remote Process Group that is using HTTP Site-to-Site 
> Protocol, though, the RPG waits until the current transactions have finished.



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

[jira] [Commented] (NIFI-2651) Remote Process Group does not stop immediately when using HTTP-based Site-to-Site

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2651:
--

GitHub user markap14 opened a pull request:

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

NIFI-2651: Ensure that when we disable transmission on an RPG that we…

… interrupt any transactions in progress for http-based site-to-site

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

$ git pull https://github.com/markap14/nifi NIFI-2651

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

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


commit 8f103d7c6e37c4ed1b4726ecd867a89aa9c29405
Author: Mark Payne 
Date:   2016-08-25T01:06:30Z

NIFI-2651: Ensure that when we disable transmission on an RPG that we 
interrupt any transactions in progress for http-based site-to-site




> Remote Process Group does not stop immediately when using HTTP-based 
> Site-to-Site
> -
>
> Key: NIFI-2651
> URL: https://issues.apache.org/jira/browse/NIFI-2651
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HTTP_Site-to-Site_with_Large_Data_Chunks.xml
>
>
> If we stop a Remote Process Group that is using the RAW Site-to-Site 
> protocol, it stops immediately, interrupting any transaction that is in 
> progress. If we stop a Remote Process Group that is using HTTP Site-to-Site 
> Protocol, though, the RPG waits until the current transactions have finished.



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

[GitHub] nifi pull request #937: NIFI-2651: Ensure that when we disable transmission ...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-2651: Ensure that when we disable transmission on an RPG that we…

… interrupt any transactions in progress for http-based site-to-site

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

$ git pull https://github.com/markap14/nifi NIFI-2651

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

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


commit 8f103d7c6e37c4ed1b4726ecd867a89aa9c29405
Author: Mark Payne 
Date:   2016-08-25T01:06:30Z

NIFI-2651: Ensure that when we disable transmission on an RPG that we 
interrupt any transactions in progress for http-based site-to-site




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

[GitHub] nifi issue #936: NIFI-2650 - Adding dependency on nifi-resources to match ma...

[JPercivall]

Github user JPercivall commented on the issue:

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


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

[jira] [Commented] (NIFI-2651) Remote Process Group does not stop immediately when using HTTP-based Site-to-Site

[Mark Payne (JIRA)]

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

Mark Payne commented on NIFI-2651:
--

The attached template should help to expose/replicate the issue. It generates a 
lot of large FlowFiles and sends them back to the same cluster. If we right 
click on the Remote Process Group and then click Disable Transmission, it 
should stop immediately but does not.

> Remote Process Group does not stop immediately when using HTTP-based 
> Site-to-Site
> -
>
> Key: NIFI-2651
> URL: https://issues.apache.org/jira/browse/NIFI-2651
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HTTP_Site-to-Site_with_Large_Data_Chunks.xml
>
>
> If we stop a Remote Process Group that is using the RAW Site-to-Site 
> protocol, it stops immediately, interrupting any transaction that is in 
> progress. If we stop a Remote Process Group that is using HTTP Site-to-Site 
> Protocol, though, the RPG waits until the current transactions have finished.



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

[jira] [Updated] (NIFI-2651) Remote Process Group does not stop immediately when using HTTP-based Site-to-Site

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2651:
-
Attachment: HTTP_Site-to-Site_with_Large_Data_Chunks.xml

> Remote Process Group does not stop immediately when using HTTP-based 
> Site-to-Site
> -
>
> Key: NIFI-2651
> URL: https://issues.apache.org/jira/browse/NIFI-2651
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
> Attachments: HTTP_Site-to-Site_with_Large_Data_Chunks.xml
>
>
> If we stop a Remote Process Group that is using the RAW Site-to-Site 
> protocol, it stops immediately, interrupting any transaction that is in 
> progress. If we stop a Remote Process Group that is using HTTP Site-to-Site 
> Protocol, though, the RPG waits until the current transactions have finished.



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

[jira] [Commented] (NIFI-2299) Add standard services API dependency to Scripting Processors

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2299:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/753
  
It is in there.  https://issues.apache.org/jira/browse/NIFI-2299
You should be all set to do fun things.


> Add standard services API dependency to Scripting Processors   
> ---
>
> Key: NIFI-2299
> URL: https://issues.apache.org/jira/browse/NIFI-2299
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0, 0.6.1
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: Scripts, groovy
> Fix For: 1.0.0
>
>
> Scripting Processors cannot used Controller Services such as 
> *DistributedMapCacheClientService* etc, as required dependencies are missing 
> for *ExecuteScript* Nar. By adding following dependencies we can open new 
> possibilities for Scripting Processors.  
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-nar/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-standard-services-api-nar
> nar
> 
> {code}
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-processors/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-distributed-cache-client-service-api
> 
> {code}
> Then we can create scripting processor like:
> {code}
> import org.apache.nifi.controller.ControllerService
> import com.crossbusiness.nifi.processors.StringSerDe
> final StringSerDe stringSerDe = new StringSerDe();
> def lookup = context.controllerServiceLookup
> def cacheServiceName = DistributedMapCacheClientServiceName.value
> log.error  "cacheServiceName: ${cacheServiceName}"
> def cacheServiceId = 
> lookup.getControllerServiceIdentifiers(ControllerService).find {
> cs -> lookup.getControllerServiceName(cs) == cacheServiceName
> }
> log.error  "cacheServiceId:  ${cacheServiceId}"
> def cache = lookup.getControllerService(cacheServiceId)
> log.error cache.get("aaa", stringSerDe, stringSerDe )
> {code}



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

[GitHub] nifi issue #753: NIFI-2299 Add standard services api access for scripting pr...

[joewitt]

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/753
  
It is in there.  https://issues.apache.org/jira/browse/NIFI-2299
You should be all set to do fun things.


---
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-2650) nifi-toolkit-tls build fails when parallel with new local repo

[Bryan Rosander (JIRA)]

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

Bryan Rosander updated NIFI-2650:
-
Fix Version/s: 1.0.0

> nifi-toolkit-tls build fails when parallel with new local repo
> --
>
> Key: NIFI-2650
> URL: https://issues.apache.org/jira/browse/NIFI-2650
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Bryan Rosander
> Fix For: 1.0.0
>
>
> If you remove your ~/.m2 folder and run a parallel build from the root, the 
> nifi-toolkit-tls build will run before nifi-resources has published its 
> artifact.  This results in a failed build.



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

[GitHub] nifi issue #753: NIFI-2299 Add standard services api access for scripting pr...

[xmlking]

Github user xmlking commented on the issue:

https://github.com/apache/nifi/pull/753
  
 @joewitt wonder if this PR will be included in final V1.0.0   ?
Thanks 
Sumo


---
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-2299) Add standard services API dependency to Scripting Processors

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2299:
--

Github user xmlking commented on the issue:

https://github.com/apache/nifi/pull/753
  
 @joewitt wonder if this PR will be included in final V1.0.0   ?
Thanks 
Sumo


> Add standard services API dependency to Scripting Processors   
> ---
>
> Key: NIFI-2299
> URL: https://issues.apache.org/jira/browse/NIFI-2299
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0, 0.6.1
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: Scripts, groovy
> Fix For: 1.0.0
>
>
> Scripting Processors cannot used Controller Services such as 
> *DistributedMapCacheClientService* etc, as required dependencies are missing 
> for *ExecuteScript* Nar. By adding following dependencies we can open new 
> possibilities for Scripting Processors.  
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-nar/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-standard-services-api-nar
> nar
> 
> {code}
> Add this dependency to 
> nifi/nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-processors/pom.xml
> {code}
> 
> org.apache.nifi
> nifi-distributed-cache-client-service-api
> 
> {code}
> Then we can create scripting processor like:
> {code}
> import org.apache.nifi.controller.ControllerService
> import com.crossbusiness.nifi.processors.StringSerDe
> final StringSerDe stringSerDe = new StringSerDe();
> def lookup = context.controllerServiceLookup
> def cacheServiceName = DistributedMapCacheClientServiceName.value
> log.error  "cacheServiceName: ${cacheServiceName}"
> def cacheServiceId = 
> lookup.getControllerServiceIdentifiers(ControllerService).find {
> cs -> lookup.getControllerServiceName(cs) == cacheServiceName
> }
> log.error  "cacheServiceId:  ${cacheServiceId}"
> def cache = lookup.getControllerService(cacheServiceId)
> log.error cache.get("aaa", stringSerDe, stringSerDe )
> {code}



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

[jira] [Updated] (NIFI-2525) HTTP Site-to-Site fails with java.nio.channels.AsynchronousCloseException when sending through proxy that requires authentication

[Yolanda M. Davis (JIRA)]

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

Yolanda M. Davis updated NIFI-2525:
---
Resolution: Resolved
  Assignee: Koji Kawamura
Status: Resolved  (was: Patch Available)

> HTTP Site-to-Site fails with java.nio.channels.AsynchronousCloseException 
> when sending through proxy that requires authentication
> -
>
> Key: NIFI-2525
> URL: https://issues.apache.org/jira/browse/NIFI-2525
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Fix For: 1.0.0
>
>
> Pulling data using Remote Process Group from output port works.
> However, pushing data using Remote Process Group to input port fails with 
> AsynchronousCloseException.
> A RPG sends data via POST, then a proxy server returns 407: proxy auth 
> required. After this, the RPG should resend the request with credential, but 
> the data channel is already closed.
> Currently, it uses chunked encoding so that it can stream data to send. 
> Sending actual data twice won't be efficient. We need to do the 
> authentication before start reading flow-file stream.



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

[jira] [Commented] (NIFI-2525) HTTP Site-to-Site fails with java.nio.channels.AsynchronousCloseException when sending through proxy that requires authentication

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2525:
--

Github user asfgit closed the pull request at:

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


> HTTP Site-to-Site fails with java.nio.channels.AsynchronousCloseException 
> when sending through proxy that requires authentication
> -
>
> Key: NIFI-2525
> URL: https://issues.apache.org/jira/browse/NIFI-2525
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
> Fix For: 1.0.0
>
>
> Pulling data using Remote Process Group from output port works.
> However, pushing data using Remote Process Group to input port fails with 
> AsynchronousCloseException.
> A RPG sends data via POST, then a proxy server returns 407: proxy auth 
> required. After this, the RPG should resend the request with credential, but 
> the data channel is already closed.
> Currently, it uses chunked encoding so that it can stream data to send. 
> Sending actual data twice won't be efficient. We need to do the 
> authentication before start reading flow-file stream.



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

[jira] [Updated] (NIFI-2650) nifi-toolkit-tls build fails when parallel with new local repo

[Bryan Rosander (JIRA)]

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

Bryan Rosander updated NIFI-2650:
-
Affects Version/s: 1.0.0

> nifi-toolkit-tls build fails when parallel with new local repo
> --
>
> Key: NIFI-2650
> URL: https://issues.apache.org/jira/browse/NIFI-2650
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Bryan Rosander
>
> If you remove your ~/.m2 folder and run a parallel build from the root, the 
> nifi-toolkit-tls build will run before nifi-resources has published its 
> artifact.  This results in a failed build.



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

[jira] [Updated] (NIFI-2650) nifi-toolkit-tls build fails when parallel with new local repo

[Bryan Rosander (JIRA)]

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

Bryan Rosander updated NIFI-2650:
-
Component/s: Tools and Build

> nifi-toolkit-tls build fails when parallel with new local repo
> --
>
> Key: NIFI-2650
> URL: https://issues.apache.org/jira/browse/NIFI-2650
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Bryan Rosander
>
> If you remove your ~/.m2 folder and run a parallel build from the root, the 
> nifi-toolkit-tls build will run before nifi-resources has published its 
> artifact.  This results in a failed build.



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

[GitHub] nifi pull request #915: NIFI-2525: Fix Proxy auth issue with async send.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2525) HTTP Site-to-Site fails with java.nio.channels.AsynchronousCloseException when sending through proxy that requires authentication

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2525: Fix Proxy auth issue with async send.

Without this fix, NiFi fails to send data via HTTP Site-to-Site through
Proxy which requires authentication due to AsynchronousCloseException.
It happens when async client replays producing contents in order to re-send the
request with auth credential for the proxy server, however the
connection is already closed.
This fix makes NiFi to send actual data only at the second round of requests, 
so that flow-file
contents can be sent without reading it twice.

Signed-off-by: Yolanda M. Davis 

This closes #915


> HTTP Site-to-Site fails with java.nio.channels.AsynchronousCloseException 
> when sending through proxy that requires authentication
> -
>
> Key: NIFI-2525
> URL: https://issues.apache.org/jira/browse/NIFI-2525
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
> Fix For: 1.0.0
>
>
> Pulling data using Remote Process Group from output port works.
> However, pushing data using Remote Process Group to input port fails with 
> AsynchronousCloseException.
> A RPG sends data via POST, then a proxy server returns 407: proxy auth 
> required. After this, the RPG should resend the request with credential, but 
> the data channel is already closed.
> Currently, it uses chunked encoding so that it can stream data to send. 
> Sending actual data twice won't be efficient. We need to do the 
> authentication before start reading flow-file stream.



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

[jira] [Commented] (NIFI-2650) nifi-toolkit-tls build fails when parallel with new local repo

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2650:
--

GitHub user brosander opened a pull request:

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

NIFI-2650 - Adding dependency on nifi-resources to match maven-depend…

…ency-plugin

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

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

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

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


commit dd96dadea54bd4d49c50ffca1006e698a986483a
Author: Bryan Rosander 
Date:   2016-08-25T00:29:13Z

NIFI-2650 - Adding dependency on nifi-resources to match 
maven-dependency-plugin




> nifi-toolkit-tls build fails when parallel with new local repo
> --
>
> Key: NIFI-2650
> URL: https://issues.apache.org/jira/browse/NIFI-2650
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Rosander
>
> If you remove your ~/.m2 folder and run a parallel build from the root, the 
> nifi-toolkit-tls build will run before nifi-resources has published its 
> artifact.  This results in a failed build.



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

[GitHub] nifi pull request #936: NIFI-2650 - Adding dependency on nifi-resources to m...

[brosander]

GitHub user brosander opened a pull request:

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

NIFI-2650 - Adding dependency on nifi-resources to match maven-depend…

…ency-plugin

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

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

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

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


commit dd96dadea54bd4d49c50ffca1006e698a986483a
Author: Bryan Rosander 
Date:   2016-08-25T00:29:13Z

NIFI-2650 - Adding dependency on nifi-resources to match 
maven-dependency-plugin




---
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-2651) Remote Process Group does not stop immediately when using HTTP-based Site-to-Site

[Mark Payne (JIRA)]

Mark Payne created NIFI-2651:


 Summary: Remote Process Group does not stop immediately when using 
HTTP-based Site-to-Site
 Key: NIFI-2651
 URL: https://issues.apache.org/jira/browse/NIFI-2651
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Mark Payne
Assignee: Mark Payne
Priority: Critical
 Fix For: 1.0.0


If we stop a Remote Process Group that is using the RAW Site-to-Site protocol, 
it stops immediately, interrupting any transaction that is in progress. If we 
stop a Remote Process Group that is using HTTP Site-to-Site Protocol, though, 
the RPG waits until the current transactions have finished.



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

[GitHub] nifi-minifi-cpp pull request #9: Minifi 87

[benqiu2016]

GitHub user benqiu2016 opened a pull request:

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

Minifi 87

add MiNiFi start/stop script

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

$ git pull https://github.com/benqiu2016/nifi-minifi-cpp MINIFI-87

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

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


commit 34cc473f478c3ffe3e5dc236ed4b233779a09139
Author: Bin Qiu 
Date:   2016-08-20T18:11:43Z

MINFI-85: Add ListenSyslog processor

commit 29e6793821b49d355ff5b43ebe5080f86df746d3
Author: Bin Qiu 
Date:   2016-08-24T15:33:47Z

add MiNiFi start/stop 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] [Created] (NIFI-2650) nifi-toolkit-tls build fails when parallel with new local repo

[Bryan Rosander (JIRA)]

Bryan Rosander created NIFI-2650:


 Summary: nifi-toolkit-tls build fails when parallel with new local 
repo
 Key: NIFI-2650
 URL: https://issues.apache.org/jira/browse/NIFI-2650
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Bryan Rosander


If you remove your ~/.m2 folder and run a parallel build from the root, the 
nifi-toolkit-tls build will run before nifi-resources has published its 
artifact.  This results in a failed build.



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

[jira] [Created] (NIFI-2649) Controller Services need to be refreshed when creating one inline from a Reporting Task

[Jeff Storck (JIRA)]

Jeff Storck created NIFI-2649:
-

 Summary: Controller Services need to be refreshed when creating 
one inline from a Reporting Task
 Key: NIFI-2649
 URL: https://issues.apache.org/jira/browse/NIFI-2649
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Reporter: Jeff Storck
Priority: Minor
 Fix For: 1.1.0


When configuring a Reporting Task such as SiteToSiteProvenanceReportingTask, 
after creating a new SSLContextService inline in the property editor, if the 
user hits the cancel button on the reporting tasks properties dialog, and then 
clicks on the ControllerServices tab, the controller service isn't listed.  
Hitting refresh manually reveals the newly-created controller service, or 
closing the NiFi Settings dialog and reopening it also reveals the new 
controller service.



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

[GitHub] nifi issue #915: NIFI-2525: Fix Proxy auth issue with async send.

[YolandaMDavis]

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/915
  
I setup 2 standalone nifi instances on separate hosts and created a 3rd 
host to serve as proxy server using Apache Web.  NiFi server A was set as the 
push server which generated 10MB Flow Files every 10 seconds. Server A referred 
to server B via a RPG. Server B received input flowfiles and saved them to disk 
via PutFile.  The following test configurations were performed:

1) Unsecured NiFi instances with no Proxy  - Data was exchanged and saved 
on Server B as expected
2) Unsecured NiFi instance with Proxy (Basic/Digest Auth) - when attempting 
to post via Proxy on Server B endpoint nifi-api/data-transfer/input-ports, 
proxy logged connection attempt with Status 407 415 (authentication required, 
post method).  Proxy logged subsequent responses of 201 or 202 for these 
attempts.  For deletes, 407/415  were logged and subsequent 200 was received 
(OK). No exception seen in log on either server. Data exchange completed 
successfully
4) Secured NiFi Instances with no Proxy - After required policy updates in 
NiFi data was exchanged and performed as expected
5)  Secured NiFi Instances with Proxy (Basic/Digest Auth) - Results same as 
test #2 however proxy logs did not detail resource endpoints accessed (I 
believe due to SSL enabled)
6) Secured NiFi  instances with Proxy (No User/Pass Provided) - NiFi logged 
error indicating :  Unable to refresh Remote Group's peers due to response code 
407:Proxy Authentication Required with explanation: null.  Error Message was 
expected and resolved once user/pass provided for proxy.

Given the above tests I believe that proxy authentication is working as 
expected with this patch

+1

Will merge into master shortly





---
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-2525) HTTP Site-to-Site fails with java.nio.channels.AsynchronousCloseException when sending through proxy that requires authentication

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2525:
--

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/915
  
I setup 2 standalone nifi instances on separate hosts and created a 3rd 
host to serve as proxy server using Apache Web.  NiFi server A was set as the 
push server which generated 10MB Flow Files every 10 seconds. Server A referred 
to server B via a RPG. Server B received input flowfiles and saved them to disk 
via PutFile.  The following test configurations were performed:

1) Unsecured NiFi instances with no Proxy  - Data was exchanged and saved 
on Server B as expected
2) Unsecured NiFi instance with Proxy (Basic/Digest Auth) - when attempting 
to post via Proxy on Server B endpoint nifi-api/data-transfer/input-ports, 
proxy logged connection attempt with Status 407 415 (authentication required, 
post method).  Proxy logged subsequent responses of 201 or 202 for these 
attempts.  For deletes, 407/415  were logged and subsequent 200 was received 
(OK). No exception seen in log on either server. Data exchange completed 
successfully
4) Secured NiFi Instances with no Proxy - After required policy updates in 
NiFi data was exchanged and performed as expected
5)  Secured NiFi Instances with Proxy (Basic/Digest Auth) - Results same as 
test #2 however proxy logs did not detail resource endpoints accessed (I 
believe due to SSL enabled)
6) Secured NiFi  instances with Proxy (No User/Pass Provided) - NiFi logged 
error indicating :  Unable to refresh Remote Group's peers due to response code 
407:Proxy Authentication Required with explanation: null.  Error Message was 
expected and resolved once user/pass provided for proxy.

Given the above tests I believe that proxy authentication is working as 
expected with this patch

+1

Will merge into master shortly





> HTTP Site-to-Site fails with java.nio.channels.AsynchronousCloseException 
> when sending through proxy that requires authentication
> -
>
> Key: NIFI-2525
> URL: https://issues.apache.org/jira/browse/NIFI-2525
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
> Fix For: 1.0.0
>
>
> Pulling data using Remote Process Group from output port works.
> However, pushing data using Remote Process Group to input port fails with 
> AsynchronousCloseException.
> A RPG sends data via POST, then a proxy server returns 407: proxy auth 
> required. After this, the RPG should resend the request with credential, but 
> the data channel is already closed.
> Currently, it uses chunked encoding so that it can stream data to send. 
> Sending actual data twice won't be efficient. We need to do the 
> authentication before start reading flow-file stream.



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

[jira] [Commented] (NIFI-2591) PutSQL has no handling for Binary data types

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2591:
--

Github user patricker commented on the issue:

https://github.com/apache/nifi/pull/883
  
Did you need me to change something still, or are you doing more testing?


> PutSQL has no handling for Binary data types
> 
>
> Key: NIFI-2591
> URL: https://issues.apache.org/jira/browse/NIFI-2591
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Peter Wicks
>
> PutSQL does not call out binary types for any special treatment, so they end 
> up being routed through stmt.setObject.
> The problem is that upstream processors have formatted the binary data as a 
> string and the JDBC driver doesn't know what to do with a string going into a 
> binary field.
> Investigation into the AvroToJSON processor shows that if users are trying to 
> load data exported from a source system as Avro Binary that Avro encodes the 
> binary data into ASCII (One byte per character).



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

[GitHub] nifi issue #883: NIFI-2591 - PutSQL has no handling for Binary data types

[patricker]

Github user patricker commented on the issue:

https://github.com/apache/nifi/pull/883
  
Did you need me to change something still, or are you doing more testing?


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

[GitHub] nifi issue #933: NiFi-2635 Cluster - Two phase commit

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/933
  
Thanks.. just pushed an updated that should address the contrib check 
issues.


---
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 #933: NiFi-2635 Cluster - Two phase commit

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/933
  
I encountered some checkstyle violations building this:

```
[INFO] --- maven-checkstyle-plugin:2.15:check (check-style) @ nifi-web-api 
---
[WARNING] 
src/main/java/org/apache/nifi/web/api/ApplicationResource.java[919:9] 
(whitespace) FileTabCharacter: Line contains a tab character.
[WARNING] 
src/main/java/org/apache/nifi/web/api/ControllerResource.java[351] (sizes) 
LineLength: Line is longer than 200 characters (found 204).
[WARNING] 
src/main/java/org/apache/nifi/web/api/ProcessGroupResource.java[1315] (sizes) 
LineLength: Line is longer than 200 characters (found 207).
[WARNING] 
src/main/java/org/apache/nifi/web/api/ProcessGroupResource.java[2103] (sizes) 
LineLength: Line is longer than 200 characters (found 204).
```


---
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-2647) Dirty state of Controller Service and Reporting Task configs not being kept correctly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2647:
--

Github user asfgit closed the pull request at:

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


> Dirty state of Controller Service and Reporting Task configs not being kept 
> correctly
> -
>
> Key: NIFI-2647
> URL: https://issues.apache.org/jira/browse/NIFI-2647
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Jeff Storck
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> When opening the configuration for a controller service or reporting task 
> that uses a controller service reference, clicking on the "go to" arrow 
> widget to go to the referenced controller service results in the user being 
> asked if it should save first, regardless of the dirty state of the 
> configuration.



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

[GitHub] nifi pull request #935: UI - Fixing check to determine if save is required

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2647) Dirty state of Controller Service and Reporting Task configs not being kept correctly

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2647:
- Referencing correct components when checking if save is required.

This closes #935.

Signed-off-by: Andy LoPresto 


> Dirty state of Controller Service and Reporting Task configs not being kept 
> correctly
> -
>
> Key: NIFI-2647
> URL: https://issues.apache.org/jira/browse/NIFI-2647
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Jeff Storck
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> When opening the configuration for a controller service or reporting task 
> that uses a controller service reference, clicking on the "go to" arrow 
> widget to go to the referenced controller service results in the user being 
> asked if it should save first, regardless of the dirty state of the 
> configuration.



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

[GitHub] nifi issue #935: UI - Fixing check to determine if save is required

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/935
  
Merging...


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

[GitHub] nifi issue #935: UI - Fixing check to determine if save is required

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/935
  
Ran and verified the dialog no longer prompts to save when no changes have 
been made to the processor properties. +1. 


---
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-2635) REST API - Ensure phase two came from same user as phase one

[Joseph Percivall (JIRA)]

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

Joseph Percivall commented on NIFI-2635:


There was a PR opened but didn't automatically get linked it can be found here:

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

> REST API - Ensure phase two came from same user as phase one
> 
>
> Key: NIFI-2635
> URL: https://issues.apache.org/jira/browse/NIFI-2635
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Mutable requests are processed via a two phase commit. Need to ensure that 
> phase two comes from the same user as phase one.



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

[GitHub] nifi-minifi-cpp pull request #8: MINIFI-63 - Provide service enablement for ...

[apiri]

GitHub user apiri opened a pull request:

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

MINIFI-63 - Provide service enablement for MiNiFi C++

Restructure Makefile to generate binary assembly.  Create base minifi.sh 
script which serves as a wrapper around the minifi binary and provides 
installation as a service.

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

$ git pull https://github.com/apiri/nifi-minifi-cpp MINIFI-63

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

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


commit 0088451dc02320da731b8948acc62277e5cbf95e
Author: Aldrin Piri 
Date:   2016-07-22T17:19:32Z

MINIFI-63 - Restructure Makefile to generate binary assembly.  Create base 
minifi.sh script which serves as a wrapper around the minifi binary and 
provides installation as a service.




---
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 #934: NIFI-2648 Edit formatting of TLS toolkit section of ...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[jira] [Resolved] (NIFI-2648) Edit formatting of TLS toolkit section of Admin guide for improved readability and consistency

[Andy LoPresto (JIRA)]

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

Andy LoPresto resolved NIFI-2648.
-
Resolution: Fixed

> Edit formatting of TLS toolkit section of Admin guide for improved 
> readability and consistency
> --
>
> Key: NIFI-2648
> URL: https://issues.apache.org/jira/browse/NIFI-2648
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.0.0
>
>
> Encrypt-config tool was added to Admin guide per NIFI-2451.  The formatting 
> there should also be applied to the TLS-toolkit utility for consistency.  The 
> formatting also improves readability.



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

[jira] [Commented] (NIFI-2648) Edit formatting of TLS toolkit section of Admin guide for improved readability and consistency

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2648 Edit formatting of TLS toolkit section of Admin guide for improved 
readability and consistency

This closes #934.

Signed-off-by: Andy LoPresto 


> Edit formatting of TLS toolkit section of Admin guide for improved 
> readability and consistency
> --
>
> Key: NIFI-2648
> URL: https://issues.apache.org/jira/browse/NIFI-2648
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.0.0
>
>
> Encrypt-config tool was added to Admin guide per NIFI-2451.  The formatting 
> there should also be applied to the TLS-toolkit utility for consistency.  The 
> formatting also improves readability.



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

[jira] [Commented] (NIFI-2648) Edit formatting of TLS toolkit section of Admin guide for improved readability and consistency

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2648:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/934
  
+1, merging. 


> Edit formatting of TLS toolkit section of Admin guide for improved 
> readability and consistency
> --
>
> Key: NIFI-2648
> URL: https://issues.apache.org/jira/browse/NIFI-2648
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.0.0
>
>
> Encrypt-config tool was added to Admin guide per NIFI-2451.  The formatting 
> there should also be applied to the TLS-toolkit utility for consistency.  The 
> formatting also improves readability.



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

[GitHub] nifi issue #934: NIFI-2648 Edit formatting of TLS toolkit section of Admin g...

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/934
  
+1, merging. 


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

[jira] [Updated] (NIFI-2459) HTTP Site-to-Site can't update remote peer topology if the "bootstrap url" node is down

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2459:
-
Assignee: Koji Kawamura

> HTTP Site-to-Site can't update remote peer topology if the "bootstrap url" 
> node is down
> ---
>
> Key: NIFI-2459
> URL: https://issues.apache.org/jira/browse/NIFI-2459
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Fix For: 1.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> To establish a Site-to-Site protocol, a client NiFi uses the remote NiFi API 
> url that is specified as 'URL' at the creation of a Remote Process Group 
> (let's call it as 'bootstrap url').
> Currently, HTTP Site-to-Site keeps using the same 'bootstrap url', even if 
> the remote node goes down. If the bootstrap node went down, Site-to-Site data 
> transfer will keep working, but it can't update remote peer topology.
> RAW socket version cares about this scenario by asking updated peer 
> information with every nodes that it has connected before, until it gets a 
> successful response.
> HTTP version should follow how RAW version handles this.



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

[jira] [Commented] (NIFI-2459) HTTP Site-to-Site can't update remote peer topology if the "bootstrap url" node is down

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2459:
--

Github user asfgit closed the pull request at:

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


> HTTP Site-to-Site can't update remote peer topology if the "bootstrap url" 
> node is down
> ---
>
> Key: NIFI-2459
> URL: https://issues.apache.org/jira/browse/NIFI-2459
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
> Fix For: 1.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> To establish a Site-to-Site protocol, a client NiFi uses the remote NiFi API 
> url that is specified as 'URL' at the creation of a Remote Process Group 
> (let's call it as 'bootstrap url').
> Currently, HTTP Site-to-Site keeps using the same 'bootstrap url', even if 
> the remote node goes down. If the bootstrap node went down, Site-to-Site data 
> transfer will keep working, but it can't update remote peer topology.
> RAW socket version cares about this scenario by asking updated peer 
> information with every nodes that it has connected before, until it gets a 
> successful response.
> HTTP version should follow how RAW version handles this.



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

[jira] [Commented] (NIFI-2459) HTTP Site-to-Site can't update remote peer topology if the "bootstrap url" node is down

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2459:
--

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/927
  
Looks good. Was able to verify the behavior and the results were exactly as 
expected! A big thanks for tackling this! +1 merged to master.


> HTTP Site-to-Site can't update remote peer topology if the "bootstrap url" 
> node is down
> ---
>
> Key: NIFI-2459
> URL: https://issues.apache.org/jira/browse/NIFI-2459
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
> Fix For: 1.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> To establish a Site-to-Site protocol, a client NiFi uses the remote NiFi API 
> url that is specified as 'URL' at the creation of a Remote Process Group 
> (let's call it as 'bootstrap url').
> Currently, HTTP Site-to-Site keeps using the same 'bootstrap url', even if 
> the remote node goes down. If the bootstrap node went down, Site-to-Site data 
> transfer will keep working, but it can't update remote peer topology.
> RAW socket version cares about this scenario by asking updated peer 
> information with every nodes that it has connected before, until it gets a 
> successful response.
> HTTP version should follow how RAW version handles this.



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

[GitHub] nifi issue #927: NIFI-2459: HTTP Site-to-Site can't update remote peer topol...

[markap14]

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/927
  
Looks good. Was able to verify the behavior and the results were exactly as 
expected! A big thanks for tackling this! +1 merged to master.


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

[GitHub] nifi pull request #927: NIFI-2459: HTTP Site-to-Site can't update remote pee...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2640) Fix Windows command-line utility for encrypted configuration files

[Joseph Percivall (JIRA)]

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

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

> Fix Windows command-line utility for encrypted configuration files
> --
>
> Key: NIFI-2640
> URL: https://issues.apache.org/jira/browse/NIFI-2640
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: configuration, encryption, security, windows
> Fix For: 1.0.0
>
>
> The *nix script {{encrypt-config.sh}} properly invokes the 
> {{ConfigEncryptionTool}} but the Windows {{encrypt-config.bat}} does not. 



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

[jira] [Commented] (NIFI-2640) Fix Windows command-line utility for encrypted configuration files

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2640:
--

Github user asfgit closed the pull request at:

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


> Fix Windows command-line utility for encrypted configuration files
> --
>
> Key: NIFI-2640
> URL: https://issues.apache.org/jira/browse/NIFI-2640
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: configuration, encryption, security, windows
> Fix For: 1.0.0
>
>
> The *nix script {{encrypt-config.sh}} properly invokes the 
> {{ConfigEncryptionTool}} but the Windows {{encrypt-config.bat}} does not. 



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

[GitHub] nifi pull request #925: NIFI-2640 Fixed Windows encrypt-config.bat script

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2644) Windows file permissions and line endings cause tests to fail

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2640 Fixed Windows encrypt-config.bat script to correctly invoke 
ConfigEncryptionTool. - Resolved failing Windows tests by adding OS-agnostic 
file permission read/write methods and new regex for different date formats. - 
Ignored tests that fail on Windows due to file permission and line ending 
issues. These are captured in NIFI-2644.

This closes #925

Signed-off-by: jpercivall 


> Windows file permissions and line endings cause tests to fail
> -
>
> Key: NIFI-2644
> URL: https://issues.apache.org/jira/browse/NIFI-2644
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Minor
> Fix For: 1.1.0
>
>
> The {{ConfigEncryptionToolTest}} has three tests which fail on Windows -- two 
> due to Windows not being able to modify the file permissions in order to 
> cause the expected {{IOException}} to be thrown, and one because the 
> serialized {{nifi.properties}} has different line endings than expected. 
> These are not blockers for 1.0.0 because they assert only failure scenarios 
> and will not impede the actual behavior of the tool. 
> We can re-investigate for 1.1.0. 
> {code}
> [INFO] Scanning for projects...
> [INFO] Inspecting build with total of 1 modules...
> [INFO] Installing Nexus Staging features:
> [INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
> nexus-staging-maven-plugin
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building nifi-toolkit-encrypt-config 1.0.0-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Deleting 
> C:\Users\Joe\AppData\Local\Programs\Git\nifi\nifi-toolkit\nifi-toolkit-encrypt-config\target
> [INFO] 
> [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] 
> [INFO] --- build-helper-maven-plugin:1.5:add-source (add-source) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Source directory: 
> C:\Users\Joe\AppData\Local\Programs\Git\nifi\nifi-toolkit\nifi-toolkit-encrypt-config\src\main\groovy
>  added.
> [INFO] 
> [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] 
> [INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2 resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 6 source files to 
> C:\Users\Joe\AppData\Local\Programs\Git\nifi\nifi-toolkit\nifi-toolkit-encrypt-config\target\classes
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:compile (default) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
> [INFO] Found location 
> 
>  for className 
> [INFO] no javaAgentClass seems to be set
> [INFO] Compiling in a forked process using 
> C:\Users\Joe\.m2\repository\org\codehaus\groovy\groovy-eclipse-batch\2.4.3-01\groovy-eclipse-batch-2.4.3-01.jar
> [INFO] 
> [INFO] --- build-helper-maven-plugin:1.5:add-test-source (add-test-source) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Test Source directory: 
> C:\Users\Joe\AppData\Local\Programs\Git\nifi\nifi-toolkit\nifi-toolkit-encrypt-config\src\test\groovy
>  added.
> [INFO] 
> [INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 10 resources
> [INFO] Copying 3 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
> nifi-toolkit-encrypt-config ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:testCompile (groovy-tests) @ 
> 

[jira] [Commented] (NIFI-2640) Fix Windows command-line utility for encrypted configuration files

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2640 Fixed Windows encrypt-config.bat script to correctly invoke 
ConfigEncryptionTool. - Resolved failing Windows tests by adding OS-agnostic 
file permission read/write methods and new regex for different date formats. - 
Ignored tests that fail on Windows due to file permission and line ending 
issues. These are captured in NIFI-2644.

This closes #925

Signed-off-by: jpercivall 


> Fix Windows command-line utility for encrypted configuration files
> --
>
> Key: NIFI-2640
> URL: https://issues.apache.org/jira/browse/NIFI-2640
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: configuration, encryption, security, windows
> Fix For: 1.0.0
>
>
> The *nix script {{encrypt-config.sh}} properly invokes the 
> {{ConfigEncryptionTool}} but the Windows {{encrypt-config.bat}} does not. 



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

[jira] [Commented] (NIFI-2640) Fix Windows command-line utility for encrypted configuration files

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2640:
--

Github user JPercivall commented on the issue:

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

Visually verified code and ran a contrib check build on Windows 8. Observed 
that the bat script runs as expected on Windows. Thanks @alopresto, I will 
squash and merge it in.


> Fix Windows command-line utility for encrypted configuration files
> --
>
> Key: NIFI-2640
> URL: https://issues.apache.org/jira/browse/NIFI-2640
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: configuration, encryption, security, windows
> Fix For: 1.0.0
>
>
> The *nix script {{encrypt-config.sh}} properly invokes the 
> {{ConfigEncryptionTool}} but the Windows {{encrypt-config.bat}} does not. 



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

[GitHub] nifi issue #925: NIFI-2640 Fixed Windows encrypt-config.bat script

[JPercivall]

Github user JPercivall commented on the issue:

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

Visually verified code and ran a contrib check build on Windows 8. Observed 
that the bat script runs as expected on Windows. Thanks @alopresto, I will 
squash and merge it in.


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

[jira] [Commented] (NIFI-2647) Dirty state of Controller Service and Reporting Task configs not being kept correctly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2647:
--

GitHub user mcgilman opened a pull request:

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

UI - Fixing check to determine if save is required

NIFI-2647:
- Referencing correct components when checking if save is required.

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

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

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

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


commit aa8d3efcb8f7514f45e3e475505f25c53f96496f
Author: Matt Gilman 
Date:   2016-08-24T20:56:25Z

NIFI-2647:
- Referencing correct components when checking if save is required.




> Dirty state of Controller Service and Reporting Task configs not being kept 
> correctly
> -
>
> Key: NIFI-2647
> URL: https://issues.apache.org/jira/browse/NIFI-2647
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Jeff Storck
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> When opening the configuration for a controller service or reporting task 
> that uses a controller service reference, clicking on the "go to" arrow 
> widget to go to the referenced controller service results in the user being 
> asked if it should save first, regardless of the dirty state of the 
> configuration.



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

[jira] [Updated] (NIFI-2647) Dirty state of Controller Service and Reporting Task configs not being kept correctly

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-2647:
--
Status: Patch Available  (was: In Progress)

> Dirty state of Controller Service and Reporting Task configs not being kept 
> correctly
> -
>
> Key: NIFI-2647
> URL: https://issues.apache.org/jira/browse/NIFI-2647
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Jeff Storck
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> When opening the configuration for a controller service or reporting task 
> that uses a controller service reference, clicking on the "go to" arrow 
> widget to go to the referenced controller service results in the user being 
> asked if it should save first, regardless of the dirty state of the 
> configuration.



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

[GitHub] nifi pull request #935: UI - Fixing check to determine if save is required

[mcgilman]

GitHub user mcgilman opened a pull request:

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

UI - Fixing check to determine if save is required

NIFI-2647:
- Referencing correct components when checking if save is required.

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

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

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

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


commit aa8d3efcb8f7514f45e3e475505f25c53f96496f
Author: Matt Gilman 
Date:   2016-08-24T20:56:25Z

NIFI-2647:
- Referencing correct components when checking if save is required.




---
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-2648) Edit formatting of TLS toolkit section of Admin guide for improved readability and consistency

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2648:
-
Fix Version/s: 1.0.0

> Edit formatting of TLS toolkit section of Admin guide for improved 
> readability and consistency
> --
>
> Key: NIFI-2648
> URL: https://issues.apache.org/jira/browse/NIFI-2648
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.0.0
>
>
> Encrypt-config tool was added to Admin guide per NIFI-2451.  The formatting 
> there should also be applied to the TLS-toolkit utility for consistency.  The 
> formatting also improves readability.



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

[jira] [Commented] (NIFI-2648) Edit formatting of TLS toolkit section of Admin guide for improved readability and consistency

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2648:
--

GitHub user andrewmlim opened a pull request:

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

NIFI-2648 Edit formatting of TLS toolkit section of Admin guide for i…

…mproved readability and consistency

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

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

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

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


commit 60660e8ada8e67915a42a86c7008c87a5810f488
Author: Andrew Lim 
Date:   2016-08-24T20:42:59Z

NIFI-2648 Edit formatting of TLS toolkit section of Admin guide for 
improved readability and consistency




> Edit formatting of TLS toolkit section of Admin guide for improved 
> readability and consistency
> --
>
> Key: NIFI-2648
> URL: https://issues.apache.org/jira/browse/NIFI-2648
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> Encrypt-config tool was added to Admin guide per NIFI-2451.  The formatting 
> there should also be applied to the TLS-toolkit utility for consistency.  The 
> formatting also improves readability.



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