[GitHub] nifi pull request #802: NIFI-2470 - Fix WritesAttributes section of ListFile...

[kirkalicious]

GitHub user kirkalicious reopened a pull request:

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

NIFI-2470 - Fix WritesAttributes section of ListFiles

Fixed WritesAttributes section to include all attributes with the
correct attribute names and descriptions

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

$ git pull https://github.com/kirkalicious/nifi NIFI-2470

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

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


commit acd5bd532be63d01bb94972ac1fa417d8fe44311
Author: Kirk Tarou 
Date:   2016-08-06T01:16:23Z

NIFI-2470

Fixed WritesAttributes section to include all attributes with the
correct attribute names and descriptions




---
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 #802: NIFI-2470 - Fix WritesAttributes section of ListFile...

[kirkalicious]

Github user kirkalicious closed the pull request at:

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


---
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-2470) WritesAttributes annotations in ListFile are incorrect

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2470:
--

GitHub user kirkalicious reopened a pull request:

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

NIFI-2470

Fixed WritesAttributes section to include all attributes with the
correct attribute names and descriptions

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

$ git pull https://github.com/kirkalicious/nifi NIFI-2470

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

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


commit acd5bd532be63d01bb94972ac1fa417d8fe44311
Author: Kirk Tarou 
Date:   2016-08-06T01:16:23Z

NIFI-2470

Fixed WritesAttributes section to include all attributes with the
correct attribute names and descriptions




> WritesAttributes annotations in ListFile are incorrect
> --
>
> Key: NIFI-2470
> URL: https://issues.apache.org/jira/browse/NIFI-2470
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Kirk Tarou
>Priority: Minor
>  Labels: beginner, beginners, documentation, easyfix
> Attachments: ListFileAttributes.png, ListFileUsage.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The WritesAttributes annotations section has a variety of problems that need 
> to be cleaned up. Otherwise, 'Usage' documentation will be incorrect.
> # Some of the WritesAttributes annotations don't match the actual attribute 
> names:
> #* fs.owner -> file.owner
> #* fs.group -> file.group
> #* fs.lastModified -> file.lastModifiedTime
> #* fs.length -> file.length
> #* fs.permissions -> file.permissions
> # missing:
> #* file.creationTime
> #* file.lastAccessTime
> # Incorrect description
> #* file.lastModifiedTime is a formatted date/time



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

[jira] [Commented] (NIFI-2470) WritesAttributes annotations in ListFile are incorrect

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2470:
--

Github user kirkalicious closed the pull request at:

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


> WritesAttributes annotations in ListFile are incorrect
> --
>
> Key: NIFI-2470
> URL: https://issues.apache.org/jira/browse/NIFI-2470
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Kirk Tarou
>Priority: Minor
>  Labels: beginner, beginners, documentation, easyfix
> Attachments: ListFileAttributes.png, ListFileUsage.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The WritesAttributes annotations section has a variety of problems that need 
> to be cleaned up. Otherwise, 'Usage' documentation will be incorrect.
> # Some of the WritesAttributes annotations don't match the actual attribute 
> names:
> #* fs.owner -> file.owner
> #* fs.group -> file.group
> #* fs.lastModified -> file.lastModifiedTime
> #* fs.length -> file.length
> #* fs.permissions -> file.permissions
> # missing:
> #* file.creationTime
> #* file.lastAccessTime
> # Incorrect description
> #* file.lastModifiedTime is a formatted date/time



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

[GitHub] nifi pull request #802: NIFI-2470

[kirkalicious]

GitHub user kirkalicious reopened a pull request:

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

NIFI-2470

Fixed WritesAttributes section to include all attributes with the
correct attribute names and descriptions

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

$ git pull https://github.com/kirkalicious/nifi NIFI-2470

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

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


commit acd5bd532be63d01bb94972ac1fa417d8fe44311
Author: Kirk Tarou 
Date:   2016-08-06T01:16:23Z

NIFI-2470

Fixed WritesAttributes section to include all attributes with the
correct attribute names and descriptions




---
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 #802: NIFI-2470

[kirkalicious]

Github user kirkalicious closed the pull request at:

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


---
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-2470) WritesAttributes annotations in ListFile are incorrect

[Kirk Tarou (JIRA)]

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

Kirk Tarou commented on NIFI-2470:
--

Submitted pull request for this:
https://github.com/apache/nifi/pull/802

> WritesAttributes annotations in ListFile are incorrect
> --
>
> Key: NIFI-2470
> URL: https://issues.apache.org/jira/browse/NIFI-2470
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Kirk Tarou
>Priority: Minor
>  Labels: beginner, beginners, documentation, easyfix
> Attachments: ListFileAttributes.png, ListFileUsage.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The WritesAttributes annotations section has a variety of problems that need 
> to be cleaned up. Otherwise, 'Usage' documentation will be incorrect.
> # Some of the WritesAttributes annotations don't match the actual attribute 
> names:
> #* fs.owner -> file.owner
> #* fs.group -> file.group
> #* fs.lastModified -> file.lastModifiedTime
> #* fs.length -> file.length
> #* fs.permissions -> file.permissions
> # missing:
> #* file.creationTime
> #* file.lastAccessTime
> # Incorrect description
> #* file.lastModifiedTime is a formatted date/time



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

[jira] [Commented] (NIFI-2470) WritesAttributes annotations in ListFile are incorrect

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2470:
--

GitHub user kirkalicious opened a pull request:

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

NIFI-2470

Fixed WritesAttributes section to include all attributes with the
correct attribute names and descriptions

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

$ git pull https://github.com/kirkalicious/nifi NIFI-2470

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

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


commit acd5bd532be63d01bb94972ac1fa417d8fe44311
Author: Kirk Tarou 
Date:   2016-08-06T01:16:23Z

NIFI-2470

Fixed WritesAttributes section to include all attributes with the
correct attribute names and descriptions




> WritesAttributes annotations in ListFile are incorrect
> --
>
> Key: NIFI-2470
> URL: https://issues.apache.org/jira/browse/NIFI-2470
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.7.0
>Reporter: Kirk Tarou
>Priority: Minor
>  Labels: beginner, beginners, documentation, easyfix
> Attachments: ListFileAttributes.png, ListFileUsage.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The WritesAttributes annotations section has a variety of problems that need 
> to be cleaned up. Otherwise, 'Usage' documentation will be incorrect.
> # Some of the WritesAttributes annotations don't match the actual attribute 
> names:
> #* fs.owner -> file.owner
> #* fs.group -> file.group
> #* fs.lastModified -> file.lastModifiedTime
> #* fs.length -> file.length
> #* fs.permissions -> file.permissions
> # missing:
> #* file.creationTime
> #* file.lastAccessTime
> # Incorrect description
> #* file.lastModifiedTime is a formatted date/time



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

[GitHub] nifi pull request #802: NIFI-2470

[kirkalicious]

GitHub user kirkalicious opened a pull request:

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

NIFI-2470

Fixed WritesAttributes section to include all attributes with the
correct attribute names and descriptions

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

$ git pull https://github.com/kirkalicious/nifi NIFI-2470

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

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


commit acd5bd532be63d01bb94972ac1fa417d8fe44311
Author: Kirk Tarou 
Date:   2016-08-06T01:16:23Z

NIFI-2470

Fixed WritesAttributes section to include all attributes with the
correct attribute names and descriptions




---
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-2476) Further refine tls-toolkit based on feedback gathered during beta

[Andy LoPresto (JIRA)]

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

Andy LoPresto commented on NIFI-2476:
-

Upon further use, I think the tool should provide a flag to allow a custom 
client certificate to be generated and signed by the CA certificate. Prompt for 
the desired user name (CN), and form a key and complete certificate (only valid 
for EKU clientAuth), and output these files independently and wrapped in a 
PKCS12 keystore. The tool makes it easy to secure the nodes but access is only 
available at that time via client certificate, LDAP, and/or Kerberos 
authentication, and for rapid deployment, a client certificate is essential. 
Continually re-importing the CA certificate into the Keychain to use as a 
client cert is impractical, tedious, and negatively affects the attack surface 
of the CA certificate.  

> Further refine tls-toolkit based on feedback gathered during beta
> -
>
> Key: NIFI-2476
> URL: https://issues.apache.org/jira/browse/NIFI-2476
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Rosander
>Assignee: Bryan Rosander
>
> The basic functionality of generating keystores, truststores, 
> nifi.properties, and a configuration json is implemented.
> As people start using this tool to ease the tls setup process in NiFi, 
> shortcomings in the initial implementation will need to be addressed.



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

[jira] [Commented] (NIFI-1148) Add processor to GetEmail supporting IMAP and POP3

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1148:
--

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

https://github.com/apache/nifi/pull/710#discussion_r73770089
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/resources/docs/org.apache.nifi.processors.email.ConsumePOP3/additionalDetails.html
 ---
@@ -0,0 +1,59 @@
+
+
+
+
+
+ConsumePOP3
+
+
+
+
+   
+   Description:
+   This Processors consumes email messages via POP3 protocol and
+   sends the content of an email message as content of the 
FlowFile.
+   Content of the incoming email message is written as raw bytes 
to the
+   content of the outgoing Flow File.
+
+
+   Since different serves may require different Java Mail
+   properties such properties could be provided via dynamic 
properties.
+   For example, below is a sample configuration for GMail:
+   
+   
+   Processor's static properties:
+   
+   Host Name - pop.gmail.com
+   Port - 995
+   User Name - [your user name]
+   Password - [your password]
+   Folder - INBOX
+   
+   Processor's dynamic properties:
+   
+   mail.pop3.socketFactory.class - 
javax.net.ssl.SSLSocketFactory
--- End diff --

Same comments about populating, typos, etc. as for ConsumeIMAP above.


> Add processor to GetEmail supporting IMAP and POP3
> --
>
> Key: NIFI-1148
> URL: https://issues.apache.org/jira/browse/NIFI-1148
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



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

[GitHub] nifi pull request #710: NIFI-1148 added IMAP/POP3 support

[mattyb149]

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

https://github.com/apache/nifi/pull/710#discussion_r73770089
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/resources/docs/org.apache.nifi.processors.email.ConsumePOP3/additionalDetails.html
 ---
@@ -0,0 +1,59 @@
+
+
+
+
+
+ConsumePOP3
+
+
+
+
+   
+   Description:
+   This Processors consumes email messages via POP3 protocol and
+   sends the content of an email message as content of the 
FlowFile.
+   Content of the incoming email message is written as raw bytes 
to the
+   content of the outgoing Flow File.
+
+
+   Since different serves may require different Java Mail
+   properties such properties could be provided via dynamic 
properties.
+   For example, below is a sample configuration for GMail:
+   
+   
+   Processor's static properties:
+   
+   Host Name - pop.gmail.com
+   Port - 995
+   User Name - [your user name]
+   Password - [your password]
+   Folder - INBOX
+   
+   Processor's dynamic properties:
+   
+   mail.pop3.socketFactory.class - 
javax.net.ssl.SSLSocketFactory
--- End diff --

Same comments about populating, typos, etc. as for ConsumeIMAP above.


---
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-1148) Add processor to GetEmail supporting IMAP and POP3

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1148:
--

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

https://github.com/apache/nifi/pull/710#discussion_r73769916
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/resources/docs/org.apache.nifi.processors.email.ConsumeIMAP/additionalDetails.html
 ---
@@ -0,0 +1,60 @@
+
+
+
+
+
+ConsumeIMAP
+
+
+
+
+   
+   Description:
+   This Processors consumes email messages via IMAP protocol and
+   sends the content of an email message as content of the 
FlowFile.
+   Content of the incoming email message is written as raw bytes 
to the
+   content of the outgoing Flow File.
+
+
+   Since different serves may require different Java Mail
+   properties such properties could be provided via dynamic 
properties.
--- End diff --

that's a lot of "properties" in the same sentence ;)


> Add processor to GetEmail supporting IMAP and POP3
> --
>
> Key: NIFI-1148
> URL: https://issues.apache.org/jira/browse/NIFI-1148
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



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

[GitHub] nifi pull request #710: NIFI-1148 added IMAP/POP3 support

[mattyb149]

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

https://github.com/apache/nifi/pull/710#discussion_r73769802
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/resources/docs/org.apache.nifi.processors.email.ConsumeIMAP/additionalDetails.html
 ---
@@ -0,0 +1,60 @@
+
+
+
+
+
+ConsumeIMAP
+
+
+
+
+   
+   Description:
+   This Processors consumes email messages via IMAP protocol and
+   sends the content of an email message as content of the 
FlowFile.
+   Content of the incoming email message is written as raw bytes 
to the
+   content of the outgoing Flow File.
+
+
+   Since different serves may require different Java Mail
+   properties such properties could be provided via dynamic 
properties.
+   For example, below is a sample configuration for GMail:
+   
+   
+   Processor's static properties:
+   
+   Host Name - imap.gmail.com
+   Port - 993
+   User Name - [your user name]
+   Password - [your password]
+   Folder - INBOX
+   
+   Processor's dynamic properties:
+   
+   mail.imap.socketFactory.class - 
javax.net.ssl.SSLSocketFactory
+   mail.imap.socketFactory.fallback - false
+   mail.store.protocol - imaps
+   
+   
+   
+   Another useful property to  mail.debug which allows Java 
Mail API to print protocol messages to the console helping you to both 
understand what's going on as well as debug issues.
--- End diff --

I think this should be "Another useful property *is*" rather than *to*.


---
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-1148) Add processor to GetEmail supporting IMAP and POP3

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1148:
--

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

https://github.com/apache/nifi/pull/710#discussion_r73769714
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/resources/docs/org.apache.nifi.processors.email.ConsumeIMAP/additionalDetails.html
 ---
@@ -0,0 +1,60 @@
+
+
+
+
+
+ConsumeIMAP
+
+
+
+
+   
+   Description:
+   This Processors consumes email messages via IMAP protocol and
+   sends the content of an email message as content of the 
FlowFile.
+   Content of the incoming email message is written as raw bytes 
to the
+   content of the outgoing Flow File.
+
+
+   Since different serves may require different Java Mail
+   properties such properties could be provided via dynamic 
properties.
+   For example, below is a sample configuration for GMail:
+   
+   
+   Processor's static properties:
+   
+   Host Name - imap.gmail.com
+   Port - 993
+   User Name - [your user name]
+   Password - [your password]
+   Folder - INBOX
+   
+   Processor's dynamic properties:
+   
+   mail.imap.socketFactory.class - 
javax.net.ssl.SSLSocketFactory
+   mail.imap.socketFactory.fallback - false
+   mail.store.protocol - imaps
--- End diff --

I get that the properties are often different for different services, 
servers, etc. But is there something we can do with setting property defaults, 
such as socket factory or protocol, for example if "Use secure" is true? If 
dynamic properties are provided we'd use those, but if they were inadvertantly 
left out then the defaults would be populated.
The idea here is that there's a "Use Secure" property, but then you have to 
set the socket factory class to a secure factory, set the protocol to the 
secure version, etc. If there aren't widely used services that *require* these 
properties to be un-set, then I would think a better user experience would be 
for the "Use Secure" to take care of as much of the Java Mail property config 
as possible.  Thoughts?


> Add processor to GetEmail supporting IMAP and POP3
> --
>
> Key: NIFI-1148
> URL: https://issues.apache.org/jira/browse/NIFI-1148
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



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

[jira] [Commented] (NIFI-2507) PutS3Object should support Canned ACLs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2507:
--

GitHub user tequalsme opened a pull request:

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

NIFI-2507 Added Canned ACL support to PutS3Object



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

$ git pull https://github.com/tequalsme/incubator-nifi NIFI-2507

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

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


commit 4e6dc857f462923d3ebc018d3d35e8c205d1e249
Author: Tim Reardon 
Date:   2016-08-05T21:06:38Z

NIFI-2507 Added Canned ACL support to PutS3Object




> PutS3Object should support Canned ACLs
> --
>
> Key: NIFI-2507
> URL: https://issues.apache.org/jira/browse/NIFI-2507
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Tim Reardon
>Priority: Minor
>
> In order to support cross-account scenarios, PutS3Object should support 
> specifying canned ACL's such as "bucket-owner-full-control".
> See 
> http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl



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

[GitHub] nifi pull request #801: NIFI-2507 Added Canned ACL support to PutS3Object

[tequalsme]

GitHub user tequalsme opened a pull request:

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

NIFI-2507 Added Canned ACL support to PutS3Object



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

$ git pull https://github.com/tequalsme/incubator-nifi NIFI-2507

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

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


commit 4e6dc857f462923d3ebc018d3d35e8c205d1e249
Author: Tim Reardon 
Date:   2016-08-05T21:06:38Z

NIFI-2507 Added Canned ACL support to PutS3Object




---
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-2406) Rare start-up problems resulting in all nodes disconnected

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2406:
--

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/729
  
@markap14 thank you for this update. I executed my tests as previously 
described and ran into no issues. When disconnecting a node designated as 
cluster coordinator from both the UI and on the command line (through 
stop/restart) the remaining nodes behaves as expected. It properly displays an 
error to the user and nots in logs it's inability to determine a cluster 
coordinator. When the coordinator is back online the logs indicate successful 
reconnection and communication. Refresh of the screen properly demonstrates the 
flow and configured flow (which consists of use of remote process groups 
communicating with a standalone nifi node) operate successfully

+1

thank you @markap14 for the quick turnaround on this!



> Rare start-up problems resulting in all nodes disconnected
> --
>
> Key: NIFI-2406
> URL: https://issues.apache.org/jira/browse/NIFI-2406
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Fix For: 1.0.0
>
> Attachments: logs.tar.gz
>
>
> While testing PR 678[1], I came across a time where all the nodes were in a 
> disconnected state and each were in a weird state of heartbeating but not 
> connected.
> Also in the logs there were ~1000 lines of:
> 2016-07-26 11:38:07,841 INFO [Leader Election Notification Thread-1] 
> o.a.n.c.l.e.CuratorLeaderElectionManager 
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@24fae8c6
>  This node has been elected Leader for Role 'Cluster Coordinator'
> This message only gets called here[2] which is a call back for ZK. Also there 
> were many log messages of:
> 2016-07-26 11:54:07,910 WARN [Clustering Tasks Thread-1] 
> o.a.n.c.c.node.NodeClusterCoordinator Failed to determine which node is 
> elected active Cluster Coordinator: ZooKeeper reports the address as 
> localhost:6001, but there is no node with this address
> I believe this is a problem with ZK/NiFi that existed before this PR and not 
> directly related to the PR being reviewed. I will attach a tar of the 3 
> node's logs.
> [1] https://github.com/apache/nifi/pull/678
> [2] 
> https://github.com/apache/nifi/blame/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/leader/election/CuratorLeaderElectionManager.java#L220-L220



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

[GitHub] nifi issue #729: NIFI-2406: Ensure that hearbeat monitor continues to run wh...

[YolandaMDavis]

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/729
  
@markap14 thank you for this update. I executed my tests as previously 
described and ran into no issues. When disconnecting a node designated as 
cluster coordinator from both the UI and on the command line (through 
stop/restart) the remaining nodes behaves as expected. It properly displays an 
error to the user and nots in logs it's inability to determine a cluster 
coordinator. When the coordinator is back online the logs indicate successful 
reconnection and communication. Refresh of the screen properly demonstrates the 
flow and configured flow (which consists of use of remote process groups 
communicating with a standalone nifi node) operate successfully

+1

thank you @markap14 for the quick turnaround on 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-2505) Flow Configuration History not showing values in the User column

[Matt Gilman (JIRA)]

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

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

> Flow Configuration History not showing values in the User column
> 
>
> Key: NIFI-2505
> URL: https://issues.apache.org/jira/browse/NIFI-2505
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Jeff Storck
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
> Attachments: Screen Shot 2016-08-05 at 3.40.31 PM.png
>
>
> While running in a 3-node secured cluster, after making some flow 
> modifications, when I check the Flow Configuration History, the User column 
> of the table shows "No value previously set".



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

[GitHub] nifi pull request #800: Addressing issue preventing the display of the user ...

[mcgilman]

GitHub user mcgilman opened a pull request:

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

Addressing issue preventing the display of the user in the history table

NIFI-2505:
- Updating the user identity field in the ActionDTO.

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

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

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

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


commit 323e1dd24c6495f71f66f761612995a9ccdcc2b4
Author: Matt Gilman 
Date:   2016-08-05T20:35:13Z

NIFI-2505:
- Updating the user identity field in the ActionDTO.




---
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-2505) Flow Configuration History not showing values in the User column

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2505:
--

GitHub user mcgilman opened a pull request:

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

Addressing issue preventing the display of the user in the history table

NIFI-2505:
- Updating the user identity field in the ActionDTO.

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

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

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

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


commit 323e1dd24c6495f71f66f761612995a9ccdcc2b4
Author: Matt Gilman 
Date:   2016-08-05T20:35:13Z

NIFI-2505:
- Updating the user identity field in the ActionDTO.




> Flow Configuration History not showing values in the User column
> 
>
> Key: NIFI-2505
> URL: https://issues.apache.org/jira/browse/NIFI-2505
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Jeff Storck
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
> Attachments: Screen Shot 2016-08-05 at 3.40.31 PM.png
>
>
> While running in a 3-node secured cluster, after making some flow 
> modifications, when I check the Flow Configuration History, the User column 
> of the table shows "No value previously set".



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

[jira] [Updated] (NIFI-2505) Flow Configuration History not showing values in the User column

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-2505:
--
Fix Version/s: 1.0.0

> Flow Configuration History not showing values in the User column
> 
>
> Key: NIFI-2505
> URL: https://issues.apache.org/jira/browse/NIFI-2505
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Jeff Storck
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
> Attachments: Screen Shot 2016-08-05 at 3.40.31 PM.png
>
>
> While running in a 3-node secured cluster, after making some flow 
> modifications, when I check the Flow Configuration History, the User column 
> of the table shows "No value previously set".



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

[jira] [Commented] (NIFI-2506) Update screenshot in README.md for new 1.0 UI

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2506:
--

GitHub user andrewmlim opened a pull request:

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

NIFI-2506 Update screenshot in README.md for new 1.0 UI



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

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

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

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


commit 5409ab6915a39280d1bf11ae9f8818c3a42eaf7b
Author: Andrew Lim 
Date:   2016-08-05T20:06:43Z

NIFI-2506 Update screenshot in README.md for new 1.0 UI




> Update screenshot in README.md for new 1.0 UI
> -
>
> Key: NIFI-2506
> URL: https://issues.apache.org/jira/browse/NIFI-2506
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: nifi_first_launch_screenshot.png
>
>
> The screenshot in README.md should be updated for the new 1.0 UI.



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

[GitHub] nifi pull request #799: NIFI-2506 Update screenshot in README.md for new 1.0...

[andrewmlim]

GitHub user andrewmlim opened a pull request:

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

NIFI-2506 Update screenshot in README.md for new 1.0 UI



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

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

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

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


commit 5409ab6915a39280d1bf11ae9f8818c3a42eaf7b
Author: Andrew Lim 
Date:   2016-08-05T20:06:43Z

NIFI-2506 Update screenshot in README.md for new 1.0 UI




---
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-2493) If Port's scheduled state is not the same as cluster when a node joins, allow the node to join and update the Port

[Mark Payne (JIRA)]

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

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

> If Port's scheduled state is not the same as cluster when a node joins, allow 
> the node to join and update the Port
> --
>
> Key: NIFI-2493
> URL: https://issues.apache.org/jira/browse/NIFI-2493
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>




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

[jira] [Commented] (NIFI-2493) If Port's scheduled state is not the same as cluster when a node joins, allow the node to join and update the Port

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2493:
--

GitHub user markap14 opened a pull request:

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

NIFI-2493: Do not fingerprint Remote Ports' running state. When synch…

…ronizing remote flow with local flow, start/stop remote group ports as 
appropriate based on the inherited flow

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

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

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

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


commit 36e4c57ebc400ba1617d20a1494534ac15d7e2b2
Author: Mark Payne 
Date:   2016-08-05T19:52:45Z

NIFI-2493: Do not fingerprint Remote Ports' running state. When 
synchronizing remote flow with local flow, start/stop remote group ports as 
appropriate based on the inherited flow




> If Port's scheduled state is not the same as cluster when a node joins, allow 
> the node to join and update the Port
> --
>
> Key: NIFI-2493
> URL: https://issues.apache.org/jira/browse/NIFI-2493
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.0.0
>
>




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

[jira] [Commented] (NIFI-2494) Remove extraneous text that shows on banner line

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2494:
--

Github user asfgit closed the pull request at:

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


> Remove extraneous text that shows on banner line
> 
>
> Key: NIFI-2494
> URL: https://issues.apache.org/jira/browse/NIFI-2494
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Trivial
> Fix For: 1.0.0
>
>
> The words "NiFi Settings" appear on the top left of the page, on the banner 
> line.  They appear to be included in the page render and the banner message 
> is rendered as background so the text is not overwritten.



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

[jira] [Updated] (NIFI-2494) Remove extraneous text that shows on banner line

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-2494:
--
Fix Version/s: 1.0.0

> Remove extraneous text that shows on banner line
> 
>
> Key: NIFI-2494
> URL: https://issues.apache.org/jira/browse/NIFI-2494
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Trivial
> Fix For: 1.0.0
>
>
> The words "NiFi Settings" appear on the top left of the page, on the banner 
> line.  They appear to be included in the page render and the banner message 
> is rendered as background so the text is not overwritten.



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

[jira] [Commented] (NIFI-2494) Remove extraneous text that shows on banner line

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2494:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/793
  
Thanks @jskora. I've merged this to master.


> Remove extraneous text that shows on banner line
> 
>
> Key: NIFI-2494
> URL: https://issues.apache.org/jira/browse/NIFI-2494
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Trivial
> Fix For: 1.0.0
>
>
> The words "NiFi Settings" appear on the top left of the page, on the banner 
> line.  They appear to be included in the page render and the banner message 
> is rendered as background so the text is not overwritten.



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

[jira] [Commented] (NIFI-2494) Remove extraneous text that shows on banner line

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2494 Remove extraneous text that shows on banner line. This closes #793


> Remove extraneous text that shows on banner line
> 
>
> Key: NIFI-2494
> URL: https://issues.apache.org/jira/browse/NIFI-2494
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Trivial
>
> The words "NiFi Settings" appear on the top left of the page, on the banner 
> line.  They appear to be included in the page render and the banner message 
> is rendered as background so the text is not overwritten.



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

[GitHub] nifi pull request #793: NIFI-2494 Remove extraneous text that shows on banne...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2494) Remove extraneous text that shows on banner line

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2494:
--

Github user jskora commented on the issue:

https://github.com/apache/nifi/pull/793
  
@mcgilman, I restored the text and added the class to the div tag.  My 
canvas is still fixed and the title is back on the Controller Settings page.

Thanks for catching that.



> Remove extraneous text that shows on banner line
> 
>
> Key: NIFI-2494
> URL: https://issues.apache.org/jira/browse/NIFI-2494
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Trivial
>
> The words "NiFi Settings" appear on the top left of the page, on the banner 
> line.  They appear to be included in the page render and the banner message 
> is rendered as background so the text is not overwritten.



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

[GitHub] nifi issue #793: NIFI-2494 Remove extraneous text that shows on banner line

[jskora]

Github user jskora commented on the issue:

https://github.com/apache/nifi/pull/793
  
@mcgilman, I restored the text and added the class to the div tag.  My 
canvas is still fixed and the title is back on the Controller Settings page.

Thanks for catching that.



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

[jira] [Assigned] (NIFI-2506) Update screenshot in README.md for new 1.0 UI

[Andrew Lim (JIRA)]

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

Andrew Lim reassigned NIFI-2506:


Assignee: Andrew Lim

> Update screenshot in README.md for new 1.0 UI
> -
>
> Key: NIFI-2506
> URL: https://issues.apache.org/jira/browse/NIFI-2506
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: nifi_first_launch_screenshot.png
>
>
> The screenshot in README.md should be updated for the new 1.0 UI.



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

[jira] [Updated] (NIFI-2506) Update screenshot in README.md for new 1.0 UI

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2506:
-
Attachment: nifi_first_launch_screenshot.png

> Update screenshot in README.md for new 1.0 UI
> -
>
> Key: NIFI-2506
> URL: https://issues.apache.org/jira/browse/NIFI-2506
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Reporter: Andrew Lim
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: nifi_first_launch_screenshot.png
>
>
> The screenshot in README.md should be updated for the new 1.0 UI.



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

[jira] [Created] (NIFI-2506) Update screenshot in README.md for new 1.0 UI

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2506:


 Summary: Update screenshot in README.md for new 1.0 UI
 Key: NIFI-2506
 URL: https://issues.apache.org/jira/browse/NIFI-2506
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Documentation & Website
Reporter: Andrew Lim
Priority: Minor
 Fix For: 1.0.0


The screenshot in README.md should be updated for the new 1.0 UI.



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

[jira] [Commented] (NIFI-2494) Remove extraneous text that shows on banner line

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2494:
--

Github user jskora commented on the issue:

https://github.com/apache/nifi/pull/793
  
Working on it now.


> Remove extraneous text that shows on banner line
> 
>
> Key: NIFI-2494
> URL: https://issues.apache.org/jira/browse/NIFI-2494
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Trivial
>
> The words "NiFi Settings" appear on the top left of the page, on the banner 
> line.  They appear to be included in the page render and the banner message 
> is rendered as background so the text is not overwritten.



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

[GitHub] nifi issue #793: NIFI-2494 Remove extraneous text that shows on banner line

[jskora]

Github user jskora commented on the issue:

https://github.com/apache/nifi/pull/793
  
Working on it now.


---
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-2498) Perform Release Management Functions for 1.0.0-BETA

[ASF subversion and git services (JIRA)]

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

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

Commit 6c7b78771ae3e53a1783af3138630ace10cb1d58 in nifi's branch 
refs/heads/NIFI-2498-rc1 from [~JPercivall]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=6c7b787 ]

NIFI-2498-rc1 prepare for next development iteration


> Perform Release Management Functions for 1.0.0-BETA
> ---
>
> Key: NIFI-2498
> URL: https://issues.apache.org/jira/browse/NIFI-2498
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>




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

[jira] [Created] (NIFI-2505) Flow Configuration History not showing values in the User column

[Jeff Storck (JIRA)]

Jeff Storck created NIFI-2505:
-

 Summary: Flow Configuration History not showing values in the User 
column
 Key: NIFI-2505
 URL: https://issues.apache.org/jira/browse/NIFI-2505
 Project: Apache NiFi
  Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Jeff Storck


While running in a 3-node secured cluster, after making some flow 
modifications, when I check the Flow Configuration History, the User column of 
the table shows "No value previously set".



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

[jira] [Commented] (NIFI-2498) Perform Release Management Functions for 1.0.0-BETA

[ASF subversion and git services (JIRA)]

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

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

Commit b8813cb55d5ab4309b81b8941fb12651489732cd in nifi's branch 
refs/heads/NIFI-2498-rc1 from [~JPercivall]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=b8813cb ]

NIFI-2498-rc1 Ignore failing test for Beta


> Perform Release Management Functions for 1.0.0-BETA
> ---
>
> Key: NIFI-2498
> URL: https://issues.apache.org/jira/browse/NIFI-2498
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>




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

[jira] [Commented] (NIFI-2498) Perform Release Management Functions for 1.0.0-BETA

[ASF subversion and git services (JIRA)]

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

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

Commit 8abcf2ef71334ce8861a81d50f1705b26852a06f in nifi's branch 
refs/heads/NIFI-2498-rc1 from [~JPercivall]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8abcf2e ]

NIFI-2498-rc1 prepare release nifi-1.0.0-BETA-RC1


> Perform Release Management Functions for 1.0.0-BETA
> ---
>
> Key: NIFI-2498
> URL: https://issues.apache.org/jira/browse/NIFI-2498
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>




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

[jira] [Updated] (NIFI-2504) NiFi fails to connect to the existing RPG after export/import from template.

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky updated NIFI-2504:
---
Description: When instantiating a flow from the template that was exported 
from the existing relationship to an RPG, such relationship fails to connect 
upon the import due to id missmatch of the actual input port and the id of the 
port referenced in the exported template.  (was: NIFI build Aug.5th. 

after exporting a template (GenerateFF -> RPG), the following UUID of my input 
port: 228486a6-0156-1000--6cece7a9

becomes: 228486a6-0156-1000--

this is causing a problem where data cannot be delivered via S2S because of 
non-matched UUIDs of the input port )

> NiFi fails to connect to the existing RPG after export/import from template.
> 
>
> Key: NIFI-2504
> URL: https://issues.apache.org/jira/browse/NIFI-2504
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Haimo Liu
>Assignee: Oleg Zhurakousky
>Priority: Blocker
> Fix For: 1.0.0
>
>
> When instantiating a flow from the template that was exported from the 
> existing relationship to an RPG, such relationship fails to connect upon the 
> import due to id missmatch of the actual input port and the id of the port 
> referenced in the exported template.



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

[jira] [Commented] (NIFI-2468) Address inconsistent placement of action buttons above tables; minor style edits

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2468: Improved UI consistency.

- Addressing comments from PR. Moving new service button below the tab pane. 
(+2 squashed commits)
Squashed commits:
[f746d09] NIFI-2468:
- Addressing numerous inconsistencies throughout the UI (button placement above 
tables, timestamp styles, etc)
[7d1fb09] addressing some inconsistencies

This closes #794.

Signed-off-by: Andy LoPresto 


> Address inconsistent placement of action buttons above tables; minor style 
> edits
> 
>
> Key: NIFI-2468
> URL: https://issues.apache.org/jira/browse/NIFI-2468
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>
> Use the current Data Provenance table as a model:
> * The inputs (Filter, filter type combo) sit directly on top of the table 
> header (no space between them and the table)
> * The search button sits 4px above the table
> If there are multiple buttons (e.g., in Flow History shell), separate by 2px 
> like buttons in the Navigate and Operate palettes
> OTHER RELATED NOTES
> Configure Processor > Properties tab – Add button icon sits higher (within 
> the button); it is not vertically centered like others
> Controller Service, Reporting Task Add buttons are above the tabs. They 
> should sit above the corresponding table like all others.
> MISC STYLE EDITS
> .combo-text {
> ADD font-weight: normal;
> #general-process-group-configuration input, 
> #general-process-group-configuration textarea {
> REMOVE font-size: 11px!important;
> REMOVE font-family: Verdana;
> #general-settings input {
> REMOVE font-size: 11px!important;
> REMOVE font-family: Verdana;
> All input 'placeholder's should consistently use color:#728E9B
> #settings-last-refreshed {
> CHANGE font-weight: 500;
> .setting-field {
> ADD font-weight: 500;
> .setting-name
> ADD text-transform: capitalize;
> Still seeing some instances where values (color:#775351) are either normal or 
> bold in weight
> * All values should be font-weight:500;



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

[jira] [Commented] (NIFI-2468) Address inconsistent placement of action buttons above tables; minor style edits

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2468: Improved UI consistency.

- Addressing comments from PR. Moving new service button below the tab pane. 
(+2 squashed commits)
Squashed commits:
[f746d09] NIFI-2468:
- Addressing numerous inconsistencies throughout the UI (button placement above 
tables, timestamp styles, etc)
[7d1fb09] addressing some inconsistencies

This closes #794.

Signed-off-by: Andy LoPresto 


> Address inconsistent placement of action buttons above tables; minor style 
> edits
> 
>
> Key: NIFI-2468
> URL: https://issues.apache.org/jira/browse/NIFI-2468
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>
> Use the current Data Provenance table as a model:
> * The inputs (Filter, filter type combo) sit directly on top of the table 
> header (no space between them and the table)
> * The search button sits 4px above the table
> If there are multiple buttons (e.g., in Flow History shell), separate by 2px 
> like buttons in the Navigate and Operate palettes
> OTHER RELATED NOTES
> Configure Processor > Properties tab – Add button icon sits higher (within 
> the button); it is not vertically centered like others
> Controller Service, Reporting Task Add buttons are above the tabs. They 
> should sit above the corresponding table like all others.
> MISC STYLE EDITS
> .combo-text {
> ADD font-weight: normal;
> #general-process-group-configuration input, 
> #general-process-group-configuration textarea {
> REMOVE font-size: 11px!important;
> REMOVE font-family: Verdana;
> #general-settings input {
> REMOVE font-size: 11px!important;
> REMOVE font-family: Verdana;
> All input 'placeholder's should consistently use color:#728E9B
> #settings-last-refreshed {
> CHANGE font-weight: 500;
> .setting-field {
> ADD font-weight: 500;
> .setting-name
> ADD text-transform: capitalize;
> Still seeing some instances where values (color:#775351) are either normal or 
> bold in weight
> * All values should be font-weight:500;



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

[GitHub] nifi issue #794: UI inconsistencies

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/794
  
Squashed, merged, closed. @scottyaslan got the credit in the commit. Sorry 
to ruin your stats, @mcgilman.  


---
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 #794: UI inconsistencies

[asfgit]

Github user asfgit closed the pull request at:

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


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

[jira] [Assigned] (NIFI-2504) UUIDs are not kept correctly in templates

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky reassigned NIFI-2504:
--

Assignee: Oleg Zhurakousky

> UUIDs are not kept correctly in templates
> -
>
> Key: NIFI-2504
> URL: https://issues.apache.org/jira/browse/NIFI-2504
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Haimo Liu
>Assignee: Oleg Zhurakousky
>Priority: Blocker
> Fix For: 1.0.0
>
>
> NIFI build Aug.5th. 
> after exporting a template (GenerateFF -> RPG), the following UUID of my 
> input port: 228486a6-0156-1000--6cece7a9
> becomes: 228486a6-0156-1000--
> this is causing a problem where data cannot be delivered via S2S because of 
> non-matched UUIDs of the input port 



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

[jira] [Updated] (NIFI-2504) UUIDs are not kept correctly in templates

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky updated NIFI-2504:
---
Fix Version/s: 1.0.0

> UUIDs are not kept correctly in templates
> -
>
> Key: NIFI-2504
> URL: https://issues.apache.org/jira/browse/NIFI-2504
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Haimo Liu
>Priority: Blocker
> Fix For: 1.0.0
>
>
> NIFI build Aug.5th. 
> after exporting a template (GenerateFF -> RPG), the following UUID of my 
> input port: 228486a6-0156-1000--6cece7a9
> becomes: 228486a6-0156-1000--
> this is causing a problem where data cannot be delivered via S2S because of 
> non-matched UUIDs of the input port 



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

[jira] [Commented] (NIFI-2494) Remove extraneous text that shows on banner line

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2494:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/793
  
@jskora Thanks for the PR. I just tried it out and was able to replicate 
the issue. However, with your proposed change, the heading text on the 
Controller Settings dialog is missing. This is accessed through the global menu 
and selecting 'Controller Settings'.

I think the underlying issue is that the default visibility is not being 
set on the settings dialog [1]. By adding `class="hidden"` to the settings div, 
I believe the issue is resolved. Would you mind trying that locally and if you 
agree update the PR?

Thanks again!

[1] 
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/WEB-INF/partials/canvas/settings-content.jsp#L18
 


> Remove extraneous text that shows on banner line
> 
>
> Key: NIFI-2494
> URL: https://issues.apache.org/jira/browse/NIFI-2494
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Trivial
>
> The words "NiFi Settings" appear on the top left of the page, on the banner 
> line.  They appear to be included in the page render and the banner message 
> is rendered as background so the text is not overwritten.



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

[GitHub] nifi issue #793: NIFI-2494 Remove extraneous text that shows on banner line

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/793
  
@jskora Thanks for the PR. I just tried it out and was able to replicate 
the issue. However, with your proposed change, the heading text on the 
Controller Settings dialog is missing. This is accessed through the global menu 
and selecting 'Controller Settings'.

I think the underlying issue is that the default visibility is not being 
set on the settings dialog [1]. By adding `class="hidden"` to the settings div, 
I believe the issue is resolved. Would you mind trying that locally and if you 
agree update the PR?

Thanks again!

[1] 
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/WEB-INF/partials/canvas/settings-content.jsp#L18
 


---
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-2502) Update Multi-tenant Authorization section in Admin Guide for addition of data policies

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2502:
--

GitHub user andrewmlim opened a pull request:

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

NIFI-2502 Update Multi-tenant Authorization section in Admin Guide fo…

…r addition of data policies

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

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

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

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


commit d8e46686f4191d8a1d648233defda397940f9e77
Author: Andrew Lim 
Date:   2016-08-05T18:44:39Z

NIFI-2502 Update Multi-tenant Authorization section in Admin Guide for 
addition of data policies




> Update Multi-tenant Authorization section in Admin Guide for addition of data 
> policies
> --
>
> Key: NIFI-2502
> URL: https://issues.apache.org/jira/browse/NIFI-2502
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> The "view the data" and "modify the data" policies need to be included in the 
> Admin Guide.  Also, related screenshots need to be updated.
> Lastly, adding a table that shows Legacy roles and what policies they are 
> given.



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

[GitHub] nifi pull request #797: NIFI-2502 Update Multi-tenant Authorization section ...

[andrewmlim]

GitHub user andrewmlim opened a pull request:

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

NIFI-2502 Update Multi-tenant Authorization section in Admin Guide fo…

…r addition of data policies

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

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

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

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


commit d8e46686f4191d8a1d648233defda397940f9e77
Author: Andrew Lim 
Date:   2016-08-05T18:44:39Z

NIFI-2502 Update Multi-tenant Authorization section in Admin Guide for 
addition of data policies




---
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-2502) Update Multi-tenant Authorization section in Admin Guide for addition of data policies

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2502:
-
Summary: Update Multi-tenant Authorization section in Admin Guide for 
addition of data policies  (was: Update Multi-tenant Authorization section in 
Admin Guide for recent changes)

> Update Multi-tenant Authorization section in Admin Guide for addition of data 
> policies
> --
>
> Key: NIFI-2502
> URL: https://issues.apache.org/jira/browse/NIFI-2502
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> The "view the data" and "modify the data" policies need to be included in the 
> Admin Guide.  Also, related screenshots need to be updated.
> Lastly, adding a table that shows Legacy roles and what policies they are 
> given.



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

[jira] [Assigned] (NIFI-2502) Update Multi-tenant Authorization section in Admin Guide for recent changes

[Andrew Lim (JIRA)]

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

Andrew Lim reassigned NIFI-2502:


Assignee: Andrew Lim

> Update Multi-tenant Authorization section in Admin Guide for recent changes
> ---
>
> Key: NIFI-2502
> URL: https://issues.apache.org/jira/browse/NIFI-2502
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> The "view the data" and "modify the data" policies need to be included in the 
> Admin Guide.  Also, related screenshots need to be updated.
> Lastly, adding a table that shows Legacy roles and what policies they are 
> given.



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

[jira] [Created] (NIFI-2502) Update Multi-tenant Authorization section in Admin Guide for recent changes

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2502:


 Summary: Update Multi-tenant Authorization section in Admin Guide 
for recent changes
 Key: NIFI-2502
 URL: https://issues.apache.org/jira/browse/NIFI-2502
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Documentation & Website
Affects Versions: 1.0.0
Reporter: Andrew Lim
 Fix For: 1.0.0


The "view the data" and "modify the data" policies need to be included in the 
Admin Guide.  Also, related screenshots need to be updated.

Lastly, adding a table that shows Legacy roles and what policies they are given.



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

[jira] [Updated] (NIFI-2412) Allow user to set serializer and de serializer in publish and consume kafka processors

[Oleg Zhurakousky (JIRA)]

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

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

Applied to both master and 0.x

> Allow user to set serializer and de serializer in publish and consume kafka 
> processors
> --
>
> Key: NIFI-2412
> URL: https://issues.apache.org/jira/browse/NIFI-2412
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0, 1.0.0-Beta
>
>
> Publish kafka today sets key and value serializer to class 
> org.apache.kafka.common.serialization.ByteArraySerializer
> Even if the user passes different values in the processor config they get 
> overwritten.
> We should allow dynamic values for serializer and de serializer as needed.



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

[jira] [Updated] (NIFI-2322) ConsumeKafka gets stuck (cannot be stopped)

[Oleg Zhurakousky (JIRA)]

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

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

Applied to both master and 0.x

> ConsumeKafka gets stuck (cannot be stopped)
> ---
>
> Key: NIFI-2322
> URL: https://issues.apache.org/jira/browse/NIFI-2322
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Haimo Liu
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0, 1.0.0-Beta
>
> Attachments: Screen Shot 2016-07-19 at 2.14.32 PM.png, Screen Shot 
> 2016-07-19 at 2.14.48 PM.png
>
>
> If kafka broker path is invalid or inaccurate, ConsumeKafka processor can get 
> stuck (concurrent tasks cannot be stopped in a clustered mode). Please refer 
> to the images in the attachment. It appears that a configurable timeout 
> property would potentially solve the problem.



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

[jira] [Commented] (NIFI-2322) ConsumeKafka gets stuck (cannot be stopped)

[ASF subversion and git services (JIRA)]

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

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

Commit 46a9bba31d650f9c45284ca97c9cf7b1150aaa22 in nifi's branch refs/heads/0.x 
from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=46a9bba ]

NIFI-2322, NIFI-2423, NIFI-2412 Kafka improvements
- Fixed KafkaConsumer's connection block when broker is not available
- Fixed Serializer/Deserializer configs in both Consume/Publish Kafka
- Added sensitive properties for SSL ket/trust stores

NIFI-2322 fixed tests


> ConsumeKafka gets stuck (cannot be stopped)
> ---
>
> Key: NIFI-2322
> URL: https://issues.apache.org/jira/browse/NIFI-2322
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Haimo Liu
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0, 1.0.0-Beta
>
> Attachments: Screen Shot 2016-07-19 at 2.14.32 PM.png, Screen Shot 
> 2016-07-19 at 2.14.48 PM.png
>
>
> If kafka broker path is invalid or inaccurate, ConsumeKafka processor can get 
> stuck (concurrent tasks cannot be stopped in a clustered mode). Please refer 
> to the images in the attachment. It appears that a configurable timeout 
> property would potentially solve the problem.



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

[jira] [Commented] (NIFI-2423) Add a sensitive property to store the trust store password in the consume/publish kafka processors

[ASF subversion and git services (JIRA)]

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

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

Commit 46a9bba31d650f9c45284ca97c9cf7b1150aaa22 in nifi's branch refs/heads/0.x 
from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=46a9bba ]

NIFI-2322, NIFI-2423, NIFI-2412 Kafka improvements
- Fixed KafkaConsumer's connection block when broker is not available
- Fixed Serializer/Deserializer configs in both Consume/Publish Kafka
- Added sensitive properties for SSL ket/trust stores

NIFI-2322 fixed tests


> Add a sensitive property to store the trust store password in the 
> consume/publish kafka processors
> --
>
> Key: NIFI-2423
> URL: https://issues.apache.org/jira/browse/NIFI-2423
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.0.0, 0.8.0
>
> Attachments: 
> 0001-NIFI-2423-Make-use-of-the-SSLContextService-to-provi.patch
>
>
> When user configures kafka processors to interact with SSL enabled protocol 
> they need to set additional configs.
> ssl.truststore.location and ssl.truststore.password. 
> Today the trust store password is clear text. We should make that a default 
> property and make it sensitive.



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

[jira] [Commented] (NIFI-2412) Allow user to set serializer and de serializer in publish and consume kafka processors

[ASF subversion and git services (JIRA)]

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

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

Commit 46a9bba31d650f9c45284ca97c9cf7b1150aaa22 in nifi's branch refs/heads/0.x 
from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=46a9bba ]

NIFI-2322, NIFI-2423, NIFI-2412 Kafka improvements
- Fixed KafkaConsumer's connection block when broker is not available
- Fixed Serializer/Deserializer configs in both Consume/Publish Kafka
- Added sensitive properties for SSL ket/trust stores

NIFI-2322 fixed tests


> Allow user to set serializer and de serializer in publish and consume kafka 
> processors
> --
>
> Key: NIFI-2412
> URL: https://issues.apache.org/jira/browse/NIFI-2412
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0, 1.0.0-Beta
>
>
> Publish kafka today sets key and value serializer to class 
> org.apache.kafka.common.serialization.ByteArraySerializer
> Even if the user passes different values in the processor config they get 
> overwritten.
> We should allow dynamic values for serializer and de serializer as needed.



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

[jira] [Commented] (NIFI-2322) ConsumeKafka gets stuck (cannot be stopped)

[ASF subversion and git services (JIRA)]

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

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

Commit 46a9bba31d650f9c45284ca97c9cf7b1150aaa22 in nifi's branch refs/heads/0.x 
from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=46a9bba ]

NIFI-2322, NIFI-2423, NIFI-2412 Kafka improvements
- Fixed KafkaConsumer's connection block when broker is not available
- Fixed Serializer/Deserializer configs in both Consume/Publish Kafka
- Added sensitive properties for SSL ket/trust stores

NIFI-2322 fixed tests


> ConsumeKafka gets stuck (cannot be stopped)
> ---
>
> Key: NIFI-2322
> URL: https://issues.apache.org/jira/browse/NIFI-2322
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Haimo Liu
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0, 1.0.0-Beta
>
> Attachments: Screen Shot 2016-07-19 at 2.14.32 PM.png, Screen Shot 
> 2016-07-19 at 2.14.48 PM.png
>
>
> If kafka broker path is invalid or inaccurate, ConsumeKafka processor can get 
> stuck (concurrent tasks cannot be stopped in a clustered mode). Please refer 
> to the images in the attachment. It appears that a configurable timeout 
> property would potentially solve the problem.



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

[jira] [Commented] (NIFI-2423) Add a sensitive property to store the trust store password in the consume/publish kafka processors

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2423: Make use of the SSLContextService to provide SSL information

Signed-off-by: Oleg Zhurakousky 


> Add a sensitive property to store the trust store password in the 
> consume/publish kafka processors
> --
>
> Key: NIFI-2423
> URL: https://issues.apache.org/jira/browse/NIFI-2423
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.0.0, 0.8.0
>
> Attachments: 
> 0001-NIFI-2423-Make-use-of-the-SSLContextService-to-provi.patch
>
>
> When user configures kafka processors to interact with SSL enabled protocol 
> they need to set additional configs.
> ssl.truststore.location and ssl.truststore.password. 
> Today the trust store password is clear text. We should make that a default 
> property and make it sensitive.



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

[jira] [Updated] (NIFI-2322) ConsumeKafka gets stuck (cannot be stopped)

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2322:
---
Fix Version/s: 1.0.0-Beta

> ConsumeKafka gets stuck (cannot be stopped)
> ---
>
> Key: NIFI-2322
> URL: https://issues.apache.org/jira/browse/NIFI-2322
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Haimo Liu
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0, 1.0.0-Beta
>
> Attachments: Screen Shot 2016-07-19 at 2.14.32 PM.png, Screen Shot 
> 2016-07-19 at 2.14.48 PM.png
>
>
> If kafka broker path is invalid or inaccurate, ConsumeKafka processor can get 
> stuck (concurrent tasks cannot be stopped in a clustered mode). Please refer 
> to the images in the attachment. It appears that a configurable timeout 
> property would potentially solve the problem.



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

[jira] [Commented] (NIFI-2322) ConsumeKafka gets stuck (cannot be stopped)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2322:
--

Github user olegz closed the pull request at:

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


> ConsumeKafka gets stuck (cannot be stopped)
> ---
>
> Key: NIFI-2322
> URL: https://issues.apache.org/jira/browse/NIFI-2322
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Haimo Liu
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
> Attachments: Screen Shot 2016-07-19 at 2.14.32 PM.png, Screen Shot 
> 2016-07-19 at 2.14.48 PM.png
>
>
> If kafka broker path is invalid or inaccurate, ConsumeKafka processor can get 
> stuck (concurrent tasks cannot be stopped in a clustered mode). Please refer 
> to the images in the attachment. It appears that a configurable timeout 
> property would potentially solve the problem.



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

[jira] [Commented] (NIFI-2412) Allow user to set serializer and de serializer in publish and consume kafka processors

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2322, NIFI-2423, NIFI-2412 Kafka improvements
- Fixed KafkaConsumer's connection block when broker is not available
- Fixed Serializer/Deserializer configs in both Consume/Publish Kafka
- Added sensitive properties for SSL ket/trust stores

NIFI-2322 fixed tests


> Allow user to set serializer and de serializer in publish and consume kafka 
> processors
> --
>
> Key: NIFI-2412
> URL: https://issues.apache.org/jira/browse/NIFI-2412
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
>
> Publish kafka today sets key and value serializer to class 
> org.apache.kafka.common.serialization.ByteArraySerializer
> Even if the user passes different values in the processor config they get 
> overwritten.
> We should allow dynamic values for serializer and de serializer as needed.



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

[jira] [Commented] (NIFI-2423) Add a sensitive property to store the trust store password in the consume/publish kafka processors

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2423: Make use of the SSLContextService to provide SSL information

Signed-off-by: Oleg Zhurakousky 


> Add a sensitive property to store the trust store password in the 
> consume/publish kafka processors
> --
>
> Key: NIFI-2423
> URL: https://issues.apache.org/jira/browse/NIFI-2423
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.0.0, 0.8.0
>
> Attachments: 
> 0001-NIFI-2423-Make-use-of-the-SSLContextService-to-provi.patch
>
>
> When user configures kafka processors to interact with SSL enabled protocol 
> they need to set additional configs.
> ssl.truststore.location and ssl.truststore.password. 
> Today the trust store password is clear text. We should make that a default 
> property and make it sensitive.



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

[jira] [Commented] (NIFI-2423) Add a sensitive property to store the trust store password in the consume/publish kafka processors

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2322, NIFI-2423, NIFI-2412 Kafka improvements
- Fixed KafkaConsumer's connection block when broker is not available
- Fixed Serializer/Deserializer configs in both Consume/Publish Kafka
- Added sensitive properties for SSL ket/trust stores

NIFI-2322 fixed tests


> Add a sensitive property to store the trust store password in the 
> consume/publish kafka processors
> --
>
> Key: NIFI-2423
> URL: https://issues.apache.org/jira/browse/NIFI-2423
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: Arpit Gupta
>Assignee: Oleg Zhurakousky
>Priority: Critical
> Fix For: 1.0.0, 0.8.0
>
> Attachments: 
> 0001-NIFI-2423-Make-use-of-the-SSLContextService-to-provi.patch
>
>
> When user configures kafka processors to interact with SSL enabled protocol 
> they need to set additional configs.
> ssl.truststore.location and ssl.truststore.password. 
> Today the trust store password is clear text. We should make that a default 
> property and make it sensitive.



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

[jira] [Commented] (NIFI-2322) ConsumeKafka gets stuck (cannot be stopped)

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2322, NIFI-2423, NIFI-2412 Kafka improvements
- Fixed KafkaConsumer's connection block when broker is not available
- Fixed Serializer/Deserializer configs in both Consume/Publish Kafka
- Added sensitive properties for SSL ket/trust stores

NIFI-2322 fixed tests


> ConsumeKafka gets stuck (cannot be stopped)
> ---
>
> Key: NIFI-2322
> URL: https://issues.apache.org/jira/browse/NIFI-2322
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Haimo Liu
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0, 0.8.0
>
> Attachments: Screen Shot 2016-07-19 at 2.14.32 PM.png, Screen Shot 
> 2016-07-19 at 2.14.48 PM.png
>
>
> If kafka broker path is invalid or inaccurate, ConsumeKafka processor can get 
> stuck (concurrent tasks cannot be stopped in a clustered mode). Please refer 
> to the images in the attachment. It appears that a configurable timeout 
> property would potentially solve the problem.



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

[GitHub] nifi pull request #741: NIFI-2322, NIFI-2423, NIFI-2412 Kafka improvements

[olegz]

Github user olegz closed the pull request at:

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


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

[Matthew Clarke (JIRA)]

Matthew Clarke created NIFI-2500:


 Summary: Allow request buffer to be configurable on 
HandleHTTPRequest processor
 Key: NIFI-2500
 URL: https://issues.apache.org/jira/browse/NIFI-2500
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core Framework
Affects Versions: 0.6.1
Reporter: Matthew Clarke
Priority: Critical


The request buffer for the HandleHTTPRequest buffer is hard coded to 50.  For 
environments where bursts of requests can come in that exceed that threshold, 
the processor will trigger Service Unavailable responses. Users should be able 
to increase that buffer to meet their dataflow needs similar to how the 
ConsumeMQTT processor works.



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

[jira] [Commented] (NIFI-1148) Add processor to GetEmail supporting IMAP and POP3

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1148:
--

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/710
  
@mattyb149 all the suggested changes have been addressed in the last 
commit. I've also included in the additional documentation sample configuration 
for GMail, so you can use it to play around/test.


> Add processor to GetEmail supporting IMAP and POP3
> --
>
> Key: NIFI-1148
> URL: https://issues.apache.org/jira/browse/NIFI-1148
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



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

[GitHub] nifi issue #794: UI inconsistencies

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/794
  
Thanks @moranr. Will update 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.
---

[GitHub] nifi issue #710: NIFI-1148 added IMAP/POP3 support

[olegz]

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/710
  
@mattyb149 all the suggested changes have been addressed in the last 
commit. I've also included in the additional documentation sample configuration 
for GMail, so you can use it to play around/test.


---
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-2406) Rare start-up problems resulting in all nodes disconnected

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2406:
-
Fix Version/s: 1.0.0

> Rare start-up problems resulting in all nodes disconnected
> --
>
> Key: NIFI-2406
> URL: https://issues.apache.org/jira/browse/NIFI-2406
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Fix For: 1.0.0
>
> Attachments: logs.tar.gz
>
>
> While testing PR 678[1], I came across a time where all the nodes were in a 
> disconnected state and each were in a weird state of heartbeating but not 
> connected.
> Also in the logs there were ~1000 lines of:
> 2016-07-26 11:38:07,841 INFO [Leader Election Notification Thread-1] 
> o.a.n.c.l.e.CuratorLeaderElectionManager 
> org.apache.nifi.controller.leader.election.CuratorLeaderElectionManager$ElectionListener@24fae8c6
>  This node has been elected Leader for Role 'Cluster Coordinator'
> This message only gets called here[2] which is a call back for ZK. Also there 
> were many log messages of:
> 2016-07-26 11:54:07,910 WARN [Clustering Tasks Thread-1] 
> o.a.n.c.c.node.NodeClusterCoordinator Failed to determine which node is 
> elected active Cluster Coordinator: ZooKeeper reports the address as 
> localhost:6001, but there is no node with this address
> I believe this is a problem with ZK/NiFi that existed before this PR and not 
> directly related to the PR being reviewed. I will attach a tar of the 3 
> node's logs.
> [1] https://github.com/apache/nifi/pull/678
> [2] 
> https://github.com/apache/nifi/blame/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/leader/election/CuratorLeaderElectionManager.java#L220-L220



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

[jira] [Resolved] (NIFI-2497) testOutputDirectory fails on Windows

[Oleg Zhurakousky (JIRA)]

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

Oleg Zhurakousky resolved NIFI-2497.

Resolution: Fixed

> testOutputDirectory fails on Windows
> 
>
> Key: NIFI-2497
> URL: https://issues.apache.org/jira/browse/NIFI-2497
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>Priority: Blocker
> Fix For: 1.0.0, 1.0.0-Beta
>
>
> In nifi-toolkit-tls, the test testOutputDirectory fails every time due to a 
> mismatch in the expected output.
> This test needs to be changed to be file system agnostic.
> https://github.com/apache/nifi/blob/master/nifi-toolkit/nifi-toolkit-tls/src/test/java/org/apache/nifi/toolkit/tls/standalone/TlsToolkitStandaloneCommandLineTest.java#L132-L132



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

[GitHub] nifi pull request #795: NIFI-2497 Fixing testOutputDirectory to be system ag...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2497) testOutputDirectory fails on Windows

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2497:
--

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/795
  
+1. Merged


> testOutputDirectory fails on Windows
> 
>
> Key: NIFI-2497
> URL: https://issues.apache.org/jira/browse/NIFI-2497
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>Priority: Blocker
> Fix For: 1.0.0, 1.0.0-Beta
>
>
> In nifi-toolkit-tls, the test testOutputDirectory fails every time due to a 
> mismatch in the expected output.
> This test needs to be changed to be file system agnostic.
> https://github.com/apache/nifi/blob/master/nifi-toolkit/nifi-toolkit-tls/src/test/java/org/apache/nifi/toolkit/tls/standalone/TlsToolkitStandaloneCommandLineTest.java#L132-L132



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

[jira] [Commented] (NIFI-2497) testOutputDirectory fails on Windows

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2497:
--

Github user asfgit closed the pull request at:

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


> testOutputDirectory fails on Windows
> 
>
> Key: NIFI-2497
> URL: https://issues.apache.org/jira/browse/NIFI-2497
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>Priority: Blocker
> Fix For: 1.0.0, 1.0.0-Beta
>
>
> In nifi-toolkit-tls, the test testOutputDirectory fails every time due to a 
> mismatch in the expected output.
> This test needs to be changed to be file system agnostic.
> https://github.com/apache/nifi/blob/master/nifi-toolkit/nifi-toolkit-tls/src/test/java/org/apache/nifi/toolkit/tls/standalone/TlsToolkitStandaloneCommandLineTest.java#L132-L132



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

[GitHub] nifi pull request #795: NIFI-2497 Fixing testOutputDirectory to be system ag...

[JPercivall]

GitHub user JPercivall opened a pull request:

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

NIFI-2497 Fixing testOutputDirectory to be system agnostic



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

$ git pull https://github.com/JPercivall/nifi NIFI-2497

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

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


commit 6e2d563a0dac7bdd3910e2e380c734b3e6604457
Author: Joseph Percivall 
Date:   2016-08-05T16:06:51Z

NIFI-2497 Fixing testOutputDirectory to be system agnostic




---
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-2497) testOutputDirectory fails on Windows

[Joseph Percivall (JIRA)]

Joseph Percivall created NIFI-2497:
--

 Summary: testOutputDirectory fails on Windows
 Key: NIFI-2497
 URL: https://issues.apache.org/jira/browse/NIFI-2497
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Joseph Percivall
Assignee: Joseph Percivall
Priority: Blocker
 Fix For: 1.0.0, 1.0.0-Beta


In nifi-toolkit-tls, the test testOutputDirectory fails every time due to a 
mismatch in the expected output.

This test needs to be changed to be file system agnostic.

https://github.com/apache/nifi/blob/master/nifi-toolkit/nifi-toolkit-tls/src/test/java/org/apache/nifi/toolkit/tls/standalone/TlsToolkitStandaloneCommandLineTest.java#L132-L132



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

[jira] [Commented] (NIFI-1148) Add processor to GetEmail supporting IMAP and POP3

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1148:
--

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/710
  
@mattyb149 I was just trying to reproduce the issue with the hanging thread 
you described above in relation to ConsumePop3, but I can't. Are you sure that 
what you saw is related to this processor or NiFo in general?


> Add processor to GetEmail supporting IMAP and POP3
> --
>
> Key: NIFI-1148
> URL: https://issues.apache.org/jira/browse/NIFI-1148
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



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

[GitHub] nifi issue #710: NIFI-1148 added IMAP/POP3 support

[olegz]

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/710
  
@mattyb149 I was just trying to reproduce the issue with the hanging thread 
you described above in relation to ConsumePop3, but I can't. Are you sure that 
what you saw is related to this processor or NiFo in general?


---
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 #794: UI inconsistencies

[mcgilman]

GitHub user mcgilman opened a pull request:

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

UI inconsistencies

NiFi-2468:
- Addressing numerous inconsistencies throughout the UI (button placement 
above tables, timestamp styles, etc)

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

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

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

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


commit c68c4da419574fbbe42f8289c94c6a33543840e6
Author: Scott Aslan 
Date:   2016-08-03T21:19:50Z

addressing some inconsistencies

commit cfb07fba16ee57d3d53216ed35fa9aeacd1ec1d2
Author: Matt Gilman 
Date:   2016-08-05T15:35:28Z

NIFI-2468:
- Addressing numerous inconsistencies throughout the UI (button placement 
above tables, timestamp styles, etc)




---
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-1148) Add processor to GetEmail supporting IMAP and POP3

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1148:
--

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

https://github.com/apache/nifi/pull/710#discussion_r73712664
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/java/org/apache/nifi/processors/email/ConsumeIMAP.java
 ---
@@ -0,0 +1,91 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.email;
+
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.List;
+
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.springframework.integration.mail.ImapMailReceiver;
+
+@InputRequirement(Requirement.INPUT_FORBIDDEN)
+@CapabilityDescription("Consumes messages from Email Server using IMAP 
protocol. "
++ "The raw-bytes of each received email message are written as 
contents of the FlowFile")
+@Tags({ "Email", "Imap", "Get", "Ingest", "Ingress", "Message", "Consume" 
})
+public class ConsumeIMAP extends AbstractEmailProcessor {
+
+public static final PropertyDescriptor SHOULD_MARK_READ = new 
PropertyDescriptor.Builder()
+.name("Mark Messages as Read")
+.description("Specify if messages should be marked as read 
after retrieval.")
+.required(true)
+.allowableValues("true", "false")
+.defaultValue("false")
+.addValidator(StandardValidators.BOOLEAN_VALIDATOR)
+.build();
+public static final PropertyDescriptor USE_SSL = new 
PropertyDescriptor.Builder()
+.name("Use SSL")
+.description("Specifies if IMAP connection must be obtained 
via SSL encypted connection (i.e., IMAPS)")
--- End diff --

@mattyb149  Actually you're not missing anything and there is no extra 
configuration on the cline side (NIFI). This is all derived form the email 
server capabilities and how it's configured. For example if you want to test it 
with your existing GMail you would have to use "imaps". That is because Google 
has set it up as such. Does that help?


> Add processor to GetEmail supporting IMAP and POP3
> --
>
> Key: NIFI-1148
> URL: https://issues.apache.org/jira/browse/NIFI-1148
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



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

[jira] [Commented] (NIFI-1148) Add processor to GetEmail supporting IMAP and POP3

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1148:
--

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

https://github.com/apache/nifi/pull/710#discussion_r73710841
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/java/org/apache/nifi/processors/email/AbstractEmailProcessor.java
 ---
@@ -0,0 +1,400 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.email;
+
+import java.io.IOException;
+import java.io.OutputStream;
+import java.io.UnsupportedEncodingException;
+import java.net.URLEncoder;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map.Entry;
+import java.util.Properties;
+import java.util.Set;
+import java.util.concurrent.ArrayBlockingQueue;
+import java.util.concurrent.BlockingQueue;
+import java.util.concurrent.TimeUnit;
+
+import javax.mail.Address;
+import javax.mail.Flags;
+import javax.mail.Message;
+import javax.mail.MessagingException;
+
+import org.apache.nifi.annotation.lifecycle.OnStopped;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.io.OutputStreamCallback;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+import org.springframework.beans.factory.support.StaticListableBeanFactory;
+import org.springframework.integration.mail.AbstractMailReceiver;
+import org.springframework.util.Assert;
+import org.springframework.util.StreamUtils;
+
+/**
+ * Base processor for implementing processors to consume messages from 
Email
+ * servers using Spring Integration libraries.
+ *
+ * @param 
+ *the type of {@link AbstractMailReceiver}.
+ */
+abstract class AbstractEmailProcessor 
extends AbstractProcessor {
+
+public static final PropertyDescriptor HOST = new 
PropertyDescriptor.Builder()
+.name("Host Name")
--- End diff --

I can do that, especially since I am the one advocating it ;)



> Add processor to GetEmail supporting IMAP and POP3
> --
>
> Key: NIFI-1148
> URL: https://issues.apache.org/jira/browse/NIFI-1148
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> It is fairly common that users want to be able to acquire data via email.  
> This means both IMAP and POP3.  POP3 is easier as it is a sort of fire/forget 
> model whereas IMAP involves more state handling.  But in any event both modes 
> are important to support.



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

[GitHub] nifi pull request #710: NIFI-1148 added IMAP/POP3 support

[olegz]

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

https://github.com/apache/nifi/pull/710#discussion_r73710841
  
--- Diff: 
nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/java/org/apache/nifi/processors/email/AbstractEmailProcessor.java
 ---
@@ -0,0 +1,400 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.email;
+
+import java.io.IOException;
+import java.io.OutputStream;
+import java.io.UnsupportedEncodingException;
+import java.net.URLEncoder;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map.Entry;
+import java.util.Properties;
+import java.util.Set;
+import java.util.concurrent.ArrayBlockingQueue;
+import java.util.concurrent.BlockingQueue;
+import java.util.concurrent.TimeUnit;
+
+import javax.mail.Address;
+import javax.mail.Flags;
+import javax.mail.Message;
+import javax.mail.MessagingException;
+
+import org.apache.nifi.annotation.lifecycle.OnStopped;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.io.OutputStreamCallback;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+import org.springframework.beans.factory.support.StaticListableBeanFactory;
+import org.springframework.integration.mail.AbstractMailReceiver;
+import org.springframework.util.Assert;
+import org.springframework.util.StreamUtils;
+
+/**
+ * Base processor for implementing processors to consume messages from 
Email
+ * servers using Spring Integration libraries.
+ *
+ * @param 
+ *the type of {@link AbstractMailReceiver}.
+ */
+abstract class AbstractEmailProcessor 
extends AbstractProcessor {
+
+public static final PropertyDescriptor HOST = new 
PropertyDescriptor.Builder()
+.name("Host Name")
--- End diff --

I can do that, especially since I am the one advocating it ;)



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

[GitHub] nifi pull request #710: NIFI-1148 added IMAP/POP3 support

[olegz]

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

https://github.com/apache/nifi/pull/710#discussion_r73710769
  
--- Diff: nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/pom.xml 
---
@@ -1,73 +1,84 @@
 
-
-http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
-4.0.0

[jira] [Created] (NIFI-2495) testModifyIndexWhileSearching breaks Windows build

[Joseph Percivall (JIRA)]

Joseph Percivall created NIFI-2495:
--

 Summary: testModifyIndexWhileSearching breaks Windows build
 Key: NIFI-2495
 URL: https://issues.apache.org/jira/browse/NIFI-2495
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Joseph Percivall
Priority: Blocker
 Fix For: 1.0.0, 1.0.0-Beta


On Windows this[1] test fails every time with IoException[2] due to not being 
able to delete files because they are still in use.


[1] 
https://github.com/apache/nifi/blame/16348b071d361697f517397b2da2ea32c5599c11/nifi-nar-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/test/java/org/apache/nifi/provenance/TestPersistentProvenanceRepository.java#L489

[2] java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\6175506c-583b-4161-8c09-d1d6bdfbbe63\index-1470413655530\_0.cfs

at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:152)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
at 
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)



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

[jira] [Commented] (NIFI-2494) Remove extraneous text that shows on banner line

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2494:
--

Github user mcgilman commented on the issue:

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


> Remove extraneous text that shows on banner line
> 
>
> Key: NIFI-2494
> URL: https://issues.apache.org/jira/browse/NIFI-2494
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Trivial
>
> The words "NiFi Settings" appear on the top left of the page, on the banner 
> line.  They appear to be included in the page render and the banner message 
> is rendered as background so the text is not overwritten.



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

[GitHub] nifi issue #793: NIFI-2494 Remove extraneous text that shows on banner line

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/793
  
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-2491) ControllerService startup issue

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2491:
---

Similar to how processors should work the intent is that you're communicating 
you either want this thing to run or do not want it to run.  On each node how 
successful that will be such as when or if it will be truly running may differ 
but what should be consistent is that they're all trying to run.  So it should 
retry forever or until you disable/stop it.  The code for that is here:

  
https://github.com/apache/nifi/blob/0.x/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/service/StandardControllerServiceNode.java#L279-L299

That said, in looking at the code you link i can see why you're thinking it is 
a one-shot deal.  I'm still looking into how that code relates to what I linked 
above.  Are you not seeing it attempt to restart the services?


> ControllerService startup issue
> ---
>
> Key: NIFI-2491
> URL: https://issues.apache.org/jira/browse/NIFI-2491
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Brandon DeVries
>Priority: Minor
>
> In the process of testing NIFI-2160 and NIFI-2344, we found that if a 
> controller service throws some type of RuntimeException(e.g. 
> IllegalStateException) in its @OnEnabled method it will essentially "break 
> the chain" of startup of things that depend on it.  The end result is that in 
> a cluster, you can have a processor that is running on some nodes and stopped 
> on others.  This probably isn't the desired behavior.  In 
> StandardControllerServiceProvider\[1\] when thrown Exceptions are caught, we 
> should possibly retry enabling the service.  If it can't be enabled... we 
> might want to consider shutting down NiFi.  That's sort of extreme, but 
> allowing the cluster to enter an inconsistent state seems like a bad thing.  
> We could possibly also come up with some way of indicating there's an 
> inconsistency in the UI.  The proper solution will require some 
> consideration, but the issue needs to be addressed somehow.
> \[1\] 
> https://github.com/apache/nifi/blob/rel/nifi-0.7.0/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/service/StandardControllerServiceProvider.java#L320-L325



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

[jira] [Commented] (NIFI-2492) Processor startup issue

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2492:
---

also here is the 0.x link 
https://github.com/apache/nifi/blob/0.x/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/StandardProcessorNode.java#L1191-L1225

Should be the same.

> Processor startup issue
> ---
>
> Key: NIFI-2492
> URL: https://issues.apache.org/jira/browse/NIFI-2492
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Brandon DeVries
>Priority: Minor
>
> In the process of testing NIFI-2160 and NIFI-2344, we found that if a 
> processor throws an Exception (e.g. IllegalStateException) from its 
> @OnScheduled method, it will not resume its STARTED state.  In a cluster, 
> this could result in inconsistent state similar to NIFI-2491, and should 
> either not be allowed to happen (terminate the instance), or should be made 
> clear in the UI.



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

[jira] [Commented] (NIFI-2492) Processor startup issue

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2492:
---

[~devriesb] The notion of "I want this running" vs "I want this thing not 
running" is really what is getting captured when you start or stop a processor 
and that is what we must keep consistent in terms of managing the cluster.  The 
behavior that is intended for the case you've mentioned here should be that the 
processor is told to start, it throws an exception, that gets logged and a 
bulletin generated, and it will continue to try to start it over and over ever 
30 seconds or until the processor is told to stop.  Are you not seeing the 
bulletin and not seeing it continue to try?

https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/StandardProcessorNode.java#L1191-L1225

> Processor startup issue
> ---
>
> Key: NIFI-2492
> URL: https://issues.apache.org/jira/browse/NIFI-2492
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Brandon DeVries
>Priority: Minor
>
> In the process of testing NIFI-2160 and NIFI-2344, we found that if a 
> processor throws an Exception (e.g. IllegalStateException) from its 
> @OnScheduled method, it will not resume its STARTED state.  In a cluster, 
> this could result in inconsistent state similar to NIFI-2491, and should 
> either not be allowed to happen (terminate the instance), or should be made 
> clear in the UI.



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

[jira] [Updated] (NIFI-2493) If Port's scheduled state is not the same as cluster when a node joins, allow the node to join and update the Port

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2493:
-
Fix Version/s: (was: 1.1.0)
   1.0.0

> If Port's scheduled state is not the same as cluster when a node joins, allow 
> the node to join and update the Port
> --
>
> Key: NIFI-2493
> URL: https://issues.apache.org/jira/browse/NIFI-2493
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>




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

[jira] [Updated] (NIFI-2468) Address inconsistent placement of action buttons above tables; minor style edits

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-2468:
--
Fix Version/s: 1.0.0

> Address inconsistent placement of action buttons above tables; minor style 
> edits
> 
>
> Key: NIFI-2468
> URL: https://issues.apache.org/jira/browse/NIFI-2468
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>
> Use the current Data Provenance table as a model:
> * The inputs (Filter, filter type combo) sit directly on top of the table 
> header (no space between them and the table)
> * The search button sits 4px above the table
> If there are multiple buttons (e.g., in Flow History shell), separate by 2px 
> like buttons in the Navigate and Operate palettes
> OTHER RELATED NOTES
> Configure Processor > Properties tab – Add button icon sits higher (within 
> the button); it is not vertically centered like others
> Controller Service, Reporting Task Add buttons are above the tabs. They 
> should sit above the corresponding table like all others.
> MISC STYLE EDITS
> .combo-text {
> ADD font-weight: normal;
> #general-process-group-configuration input, 
> #general-process-group-configuration textarea {
> REMOVE font-size: 11px!important;
> REMOVE font-family: Verdana;
> #general-settings input {
> REMOVE font-size: 11px!important;
> REMOVE font-family: Verdana;
> All input 'placeholder's should consistently use color:#728E9B
> #settings-last-refreshed {
> CHANGE font-weight: 500;
> .setting-field {
> ADD font-weight: 500;
> .setting-name
> ADD text-transform: capitalize;
> Still seeing some instances where values (color:#775351) are either normal or 
> bold in weight
> * All values should be font-weight:500;



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

[jira] [Commented] (NIFI-2468) Address inconsistent placement of action buttons above tables; minor style edits

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2468:
--

Github user scottyaslan closed the pull request at:

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


> Address inconsistent placement of action buttons above tables; minor style 
> edits
> 
>
> Key: NIFI-2468
> URL: https://issues.apache.org/jira/browse/NIFI-2468
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
>
> Use the current Data Provenance table as a model:
> * The inputs (Filter, filter type combo) sit directly on top of the table 
> header (no space between them and the table)
> * The search button sits 4px above the table
> If there are multiple buttons (e.g., in Flow History shell), separate by 2px 
> like buttons in the Navigate and Operate palettes
> OTHER RELATED NOTES
> Configure Processor > Properties tab – Add button icon sits higher (within 
> the button); it is not vertically centered like others
> Controller Service, Reporting Task Add buttons are above the tabs. They 
> should sit above the corresponding table like all others.
> MISC STYLE EDITS
> .combo-text {
> ADD font-weight: normal;
> #general-process-group-configuration input, 
> #general-process-group-configuration textarea {
> REMOVE font-size: 11px!important;
> REMOVE font-family: Verdana;
> #general-settings input {
> REMOVE font-size: 11px!important;
> REMOVE font-family: Verdana;
> All input 'placeholder's should consistently use color:#728E9B
> #settings-last-refreshed {
> CHANGE font-weight: 500;
> .setting-field {
> ADD font-weight: 500;
> .setting-name
> ADD text-transform: capitalize;
> Still seeing some instances where values (color:#775351) are either normal or 
> bold in weight
> * All values should be font-weight:500;



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

[GitHub] nifi pull request #781: [NIFI-2468] addressing some inconsistencies

[scottyaslan]

Github user scottyaslan closed the pull request at:

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


---
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-2492) Processor startup issue

[Brandon DeVries (JIRA)]

Brandon DeVries created NIFI-2492:
-

 Summary: Processor startup issue
 Key: NIFI-2492
 URL: https://issues.apache.org/jira/browse/NIFI-2492
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Brandon DeVries
Priority: Minor


In the process of testing NIFI-2160 and NIFI-2344, we found that if a processor 
throws an Exception (e.g. IllegalStateException) from its @OnScheduled method, 
it will not resume its STARTED state.  In a cluster, this could result in 
inconsistent state similar to NIFI-2491, and should either not be allowed to 
happen (terminate the instance), or should be made clear in the UI.



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