[jira] [Commented] (NIFI-2034) NiFi is always loading a specific version of httpcore to classpath

[asanka sanjaya (JIRA)]

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

asanka sanjaya commented on NIFI-2034:
--

The pom file looks like this.


http://www.w3.org/2001/XMLSchema-instance; 
xmlns="http://maven.apache.org/POM/4.0.0; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0


org.apache.nifi
nifi-nar-bundles
0.6.1


com.xyz.product
abcd
1.0-SNAPSHOT
pom


pqr



1.7.14
3.2.2
5.1.0
1.3
4.12
1.10.19
4.2.0
1.1.3
4.0
1.3.2
1.8
1.11
2.4
1.4.7
1.1.1
9.0.9
r938
0.6.1
2.7.5
2.7.5







org.slf4j
slf4j-api
${slf4j.version}


ch.qos.logback
logback-core
${logback.version}


ch.qos.logback
logback-classic
${logback.version}


org.mongodb
mongo-java-driver
${mongo-java-driver.version}


org.mongodb.morphia
morphia
${morpia.version}


solr-solrj
org.apache.solr
${solr-solrj.version}


com.google.inject
guice
${guice.version}


org.apache.oozie
oozie-client
${oozie-client.version}


org.apache.directory.api
api-all
1.0.0-M33


net.lingala.zip4j
zip4j
${zip4j.version}


com.sun.jersey
jersey-client
${jersey-version}


org.apache.tika
tika-parsers
${tika.version}


org.apache.tika
tika-app
${tika.version}


javax.mail
mail
${javax.mail.version}


commons-io
commons-io
${apache.commons.io.version}


com.fasterxml.jackson.core
jackson-core
${jackson-core-version}


com.fasterxml.jackson.core
jackson-databind
${jackson-databind-version}


org.hamcrest
hamcrest-all
${hamcrest-all.version}
test


junit
junit
${junit.version}
test


org.mockito
mockito-all
${mockito-all.version}
test


com.microsoft.ews-java-api
ews-java-api
2.0


org.codehaus.jackson
jackson-mapper-asl
1.9.13






> NiFi is always loading a specific version of httpcore to classpath
> --
>
> Key: NIFI-2034
> URL: https://issues.apache.org/jira/browse/NIFI-2034
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.5.1, 0.6.1
>Reporter: asanka sanjaya
>
> We have written a custom nifi processor to connect to microsoft exchange 
> server and get emails. It runs perfectly as a standalone application. But 
> nifi always loads httpcore-4.4.1.jar and httpclient-4.4.1.jar to classpath 
> even though the nar file contains httpcore-4.4.4.jar and httpclient-4.5.2.jar.
> Because of that, it throws this error.
> 016-06-15 18:57:17,086 WARN [Timer-Driven Process Thread-4] 
> o.a.n.c.t.ContinuallyRunProcessorTask Administratively Yielding 
> NiFiJournalJob[id=52616329-d64c-4e14-bcb1-4c799891682a] due to uncaught 
> Exception: java.lang.NoSuchFieldError: INSTANCE
> 2016-06-15 18:57:17,091 WARN [Timer-Driven Process Thread-4] 
> o.a.n.c.t.ContinuallyRunProcessorTask 
> java.lang.NoSuchFieldError: INSTANCE
>   at 
> org.apache.http.impl.io.DefaultHttpRequestWriterFactory.(DefaultHttpRequestWriterFactory.java:52)
>  ~[httpcore-4.4.1.jar:4.4.1]
>   at 
> 

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

[Andre (JIRA)]

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

Andre commented on NIFI-1148:
-

[~ozhurakousky] - no dramas. It may be worth having a look on the attributes 
being created by the processors within NIFI-1899 so we have no conflicting 
attribute names and perhaps some common take to their names?

Cheers

> 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-2250) Add EL support to Queue URL in GetSQS

[Joseph Gresock (JIRA)]

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

Joseph Gresock commented on NIFI-2250:
--

Good question, I hadn't considered the case of switching URLs often.  I'll 
research whether the library uses any kind of caching tomorrow.

> Add EL support to Queue URL in GetSQS
> -
>
> Key: NIFI-2250
> URL: https://issues.apache.org/jira/browse/NIFI-2250
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Joseph Gresock
>Assignee: Joseph Gresock
>Priority: Minor
> Attachments: 0001-NIFI-2250-Enabling-EL-on-GetSQS-Queue-URL.patch
>
>
> Allowing EL support in the Queue URL would allow for more dynamic 
> configuration of SQS queues (i.e., a different queue in a production vs a 
> staging environment).



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

[jira] [Commented] (NIFI-2028) Site-to-Site Transit URI is inconsistent

[Koji Kawamura (JIRA)]

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

Koji Kawamura commented on NIFI-2028:
-

[~JDP10101] Yes, the server bind 3080 and 3081, and client has to use new 
random free port to transfer data. I'm sure those transit URIs are what will be 
in the same box. Test result Provenance data is attached.

> Site-to-Site Transit URI is inconsistent
> 
>
> Key: NIFI-2028
> URL: https://issues.apache.org/jira/browse/NIFI-2028
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Fix For: 1.0.0
>
> Attachments: send-to-the-same-box.png
>
>
> Site-to-Site client and server create provenance event at both end, and those 
> have Transit URI in it to record how flow files are transferred. However, the 
> URI formats are inconsistent among RAW vs HTTP.
> Test result as follows:
> - These port numbers are configurable in nifi.properties
> - 3080: Web API port (nifi.web.http.port)
> - 3081: Site-to-Site RAW Socket port (nifi.remote.input.socket.port)
> *Before Fix*
> PUSH - RAW
> |Client - SEND: | nifi://localhost:3081/flow-file-uuid |
> |Server - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> PULL - RAW
> |Client - RECEIVE:| nifi://localhost:3081flow-file-uuid|
> |Server - SEND:   | nifi://localhost:3081/flow-file-uuid|
> PUSH - HTTP
> |Client - SEND:   | http://127.0.0.1:3080/nifi-api/flow-file-uuid|
> |Server - RECEIVE:| nifi://127.0.0.1:57390|
> PULL - HTTP
> |Client - RECEIVE:| http://127.0.0.1:3080/flow-file-uuid|
> |Server - SEND:   | nifi://127.0.0.1:57673|
> *Issues*
> - PULL - RAW, Client - RECEIVE: lacks '/' in between port and flow-file uuid
> - RAW uses server's host and port on both end (by transit url prefix), HTTP 
> should follow this rule
> - HTTP transit uri looks like REST endpoint but it is not a real endpoint. It 
> should be an actual endpoint URI
> - RAW uses hostname, while HTTP uses IP address
> *After Fix*
> PUSH - RAW
> |Client - SEND: | nifi://localhost:3081/flow-file-uuid |
> |Server - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> PULL - RAW
> |Client - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> |Server - SEND:   | nifi://localhost:3081/flow-file-uuid|
> PUSH - HTTP
> |Client - SEND:   | 
> http://localhost:3080/nifi-api/site-to-site/input-ports/$port-id/transactions/$tx-id/flow-files|
> |Server - RECEIVE:| 
> http://localhost:3080/nifi-api/site-to-site/input-ports/$port-id/transactions/$tx-id/flow-files|
> PULL - HTTP
> |Client - RECEIVE: | 
> http://localhost:3080/nifi-api/site-to-site/output-ports/$port-id/transactions/$tx-id/flow-files|
> |Server - SEND:   | 
> http://localhost:3080/nifi-api/site-to-site/output-ports/$port-id/transactions/$tx-id/flow-files|



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

[jira] [Updated] (NIFI-2028) Site-to-Site Transit URI is inconsistent

[Koji Kawamura (JIRA)]

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

Koji Kawamura updated NIFI-2028:

Attachment: send-to-the-same-box.png

> Site-to-Site Transit URI is inconsistent
> 
>
> Key: NIFI-2028
> URL: https://issues.apache.org/jira/browse/NIFI-2028
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Fix For: 1.0.0
>
> Attachments: send-to-the-same-box.png
>
>
> Site-to-Site client and server create provenance event at both end, and those 
> have Transit URI in it to record how flow files are transferred. However, the 
> URI formats are inconsistent among RAW vs HTTP.
> Test result as follows:
> - These port numbers are configurable in nifi.properties
> - 3080: Web API port (nifi.web.http.port)
> - 3081: Site-to-Site RAW Socket port (nifi.remote.input.socket.port)
> *Before Fix*
> PUSH - RAW
> |Client - SEND: | nifi://localhost:3081/flow-file-uuid |
> |Server - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> PULL - RAW
> |Client - RECEIVE:| nifi://localhost:3081flow-file-uuid|
> |Server - SEND:   | nifi://localhost:3081/flow-file-uuid|
> PUSH - HTTP
> |Client - SEND:   | http://127.0.0.1:3080/nifi-api/flow-file-uuid|
> |Server - RECEIVE:| nifi://127.0.0.1:57390|
> PULL - HTTP
> |Client - RECEIVE:| http://127.0.0.1:3080/flow-file-uuid|
> |Server - SEND:   | nifi://127.0.0.1:57673|
> *Issues*
> - PULL - RAW, Client - RECEIVE: lacks '/' in between port and flow-file uuid
> - RAW uses server's host and port on both end (by transit url prefix), HTTP 
> should follow this rule
> - HTTP transit uri looks like REST endpoint but it is not a real endpoint. It 
> should be an actual endpoint URI
> - RAW uses hostname, while HTTP uses IP address
> *After Fix*
> PUSH - RAW
> |Client - SEND: | nifi://localhost:3081/flow-file-uuid |
> |Server - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> PULL - RAW
> |Client - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> |Server - SEND:   | nifi://localhost:3081/flow-file-uuid|
> PUSH - HTTP
> |Client - SEND:   | 
> http://localhost:3080/nifi-api/site-to-site/input-ports/$port-id/transactions/$tx-id/flow-files|
> |Server - RECEIVE:| 
> http://localhost:3080/nifi-api/site-to-site/input-ports/$port-id/transactions/$tx-id/flow-files|
> PULL - HTTP
> |Client - RECEIVE: | 
> http://localhost:3080/nifi-api/site-to-site/output-ports/$port-id/transactions/$tx-id/flow-files|
> |Server - SEND:   | 
> http://localhost:3080/nifi-api/site-to-site/output-ports/$port-id/transactions/$tx-id/flow-files|



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

[jira] [Updated] (NIFI-2028) Site-to-Site Transit URI is inconsistent

[Koji Kawamura (JIRA)]

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

Koji Kawamura updated NIFI-2028:

Attachment: (was: send-locally-provenance.png)

> Site-to-Site Transit URI is inconsistent
> 
>
> Key: NIFI-2028
> URL: https://issues.apache.org/jira/browse/NIFI-2028
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Fix For: 1.0.0
>
> Attachments: send-to-the-same-box.png
>
>
> Site-to-Site client and server create provenance event at both end, and those 
> have Transit URI in it to record how flow files are transferred. However, the 
> URI formats are inconsistent among RAW vs HTTP.
> Test result as follows:
> - These port numbers are configurable in nifi.properties
> - 3080: Web API port (nifi.web.http.port)
> - 3081: Site-to-Site RAW Socket port (nifi.remote.input.socket.port)
> *Before Fix*
> PUSH - RAW
> |Client - SEND: | nifi://localhost:3081/flow-file-uuid |
> |Server - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> PULL - RAW
> |Client - RECEIVE:| nifi://localhost:3081flow-file-uuid|
> |Server - SEND:   | nifi://localhost:3081/flow-file-uuid|
> PUSH - HTTP
> |Client - SEND:   | http://127.0.0.1:3080/nifi-api/flow-file-uuid|
> |Server - RECEIVE:| nifi://127.0.0.1:57390|
> PULL - HTTP
> |Client - RECEIVE:| http://127.0.0.1:3080/flow-file-uuid|
> |Server - SEND:   | nifi://127.0.0.1:57673|
> *Issues*
> - PULL - RAW, Client - RECEIVE: lacks '/' in between port and flow-file uuid
> - RAW uses server's host and port on both end (by transit url prefix), HTTP 
> should follow this rule
> - HTTP transit uri looks like REST endpoint but it is not a real endpoint. It 
> should be an actual endpoint URI
> - RAW uses hostname, while HTTP uses IP address
> *After Fix*
> PUSH - RAW
> |Client - SEND: | nifi://localhost:3081/flow-file-uuid |
> |Server - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> PULL - RAW
> |Client - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> |Server - SEND:   | nifi://localhost:3081/flow-file-uuid|
> PUSH - HTTP
> |Client - SEND:   | 
> http://localhost:3080/nifi-api/site-to-site/input-ports/$port-id/transactions/$tx-id/flow-files|
> |Server - RECEIVE:| 
> http://localhost:3080/nifi-api/site-to-site/input-ports/$port-id/transactions/$tx-id/flow-files|
> PULL - HTTP
> |Client - RECEIVE: | 
> http://localhost:3080/nifi-api/site-to-site/output-ports/$port-id/transactions/$tx-id/flow-files|
> |Server - SEND:   | 
> http://localhost:3080/nifi-api/site-to-site/output-ports/$port-id/transactions/$tx-id/flow-files|



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

[jira] [Updated] (NIFI-2173) LDAP provider referral strategy typo in Code

[Matt Burgess (JIRA)]

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

Matt Burgess updated NIFI-2173:
---
Assignee: Joseph Percivall

> LDAP provider referral strategy typo in Code
> 
>
> Key: NIFI-2173
> URL: https://issues.apache.org/jira/browse/NIFI-2173
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.6.0
>Reporter: Matthew Clarke
>Assignee: Joseph Percivall
>Priority: Minor
>  Labels: newbie
> Fix For: 1.0.0
>
>
> The LDAP referral strategy set in the login-identity-providers.xml file 
> should support IGNORE, FOLLOW, or THROW.  If the referral strategy is set to 
> IGNORE, NiFi will fail to start and complain that the possible values are 
> [follow, ignore, throw].  The issue is that the code has a typo where IGNORE 
> is spelled INGORE.  
> WORKAROUND: Users can get around the issue by configuring the referral 
> strategy for INGORE.



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

[jira] [Updated] (NIFI-2028) Site-to-Site Transit URI is inconsistent

[Koji Kawamura (JIRA)]

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

Koji Kawamura updated NIFI-2028:

Attachment: send-locally-provenance.png

> Site-to-Site Transit URI is inconsistent
> 
>
> Key: NIFI-2028
> URL: https://issues.apache.org/jira/browse/NIFI-2028
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Fix For: 1.0.0
>
> Attachments: send-locally-provenance.png
>
>
> Site-to-Site client and server create provenance event at both end, and those 
> have Transit URI in it to record how flow files are transferred. However, the 
> URI formats are inconsistent among RAW vs HTTP.
> Test result as follows:
> - These port numbers are configurable in nifi.properties
> - 3080: Web API port (nifi.web.http.port)
> - 3081: Site-to-Site RAW Socket port (nifi.remote.input.socket.port)
> *Before Fix*
> PUSH - RAW
> |Client - SEND: | nifi://localhost:3081/flow-file-uuid |
> |Server - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> PULL - RAW
> |Client - RECEIVE:| nifi://localhost:3081flow-file-uuid|
> |Server - SEND:   | nifi://localhost:3081/flow-file-uuid|
> PUSH - HTTP
> |Client - SEND:   | http://127.0.0.1:3080/nifi-api/flow-file-uuid|
> |Server - RECEIVE:| nifi://127.0.0.1:57390|
> PULL - HTTP
> |Client - RECEIVE:| http://127.0.0.1:3080/flow-file-uuid|
> |Server - SEND:   | nifi://127.0.0.1:57673|
> *Issues*
> - PULL - RAW, Client - RECEIVE: lacks '/' in between port and flow-file uuid
> - RAW uses server's host and port on both end (by transit url prefix), HTTP 
> should follow this rule
> - HTTP transit uri looks like REST endpoint but it is not a real endpoint. It 
> should be an actual endpoint URI
> - RAW uses hostname, while HTTP uses IP address
> *After Fix*
> PUSH - RAW
> |Client - SEND: | nifi://localhost:3081/flow-file-uuid |
> |Server - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> PULL - RAW
> |Client - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> |Server - SEND:   | nifi://localhost:3081/flow-file-uuid|
> PUSH - HTTP
> |Client - SEND:   | 
> http://localhost:3080/nifi-api/site-to-site/input-ports/$port-id/transactions/$tx-id/flow-files|
> |Server - RECEIVE:| 
> http://localhost:3080/nifi-api/site-to-site/input-ports/$port-id/transactions/$tx-id/flow-files|
> PULL - HTTP
> |Client - RECEIVE: | 
> http://localhost:3080/nifi-api/site-to-site/output-ports/$port-id/transactions/$tx-id/flow-files|
> |Server - SEND:   | 
> http://localhost:3080/nifi-api/site-to-site/output-ports/$port-id/transactions/$tx-id/flow-files|



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

[jira] [Updated] (NIFI-1896) Extract Extension API into separate module

[Joseph Witt (JIRA)]

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

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

> Extract Extension API into separate module
> --
>
> Key: NIFI-1896
> URL: https://issues.apache.org/jira/browse/NIFI-1896
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Core Framework
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
> Fix For: 1.0.0
>
>
> As discussed on the mailing list, the original contents of which are below:
> {quote}
> I would like to propose a refactoring of the nifi-api for our master/1.0 
> branch.  In summary, a lightweight and concise view of this module allows for 
> reduced footprint of the NIFI API for components and minimizes the creep of 
> those items that authoring components do not need to use.  
> In a broader context there is a core set of interfaces that users will 
> interface with in their generation of new extensions for NiFi.  Summarily, 
> these components have comprised Processors, Controller Services, Reporting 
> Tasks, & Prioritizers (the last of which is currently under discussion to 
> potentially be removed from this forward facing status).  
> What I would like to suggest is the refactoring of the nifi-api module to be 
> broken down into to two components: the nifi-api and the nifi-framework-api.  
> nifi-api will encompass all things developers would need to provide 
> extensions tailored toward interacting with dataflow.  nifi-framework-api 
> would address the more internal items that are also extensible, but not 
> something that is typically implemented and would consist of the remainder of 
> those items not in nifi-api. 
> This enables a core set of APIs that extensions can implement with a broader 
> perspective of providing API compatibility between both NiFi and MiNiFi.  
> This enables some nice reuse of work with the goal ultimately amounting to, 
> write for NiFi, run on MiNiFi and the reverse.
> Logistically, for NiFi extension writers, at first glance, not much would 
> change with their efforts.  The core dependency would remain the same, but 
> would be curtailed in its scope to only what is required.  Framework 
> components of course, would need to be updated to include a dependency on 
> nifi-framework-api.
> Given that the new structure would not yet be released, and to allow MiNiFi 
> to continue on its development path, a Git submodule or subtree would be 
> introduced into MiNiFi and supporting documentation on how to make use of 
> this for those not familiar.
> {quote}



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

[jira] [Commented] (NIFI-1896) Extract Extension API into separate module

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1896:
--

Github user asfgit closed the pull request at:

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


> Extract Extension API into separate module
> --
>
> Key: NIFI-1896
> URL: https://issues.apache.org/jira/browse/NIFI-1896
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Core Framework
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
> Fix For: 1.0.0
>
>
> As discussed on the mailing list, the original contents of which are below:
> {quote}
> I would like to propose a refactoring of the nifi-api for our master/1.0 
> branch.  In summary, a lightweight and concise view of this module allows for 
> reduced footprint of the NIFI API for components and minimizes the creep of 
> those items that authoring components do not need to use.  
> In a broader context there is a core set of interfaces that users will 
> interface with in their generation of new extensions for NiFi.  Summarily, 
> these components have comprised Processors, Controller Services, Reporting 
> Tasks, & Prioritizers (the last of which is currently under discussion to 
> potentially be removed from this forward facing status).  
> What I would like to suggest is the refactoring of the nifi-api module to be 
> broken down into to two components: the nifi-api and the nifi-framework-api.  
> nifi-api will encompass all things developers would need to provide 
> extensions tailored toward interacting with dataflow.  nifi-framework-api 
> would address the more internal items that are also extensible, but not 
> something that is typically implemented and would consist of the remainder of 
> those items not in nifi-api. 
> This enables a core set of APIs that extensions can implement with a broader 
> perspective of providing API compatibility between both NiFi and MiNiFi.  
> This enables some nice reuse of work with the goal ultimately amounting to, 
> write for NiFi, run on MiNiFi and the reverse.
> Logistically, for NiFi extension writers, at first glance, not much would 
> change with their efforts.  The core dependency would remain the same, but 
> would be curtailed in its scope to only what is required.  Framework 
> components of course, would need to be updated to include a dependency on 
> nifi-framework-api.
> Given that the new structure would not yet be released, and to allow MiNiFi 
> to continue on its development path, a Git submodule or subtree would be 
> introduced into MiNiFi and supporting documentation on how to make use of 
> this for those not familiar.
> {quote}



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

[GitHub] nifi pull request #650: NIFI-1896 Refactoring nifi-api module to only be tho...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2020) Enhance JoltTransformJSON processor to support custom transforms

[Matt Burgess (JIRA)]

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

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

> Enhance JoltTransformJSON processor to support custom transforms
> 
>
> Key: NIFI-2020
> URL: https://issues.apache.org/jira/browse/NIFI-2020
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 1.0.0
>
>
> Jolt supports additional custom transforms via fully-qualified Java 
> classnames. Would like to provide the ability to support custom 
> transformation (via drop in jars) for the Jolt Transform processor.



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

[jira] [Commented] (NIFI-2020) Enhance JoltTransformJSON processor to support custom transforms

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2020 - initial commit for custom transformation support

NIFI-2020 - updates to use lambdas/stream wherever possible and fix potential 
nullpointer issue.

Signed-off-by: Matt Burgess 

This closes #564


> Enhance JoltTransformJSON processor to support custom transforms
> 
>
> Key: NIFI-2020
> URL: https://issues.apache.org/jira/browse/NIFI-2020
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 1.0.0
>
>
> Jolt supports additional custom transforms via fully-qualified Java 
> classnames. Would like to provide the ability to support custom 
> transformation (via drop in jars) for the Jolt Transform processor.



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

[GitHub] nifi pull request #564: NIFI-2020 - Enhance JoltTransformJSON processor to s...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2020) Enhance JoltTransformJSON processor to support custom transforms

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2020 - initial commit for custom transformation support

NIFI-2020 - updates to use lambdas/stream wherever possible and fix potential 
nullpointer issue.

Signed-off-by: Matt Burgess 

This closes #564


> Enhance JoltTransformJSON processor to support custom transforms
> 
>
> Key: NIFI-2020
> URL: https://issues.apache.org/jira/browse/NIFI-2020
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 1.0.0
>
>
> Jolt supports additional custom transforms via fully-qualified Java 
> classnames. Would like to provide the ability to support custom 
> transformation (via drop in jars) for the Jolt Transform processor.



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

[jira] [Commented] (NIFI-2028) Site-to-Site Transit URI is inconsistent

[Joseph Percivall (JIRA)]

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

Joseph Percivall commented on NIFI-2028:


[~ijokarumawak] are you sure those transit URIs are what they will be when 
transmitting to an instance on the same box? Wouldn't ports 3080 and 3081 be 
bound to by the instance from the start and when S2S tried to communicate it 
would need to bind to a new port?

I ask because I am seeing HTTP and RAW transmitting to/from (push/pull) the 
proper port but the source/dest (push/pull) are seemingly random free ports. I 
can attach Wireshark captures if necessary.

> Site-to-Site Transit URI is inconsistent
> 
>
> Key: NIFI-2028
> URL: https://issues.apache.org/jira/browse/NIFI-2028
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Fix For: 1.0.0
>
>
> Site-to-Site client and server create provenance event at both end, and those 
> have Transit URI in it to record how flow files are transferred. However, the 
> URI formats are inconsistent among RAW vs HTTP.
> Test result as follows:
> - 3080: Web API port
> - 3081: Site-to-Site RAW Socket port
> *Before Fix*
> PUSH - RAW
> |Client - SEND: | nifi://localhost:3081/flow-file-uuid |
> |Server - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> PULL - RAW
> |Client - RECEIVE:| nifi://localhost:3081flow-file-uuid|
> |Server - SEND:   | nifi://localhost:3081/flow-file-uuid|
> PUSH - HTTP
> |Client - SEND:   | http://127.0.0.1:3080/nifi-api/flow-file-uuid|
> |Server - RECEIVE:| nifi://127.0.0.1:57390|
> PULL - HTTP
> |Client - RECEIVE:| http://127.0.0.1:3080/flow-file-uuid|
> |Server - SEND:   | nifi://127.0.0.1:57673|
> *Issues*
> - PULL - RAW, Client - RECEIVE: lacks '/' in between port and flow-file uuid
> - RAW uses server's host and port on both end (by transit url prefix), HTTP 
> should follow this rule
> - HTTP transit uri looks like REST endpoint but it is not a real endpoint. It 
> should be an actual endpoint URI
> - RAW uses hostname, while HTTP uses IP address
> *After Fix*
> PUSH - RAW
> |Client - SEND: | nifi://localhost:3081/flow-file-uuid |
> |Server - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> PULL - RAW
> |Client - RECEIVE: | nifi://localhost:3081/flow-file-uuid|
> |Server - SEND:   | nifi://localhost:3081/flow-file-uuid|
> PUSH - HTTP
> |Client - SEND:   | 
> http://localhost:3080/nifi-api/site-to-site/input-ports/$port-id/transactions/$tx-id/flow-files|
> |Server - RECEIVE:| 
> http://localhost:3080/nifi-api/site-to-site/input-ports/$port-id/transactions/$tx-id/flow-files|
> PULL - HTTP
> |Client - RECEIVE: | 
> http://localhost:3080/nifi-api/site-to-site/output-ports/$port-id/transactions/$tx-id/flow-files|
> |Server - SEND:   | 
> http://localhost:3080/nifi-api/site-to-site/output-ports/$port-id/transactions/$tx-id/flow-files|



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

[jira] [Commented] (NIFI-2116) Translate Documentation Into Spanish

[Chagara (JIRA)]

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

Chagara commented on NIFI-2116:
---

Ill say this. It might change depending who reviews it and how they use
their words. For example i speak carib spanish.



> Translate Documentation Into Spanish
> 
>
> Key: NIFI-2116
> URL: https://issues.apache.org/jira/browse/NIFI-2116
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Documentation & Website
>Reporter: Chagara
>Assignee: Chagara
>Priority: Minor
>
> Create documentation in Spanish to expand NIFI reach.



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

[jira] [Commented] (NIFI-2116) Translate Documentation Into Spanish

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2116:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/587
  
If I can finish my 1.0 tickets I will review this. 


> Translate Documentation Into Spanish
> 
>
> Key: NIFI-2116
> URL: https://issues.apache.org/jira/browse/NIFI-2116
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Documentation & Website
>Reporter: Chagara
>Assignee: Chagara
>Priority: Minor
>
> Create documentation in Spanish to expand NIFI reach.



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

[jira] [Commented] (NIFI-2222) Jetty reversal of KeyStore, Key passwords in nifi.properties

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-:
--

Github user asfgit closed the pull request at:

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


> Jetty reversal of KeyStore, Key passwords in nifi.properties
> 
>
> Key: NIFI-
> URL: https://issues.apache.org/jira/browse/NIFI-
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Bryan Rosander
>
> In JettyServer, currently if you define both nifi.security.keystorePasswd and 
> nifi.security.keyPasswd, the keyPasswd value will be used for the 
> SslContext's keyStorePassword and the keyStorePasswd will be used for the 
> keyManagerPassword.
> Additionally if you only define the keyPasswd, it will set keyStorePassword 
> instead of keyManagerPassword.
> I believe that this is backwards from the expected behaviour of the two 
> properties.



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

[jira] [Created] (NIFI-2265) Authorization: Able to see hidden processor information in Status History

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-2265:


 Summary: Authorization: Able to see hidden processor information 
in Status History
 Key: NIFI-2265
 URL: https://issues.apache.org/jira/browse/NIFI-2265
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Affects Versions: 1.0.0
Reporter: Andrew Lim
 Attachments: NIFI-2265_statusHistory.png

When a user is not privileged to see a processor, on the canvas the Name and 
Type of the Processor is properly hidden.  But if you right-click on the 
processor and select "Stats", this information is displayed in the Status 
History.

Screenshot attached.



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

[jira] [Updated] (NIFI-2265) Authorization: Able to see hidden processor information in Status History

[Andrew Lim (JIRA)]

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

Andrew Lim updated NIFI-2265:
-
Attachment: NIFI-2265_statusHistory.png

> Authorization: Able to see hidden processor information in Status History
> -
>
> Key: NIFI-2265
> URL: https://issues.apache.org/jira/browse/NIFI-2265
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>  Labels: UI
> Attachments: NIFI-2265_statusHistory.png
>
>
> When a user is not privileged to see a processor, on the canvas the Name and 
> Type of the Processor is properly hidden.  But if you right-click on the 
> processor and select "Stats", this information is displayed in the Status 
> History.
> Screenshot attached.



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

[jira] [Resolved] (NIFI-1688) PostHTTP does not honor SSLContextService Protocols

[Aldrin Piri (JIRA)]

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

Aldrin Piri resolved NIFI-1688.
---
Resolution: Fixed

> PostHTTP does not honor SSLContextService Protocols
> ---
>
> Key: NIFI-1688
> URL: https://issues.apache.org/jira/browse/NIFI-1688
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Aldrin Piri
>Assignee: Andy LoPresto
> Fix For: 1.0.0
>
>
> As per:
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PostHTTP.java#L391
> the SSLConnectionSocketFactory is hardcoded to use TLSv1 making connections 
> impossible to some endpoints requiring TLSv1.1 or higher.



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

[jira] [Commented] (NIFI-1688) PostHTTP does not honor SSLContextService Protocols

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1688:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi/pull/624
  
Changes look good and thanks for the thorough testing.  I have merged this 
into master.  Thanks!


> PostHTTP does not honor SSLContextService Protocols
> ---
>
> Key: NIFI-1688
> URL: https://issues.apache.org/jira/browse/NIFI-1688
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Aldrin Piri
>Assignee: Andy LoPresto
> Fix For: 1.0.0
>
>
> As per:
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PostHTTP.java#L391
> the SSLConnectionSocketFactory is hardcoded to use TLSv1 making connections 
> impossible to some endpoints requiring TLSv1.1 or higher.



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

[jira] [Commented] (NIFI-1688) PostHTTP does not honor SSLContextService Protocols

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1688 Resolved issue in PostHTTP -- now uses SSLContextService's protocol 
setting. Modified construction of SSLSocketFactory to avoid hardcoding 
supported protocol.  Added debug information for supported cipher suites.

This closes #624.

Signed-off-by: Aldrin Piri 


> PostHTTP does not honor SSLContextService Protocols
> ---
>
> Key: NIFI-1688
> URL: https://issues.apache.org/jira/browse/NIFI-1688
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Aldrin Piri
>Assignee: Andy LoPresto
> Fix For: 1.0.0
>
>
> As per:
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PostHTTP.java#L391
> the SSLConnectionSocketFactory is hardcoded to use TLSv1 making connections 
> impossible to some endpoints requiring TLSv1.1 or higher.



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

[jira] [Assigned] (NIFI-2107) Other panels like 'content-viewer' still using old style

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2107:
-

Assignee: Scott Aslan

> Other panels like 'content-viewer' still using old style
> 
>
> Key: NIFI-2107
> URL: https://issues.apache.org/jira/browse/NIFI-2107
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Joseph Witt
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
> Attachments: bg-error.png
>
>




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

[jira] [Commented] (NIFI-2086) Provenance Event window: selected tab is not highlighted properly due to misaligned border

[Aldrin Piri (JIRA)]

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

Aldrin Piri commented on NIFI-2086:
---

Hey [~scottyaslan],

I see this was marked as fixed but don't seem to see any patch or linked GitHub 
PR.  Is fixed the right status for this or was it OBE/a dupe?

> Provenance Event window:  selected tab is not highlighted properly due to 
> misaligned border
> ---
>
> Key: NIFI-2086
> URL: https://issues.apache.org/jira/browse/NIFI-2086
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Mac OS X, Chrome
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
>  Labels: UI
> Attachments: NIFI-2086_provenanceEventTabs.png
>
>
> As shown in the attached screenshot, the border around the tabs in this 
> window is misaligned.  It should be aligned with the bottom of the tabs like 
> in the Configure Processor window.



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

[jira] [Closed] (NIFI-1989) Need to align commons-io artifact group as per MVNCENTRAL-244

[Puspendu Banerjee (JIRA)]

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

Puspendu Banerjee closed NIFI-1989.
---

Closing as resolved

> Need to align commons-io artifact group as per MVNCENTRAL-244
> -
>
> Key: NIFI-1989
> URL: https://issues.apache.org/jira/browse/NIFI-1989
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Puspendu Banerjee
>Assignee: Puspendu Banerjee
>Priority: Minor
>  Labels: artifact, dependency, maven
> Fix For: 1.0.0
>
>
> [WARNING] While downloading org.apache.commons:commons-io:1.3.2
>   This artifact has been relocated to commons-io:commons-io:1.3.2.
>   https://issues.sonatype.org/browse/MVNCENTRAL-244



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

[jira] [Updated] (NIFI-1989) Need to align commons-io artifact group as per MVNCENTRAL-244

[Aldrin Piri (JIRA)]

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

Aldrin Piri updated NIFI-1989:
--
Fix Version/s: 1.0.0

> Need to align commons-io artifact group as per MVNCENTRAL-244
> -
>
> Key: NIFI-1989
> URL: https://issues.apache.org/jira/browse/NIFI-1989
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Puspendu Banerjee
>Assignee: Puspendu Banerjee
>Priority: Minor
>  Labels: artifact, dependency, maven
> Fix For: 1.0.0
>
>
> [WARNING] While downloading org.apache.commons:commons-io:1.3.2
>   This artifact has been relocated to commons-io:commons-io:1.3.2.
>   https://issues.sonatype.org/browse/MVNCENTRAL-244



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

[GitHub] nifi pull request #514: fixes NIFI-1989

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #514: fixes NIFI-1989

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/514
  
Haha, glad it helped


---
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-1989) Need to align commons-io artifact group as per MVNCENTRAL-244

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1989:
--

Github user PuspenduBanerjee commented on the issue:

https://github.com/apache/nifi/pull/514
  
thanks @JPercivall . Good part is , got a reason to brush up my regex  :)


> Need to align commons-io artifact group as per MVNCENTRAL-244
> -
>
> Key: NIFI-1989
> URL: https://issues.apache.org/jira/browse/NIFI-1989
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Puspendu Banerjee
>Priority: Minor
>  Labels: artifact, dependency, maven
>
> [WARNING] While downloading org.apache.commons:commons-io:1.3.2
>   This artifact has been relocated to commons-io:commons-io:1.3.2.
>   https://issues.sonatype.org/browse/MVNCENTRAL-244



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

[jira] [Updated] (NIFI-2107) Other panels like 'content-viewer' still using old style

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2107:

Attachment: bg-error.png

> Other panels like 'content-viewer' still using old style
> 
>
> Key: NIFI-2107
> URL: https://issues.apache.org/jira/browse/NIFI-2107
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Joseph Witt
> Fix For: 1.0.0
>
> Attachments: bg-error.png
>
>




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

[jira] [Updated] (NIFI-2227) Queue Listing - View button missing in FlowFile Details Dialog

[Scott Aslan (JIRA)]

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

Scott Aslan updated NIFI-2227:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Queue Listing - View button missing in FlowFile Details Dialog
> --
>
> Key: NIFI-2227
> URL: https://issues.apache.org/jira/browse/NIFI-2227
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>




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

[GitHub] nifi issue #514: fixes NIFI-1989

[JPercivall]

Github user JPercivall commented on the issue:

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

Removed the offending package from m2 repo, rebuilt and saw that it 
properly didn't exist. Ran a template using MQTT processors to verified 
functionality. Thanks @PuspenduBanerjee, I will merge it in.


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

[GitHub] nifi issue #562: NIFI-2062 AWS SDK Update:

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi/pull/562
  
Build and contrib all look good.  Reviewed release notes from AWS and seems 
pretty low risk.  Ran through some of my templates I had saved from reviewing 
many of the components and everything looked good from that perspective.  Will 
take care of merging.  Thanks for making these upgrades! 


---
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-2062) Upgrade AWS SDK

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2062:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi/pull/562
  
Build and contrib all look good.  Reviewed release notes from AWS and seems 
pretty low risk.  Ran through some of my templates I had saved from reviewing 
many of the components and everything looked good from that perspective.  Will 
take care of merging.  Thanks for making these upgrades! 


> Upgrade AWS SDK
> ---
>
> Key: NIFI-2062
> URL: https://issues.apache.org/jira/browse/NIFI-2062
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
> Fix For: 1.0.0
>
>
> I propose to update NiFi's current AWS SDK from version 1.10.32 (Nov 3, 2015) 
> to version 1.11.8 (Jun 16, 2016).  Known impact:
> * *API Signature Version* - I expect the largest impact will be to S3 
> processors, where the default API signature version will change from v2 to v4 
> for a wider number of operations.  See release notes for 
> [1.11.0|https://aws.amazon.com/releasenotes/Java/9979983567247718].
> * *Region Endpoint Info* - The AWS SDK contains baked-in configuration data 
> about AWS regions and the services they support, which is periodically 
> updated.
> * *Service Updates* - Potentially relevant updates to future NiFi support for 
> AWS IoT and other newer services.
> I am not aware of any shocking changes for the services NiFi currently 
> supports (S3, SNS, SQS, DynamoDB, Lambda, Kinesis Firehose).



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

[jira] [Commented] (NIFI-1465) Upgrade encryption of sensitive properties

[Andy LoPresto (JIRA)]

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

Andy LoPresto commented on NIFI-1465:
-

Better link to email thread [1]. 

[1] 
https://lists.apache.org/thread.html/6a4282eca3d3a47061a13662e9d3c83e904aef334f64e9a5783940ef@%3Cusers.nifi.apache.org%3E

> Upgrade encryption of sensitive properties
> --
>
> Key: NIFI-1465
> URL: https://issues.apache.org/jira/browse/NIFI-1465
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.5.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: encryption, security
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> Currently, NiFi accepts a password and encryption algorithm in 
> `nifi.properties` which are used to encrypt all sensitive processor 
> properties throughout the application. The password defaults to empty and the 
> algorithm defaults to {{PBEWITHMD5AND256BITAES-CBC-OPENSSL}}. This algorithm:
> * uses a digest function ({{MD5}}) which is not cryptographically secure 
> [1][2][3][4]
> * uses a single iteration count [5][6]
> * limits password input to 16 characters on JVMs without the unlimited 
> strength cryptographic jurisdiction policy files installed [NIFI-1255]
> all of which combine to make it extremely insecure. We should change the 
> default algorithm to use a strong key derivation function (KDF) [7] which 
> will properly derive a key to protect the sensitive properties. 
> Because existing systems have already encrypted the properties using a key 
> derived from the original settings, we should provide a translation/upgrade 
> utility to seamlessly convert the stored values from the old password & 
> algorithm combination to the new. 
> [1] http://security.stackexchange.com/a/19908/16485
> [2] http://security.stackexchange.com/a/31846/16485
> [3] 
> http://security.stackexchange.com/questions/52461/how-weak-is-md5-as-a-password-hashing-function
> [4] http://security.stackexchange.com/a/31410/16485
> [5] http://security.stackexchange.com/a/29139/16485
> [6] https://www.openssl.org/docs/manmaster/crypto/EVP_BytesToKey.html
> [7] 
> https://cwiki.apache.org/confluence/display/NIFI/Key+Derivation+Function+Explanations



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

[jira] [Commented] (NIFI-1465) Upgrade encryption of sensitive properties

[Andy LoPresto (JIRA)]

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

Andy LoPresto commented on NIFI-1465:
-

The tool for upgrade should also allow the decryption and re-encryption using 
the same algorithm when the sensitive key value changes (i.e. key rollover) as 
documented in the mailing list [1]. 

[1] 
https://mail-archives.apache.org/mod_mbox/nifi-users/201607.mbox/%3CSN2PR14MB10889B2BF9E0BEDC1ECC4D7BAB310%40SN2PR14MB1088.namprd14.prod.outlook.com%3E

> Upgrade encryption of sensitive properties
> --
>
> Key: NIFI-1465
> URL: https://issues.apache.org/jira/browse/NIFI-1465
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.5.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: encryption, security
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> Currently, NiFi accepts a password and encryption algorithm in 
> `nifi.properties` which are used to encrypt all sensitive processor 
> properties throughout the application. The password defaults to empty and the 
> algorithm defaults to {{PBEWITHMD5AND256BITAES-CBC-OPENSSL}}. This algorithm:
> * uses a digest function ({{MD5}}) which is not cryptographically secure 
> [1][2][3][4]
> * uses a single iteration count [5][6]
> * limits password input to 16 characters on JVMs without the unlimited 
> strength cryptographic jurisdiction policy files installed [NIFI-1255]
> all of which combine to make it extremely insecure. We should change the 
> default algorithm to use a strong key derivation function (KDF) [7] which 
> will properly derive a key to protect the sensitive properties. 
> Because existing systems have already encrypted the properties using a key 
> derived from the original settings, we should provide a translation/upgrade 
> utility to seamlessly convert the stored values from the old password & 
> algorithm combination to the new. 
> [1] http://security.stackexchange.com/a/19908/16485
> [2] http://security.stackexchange.com/a/31846/16485
> [3] 
> http://security.stackexchange.com/questions/52461/how-weak-is-md5-as-a-password-hashing-function
> [4] http://security.stackexchange.com/a/31410/16485
> [5] http://security.stackexchange.com/a/29139/16485
> [6] https://www.openssl.org/docs/manmaster/crypto/EVP_BytesToKey.html
> [7] 
> https://cwiki.apache.org/confluence/display/NIFI/Key+Derivation+Function+Explanations



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

[GitHub] nifi pull request #649: Nifi 1413

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-1413) NiFi nodes should not fail to start just because its templates are not in-sync with the Cluster.

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1413: Ensure that if a node's templates don't match the clusters that we 
take the following actions: -Local templates remain but aren't shown in the 
cluster's templates. -Any templates from the cluster that don't exist on the 
node are added to the node. -Any conflicting template definitions are replaced 
by those in the cluster

This closes #596


> NiFi nodes should not fail to start just because its templates are not 
> in-sync with the Cluster.
> 
>
> Key: NIFI-1413
> URL: https://issues.apache.org/jira/browse/NIFI-1413
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> If a node tries to join a cluster, the node will fail to join and a 
> notification will indicate that the flow on the node is different than the 
> cluster's flow, just because the templates are different.
> Rather, we should rename the old template to ".standalone" or 
> something of that nature and then write the template to a new file if it 
> conflicts. If the template is simply missing, it should just be downloaded.
> We should make sure that NCM lists only those templates that are available to 
> it.



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

[jira] [Commented] (NIFI-1413) NiFi nodes should not fail to start just because its templates are not in-sync with the Cluster.

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1413: Rebased against master and updated templates endpoint merge to use 
template entities instead of template dto's

This closes #649


> NiFi nodes should not fail to start just because its templates are not 
> in-sync with the Cluster.
> 
>
> Key: NIFI-1413
> URL: https://issues.apache.org/jira/browse/NIFI-1413
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> If a node tries to join a cluster, the node will fail to join and a 
> notification will indicate that the flow on the node is different than the 
> cluster's flow, just because the templates are different.
> Rather, we should rename the old template to ".standalone" or 
> something of that nature and then write the template to a new file if it 
> conflicts. If the template is simply missing, it should just be downloaded.
> We should make sure that NCM lists only those templates that are available to 
> it.



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

[jira] [Commented] (NIFI-1157) Remove deprecated classes and methods

[Andy LoPresto (JIRA)]

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

Andy LoPresto commented on NIFI-1157:
-

Note for migration guide: 

The salt-less {{getCipher}} method contract was removed from 
{{PBECipherProvider}} interface and the method body was removed from all 
implementations. Only two of these implementations were marked as 
{{@Deprecated}} (in {{ScryptCipherProvider}} and {{BcryptCipherProvider}} as 
they require a generated salt meeting the requirements of the KDF), so this may 
cause unexpected compatibility problems for calling code. The salt-less 
invocations of this method in the other providers 
({{NiFiLegacyCipherProvider}}, {{OpenSSLPKCS5CipherProvider}}, and 
{{PBKDF2CipherProvider}}) were simply convenience methods which created an 
empty {{byte[ 0 ]}} salt and invoked the actual logic. However, they were not 
marked as deprecated and so users may be unaware of the change. This should not 
cause significant issues, as the solution is to add a line {{byte[] salt = new 
byte[ 0 ];}} above the method invocation and pass the empty salt. 

> Remove deprecated classes and methods
> -
>
> Key: NIFI-1157
> URL: https://issues.apache.org/jira/browse/NIFI-1157
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Tony Kurc
>Assignee: Joseph Witt
>Priority: Minor
> Fix For: 1.0.0
>
>




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

[jira] [Commented] (NIFI-1989) Need to align commons-io artifact group as per MVNCENTRAL-244

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1989:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/514
  
Wow, my apologizes. I looked for occurrences of "commons-io:commons-io" 
assuming that was the incorrect path. Looking at the commons-io source[1], the 
proper path is a group id of "commons-io" and artifact-id of "commons-io". I 
will do a double check and if it builds/works properly, I will merge this in.

[1] https://github.com/apache/commons-io


> Need to align commons-io artifact group as per MVNCENTRAL-244
> -
>
> Key: NIFI-1989
> URL: https://issues.apache.org/jira/browse/NIFI-1989
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Puspendu Banerjee
>Priority: Minor
>  Labels: artifact, dependency, maven
>
> [WARNING] While downloading org.apache.commons:commons-io:1.3.2
>   This artifact has been relocated to commons-io:commons-io:1.3.2.
>   https://issues.sonatype.org/browse/MVNCENTRAL-244



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

[jira] [Commented] (NIFI-1989) Need to align commons-io artifact group as per MVNCENTRAL-244

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1989:
--

Github user PuspenduBanerjee commented on the issue:

https://github.com/apache/nifi/pull/514
  
@JPercivall  Can you please tell me any specific instance that you might 
have already found.
I ran 
`(?s)org.apache.commons\Rcommons-io`
 but could not find any


> Need to align commons-io artifact group as per MVNCENTRAL-244
> -
>
> Key: NIFI-1989
> URL: https://issues.apache.org/jira/browse/NIFI-1989
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Puspendu Banerjee
>Priority: Minor
>  Labels: artifact, dependency, maven
>
> [WARNING] While downloading org.apache.commons:commons-io:1.3.2
>   This artifact has been relocated to commons-io:commons-io:1.3.2.
>   https://issues.sonatype.org/browse/MVNCENTRAL-244



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

[jira] [Updated] (NIFI-2087) Provenance Repository still removing events from Lucene Index

[Joseph Percivall (JIRA)]

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

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

> Provenance Repository still removing events from Lucene Index
> -
>
> Key: NIFI-2087
> URL: https://issues.apache.org/jira/browse/NIFI-2087
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> NIFI-756 was implemented in NiFi 0.3.0 to change the way in which we remove 
> events from the Lucene Indexes. It appears, though, that we still are using 
> the DeleteIndexAction to remove events from the Lucene Index, in addition to 
> the code that was added. As a result, we are removing events from the lucene 
> index, in addition to the newer mechanism of just deleting the index files 
> when they are no longer relevant.
> We should be able to simply stop using the DeleteIndexAction in 
> PersistentProvenanceRepository and then test by starting NiFi with a small 
> index shard size (say 25 MB), create a lot of data, such that some of the 
> data ages off. We should  then be able to verify that queries no longer show 
> the data and be able to look in the provenance repository directory to verify 
> that the old index-* directories are getting deleted.



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

[jira] [Commented] (NIFI-2227) Queue Listing - View button missing in FlowFile Details Dialog

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2227:
--

Github user asfgit closed the pull request at:

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


> Queue Listing - View button missing in FlowFile Details Dialog
> --
>
> Key: NIFI-2227
> URL: https://issues.apache.org/jira/browse/NIFI-2227
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>




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

[jira] [Commented] (NIFI-2109) Update radio buttons, checkboxes, etc. to angular/material design

[ASF subversion and git services (JIRA)]

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

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

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

[NIFI-2227] fix race condition for showing the view button on the flow file 
details dialog
[NIFI-2109] update check boxes
[NIFI-2226] reset controller services properties table size on dialog open
This closes #653


> Update radio buttons, checkboxes, etc. to angular/material design
> -
>
> Key: NIFI-2109
> URL: https://issues.apache.org/jira/browse/NIFI-2109
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: inputCheckbox.png
>
>




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

[jira] [Commented] (NIFI-2227) Queue Listing - View button missing in FlowFile Details Dialog

[ASF subversion and git services (JIRA)]

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

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

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

[NIFI-2227] fix race condition for showing the view button on the flow file 
details dialog
[NIFI-2109] update check boxes
[NIFI-2226] reset controller services properties table size on dialog open
This closes #653


> Queue Listing - View button missing in FlowFile Details Dialog
> --
>
> Key: NIFI-2227
> URL: https://issues.apache.org/jira/browse/NIFI-2227
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>




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

[GitHub] nifi pull request #652: NIFI-2087: Do not update the lucene index to delete ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #653: [NIFI-2227] [NIFI-2109] [NIFI-2226]

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2087) Provenance Repository still removing events from Lucene Index

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2087:
--

Github user asfgit closed the pull request at:

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


> Provenance Repository still removing events from Lucene Index
> -
>
> Key: NIFI-2087
> URL: https://issues.apache.org/jira/browse/NIFI-2087
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> NIFI-756 was implemented in NiFi 0.3.0 to change the way in which we remove 
> events from the Lucene Indexes. It appears, though, that we still are using 
> the DeleteIndexAction to remove events from the Lucene Index, in addition to 
> the code that was added. As a result, we are removing events from the lucene 
> index, in addition to the newer mechanism of just deleting the index files 
> when they are no longer relevant.
> We should be able to simply stop using the DeleteIndexAction in 
> PersistentProvenanceRepository and then test by starting NiFi with a small 
> index shard size (say 25 MB), create a lot of data, such that some of the 
> data ages off. We should  then be able to verify that queries no longer show 
> the data and be able to look in the provenance repository directory to verify 
> that the old index-* directories are getting deleted.



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

[jira] [Updated] (NIFI-1961) Test Resource - nifi.properties

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-1961:
--
Fix Version/s: (was: 1.0.0)
   1.1.0

> Test Resource - nifi.properties
> ---
>
> Key: NIFI-1961
> URL: https://issues.apache.org/jira/browse/NIFI-1961
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Core Framework
>Reporter: Matt Gilman
>Priority: Trivial
> Fix For: 1.1.0
>
>
> Many tests reference a copy of nifi.properties. These copies have become 
> increasingly stale with as the application has evolved. With the changes in 
> 1.x we should at the very least update the copies or better yet, update the 
> tests to mock out the necessary configuration to avoid the copies all 
> together.



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

[jira] [Commented] (NIFI-1961) Test Resource - nifi.properties

[Matt Gilman (JIRA)]

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

Matt Gilman commented on NIFI-1961:
---

Definitely, can slide. Thanks!

> Test Resource - nifi.properties
> ---
>
> Key: NIFI-1961
> URL: https://issues.apache.org/jira/browse/NIFI-1961
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Core Framework
>Reporter: Matt Gilman
>Priority: Trivial
> Fix For: 1.1.0
>
>
> Many tests reference a copy of nifi.properties. These copies have become 
> increasingly stale with as the application has evolved. With the changes in 
> 1.x we should at the very least update the copies or better yet, update the 
> tests to mock out the necessary configuration to avoid the copies all 
> together.



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

[jira] [Created] (NIFI-2264) Cluster - Merge history results

[Matt Gilman (JIRA)]

Matt Gilman created NIFI-2264:
-

 Summary: Cluster - Merge history results
 Key: NIFI-2264
 URL: https://issues.apache.org/jira/browse/NIFI-2264
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Matt Gilman
Assignee: Jeff Storck
Priority: Blocker
 Fix For: 1.0.0


History results need to be rolled up according to which node(s) contain the 
history of the actions.



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

[jira] [Updated] (NIFI-2115) Enhanced About Box Version Information

[James Wing (JIRA)]

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

James Wing updated NIFI-2115:
-
Attachment: screenshot-4-of-4-source-build.png
screenshot-3-of-4-release-build.png
screenshot-2-of-4-git-build.png
screenshot-1-of-4-about-expands.png

> Enhanced About Box Version Information
> --
>
> Key: NIFI-2115
> URL: https://issues.apache.org/jira/browse/NIFI-2115
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI, Tools and Build
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
> Attachments: screenshot-1-of-4-about-expands.png, 
> screenshot-2-of-4-git-build.png, screenshot-3-of-4-release-build.png, 
> screenshot-4-of-4-source-build.png
>
>
> The UI's About dialog and underlying API provide the version of NiFi, like 
> "0.7.0-SNAPSHOT".  For many bug reports and troubleshooting requests, this is 
> not very precise, especially around rapidly changing code or 
> platform-dependent behavior.  It would help if NiFi captured and displayed 
> additional information:  
> * NiFi build commit hash
> * NiFi build branch
> * NiFi build date/time
> * Java Version
> * Java Vendor (Oracle, OpenJDK)
> * OS
> Then a simple copy/paste from the about box would provide very specific 
> information about a particular NiFi installation and which code it was 
> derived from.



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

[jira] [Reopened] (NIFI-1413) NiFi nodes should not fail to start just because its templates are not in-sync with the Cluster.

[Matt Burgess (JIRA)]

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

Matt Burgess reopened NIFI-1413:


> NiFi nodes should not fail to start just because its templates are not 
> in-sync with the Cluster.
> 
>
> Key: NIFI-1413
> URL: https://issues.apache.org/jira/browse/NIFI-1413
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> If a node tries to join a cluster, the node will fail to join and a 
> notification will indicate that the flow on the node is different than the 
> cluster's flow, just because the templates are different.
> Rather, we should rename the old template to ".standalone" or 
> something of that nature and then write the template to a new file if it 
> conflicts. If the template is simply missing, it should just be downloaded.
> We should make sure that NCM lists only those templates that are available to 
> it.



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

[jira] [Resolved] (NIFI-2261) Enabling or Disabling Controller Service gives Parse Error in browser

[Mark Payne (JIRA)]

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

Mark Payne resolved NIFI-2261.
--
Resolution: Fixed

> Enabling or Disabling Controller Service gives Parse Error in browser
> -
>
> Key: NIFI-2261
> URL: https://issues.apache.org/jira/browse/NIFI-2261
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Whenever I attempt to enable or disable a controller service, the action 
> succeeds, but the browser then shows a "Parse Error" page, showing a bunch of 
> HTML. It appears that HTML is sent back instead of JSON.



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

[jira] [Updated] (NIFI-2226) Controller Services: table in Properties tab is cut-off

[Scott Aslan (JIRA)]

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

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

> Controller Services:  table in Properties tab is cut-off
> 
>
> Key: NIFI-2226
> URL: https://issues.apache.org/jira/browse/NIFI-2226
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Mac OS X, Chrome
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
>  Labels: UI
> Fix For: 1.0.0
>
> Attachments: NIFI-2226_propertiesCutoff.png
>
>
> Steps to reproduce:
> 1. Use Administration drop-down menu and select "Controller Settings"
> 2. Go to Controller Services tab and select "+"
> 3. Select a service to create ie. DBCPConnectionPool.  Select Add.
> 4. Select the Edit pencil icon for this service.
> 5. Select the Properties tab
> 6. The table in this tab is not fully visible
> See attached screenshot.  If you switch to Settings tab and then back to 
> Properties tab, the full table is then displayed.  Resizing the browser 
> window also displays the full table.
> Note: Issue is not always reproducible.  Seems to depend on whether the 
> Properties tab has been properly rendered previously.  However, I've seen 
> this show the issue fairly consistently:  while in the Controller Services 
> tab, select the View Details "i" icon and go to the properties tab, then 
> exit.  Then select the Edit pencil icon for the service and go to the 
> properties tab.



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

[jira] [Assigned] (NIFI-1795) Improve documentation regarding PropertyDescriptor name & displayName

[Andy LoPresto (JIRA)]

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

Andy LoPresto reassigned NIFI-1795:
---

Assignee: Andy LoPresto

> Improve documentation regarding PropertyDescriptor name & displayName
> -
>
> Key: NIFI-1795
> URL: https://issues.apache.org/jira/browse/NIFI-1795
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 0.6.1
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Minor
> Fix For: 1.0.0
>
>
> As evidenced in numerous pull requests, developers are often unaware of the 
> behavior of {{PropertyDescriptor}} {{name}} and {{displayName}} attributes. 
> Originally, {{name}} existed and served as both the UI display value for the 
> processor properties configuration dialog and as the unique identifier when 
> writing/reading the properties from file storage. However, a change to the 
> {{name}} value after the flow had been persisted could cause issues 
> retrieving the value from file storage. Thus, {{displayName}} was introduced 
> as the UI display value to allow for backward-compatible updates. The 
> documentation does not sufficiently explain this information and can better 
> encourage developers to provide both {{name}} and {{displayName}} attributes 
> in order to be proactive on flow compatibility and to improve the foundation 
> for internationalization and localization of the UI. 



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

[jira] [Commented] (NIFI-2261) Enabling or Disabling Controller Service gives Parse Error in browser

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2261
- Addressed issue enabling/disabling controller services where the wrong URI 
was referenced.
- Addressed with the update revisions in the controller service references.
- Addressed issue with showing the disconnected from cluster dialog on page 
load.
- Addressed issue with URI when adding a dynamic property.

This closes #654.


> Enabling or Disabling Controller Service gives Parse Error in browser
> -
>
> Key: NIFI-2261
> URL: https://issues.apache.org/jira/browse/NIFI-2261
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Whenever I attempt to enable or disable a controller service, the action 
> succeeds, but the browser then shows a "Parse Error" page, showing a bunch of 
> HTML. It appears that HTML is sent back instead of JSON.



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

[jira] [Updated] (NIFI-2109) Update radio buttons, checkboxes, etc. to angular/material design

[Scott Aslan (JIRA)]

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

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

> Update radio buttons, checkboxes, etc. to angular/material design
> -
>
> Key: NIFI-2109
> URL: https://issues.apache.org/jira/browse/NIFI-2109
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: inputCheckbox.png
>
>




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

[GitHub] nifi pull request #654: Addressing issue with enabling/disabling Controller ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #649: Nifi 1413

[mattyb149]

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/649
  
+1 LGTM built (against latest master) and tested. Want to rebase the 
commits or push as is?


---
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 #654: Addressing issue with enabling/disabling Controller Service...

[markap14]

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/654
  
These changes all look good, and they do address the issues seen. Thanks! 
Will merge to master.


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

[GitHub] nifi issue #652: NIFI-2087: Do not update the lucene index to delete expired...

[markap14]

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/652
  
@JPercivall no, that should be it. We have one other place where we use the 
DeleteFileAction but it still needs to stay there. This should take care of it.


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

[jira] [Commented] (NIFI-2204) Move Controller level bulletins out of Controller Status

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2204:
--

Github user mcgilman closed the pull request at:

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


> Move Controller level bulletins out of Controller Status
> 
>
> Key: NIFI-2204
> URL: https://issues.apache.org/jira/browse/NIFI-2204
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework, Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Controller level bulletins need to be removed from the controller status 
> endpoint and into some endpoint that is accessed through the Controller 
> resource for authorization consistency.
> All status requests are authorized under the flow but the bulletins are more 
> sensitive.



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

[jira] [Commented] (NIFI-1922) Add support for WASB / Azure Blob Storage with HDFS processors

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1922:
--

Github user atilcock closed the pull request at:

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


> Add support for WASB / Azure Blob Storage with HDFS processors
> --
>
> Key: NIFI-1922
> URL: https://issues.apache.org/jira/browse/NIFI-1922
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Joseph Witt
>
> https://hadoop.apache.org/docs/stable2/hadoop-azure/index.html
> Received two mailing list questions on this in the past couple weeks.
> We should look at what things we'd need to do in the processors to make this 
> possible.  Adding the dependency is one, anything else?



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

[GitHub] nifi pull request #500: NIFI 1922

[atilcock]

Github user atilcock closed the pull request at:

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


---
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-619) update MonitorActivity processor to be cluster friendly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-619:
-

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/575
  
@JPercivall I'm running out of time today.
Also, I realized isClustered can change after processor is created. If a 
node is disconnected from a cluster, it will be a standalone.

I'll reconsider how to proceed this, thanks.


> update MonitorActivity processor to be cluster friendly
> ---
>
> Key: NIFI-619
> URL: https://issues.apache.org/jira/browse/NIFI-619
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Brandon DeVries
>Assignee: Koji Kawamura
>Priority: Minor
> Fix For: 1.0.0
>
>
> This processor should be able to be used to monitor activity across the 
> cluster.  In its current state, alerting is based on activity of a single 
> node, not the entire cluster.
> For example, in a 2 node cluster, if system A is getting data from a given 
> flow and system B is not, system B will alert for lack of activity even 
> though the flow is functioning "normally".
> The ideal behavior would be fore an alert to be generated only if both 
> systems did not see data in the specified time.



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

[GitHub] nifi issue #575: NIFI-619: Make MonitorActivity more cluster friendly

[ijokarumawak]

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/575
  
@JPercivall I'm running out of time today.
Also, I realized isClustered can change after processor is created. If a 
node is disconnected from a cluster, it will be a standalone.

I'll reconsider how to proceed this, thanks.


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

[jira] [Commented] (NIFI-2250) Add EL support to Queue URL in GetSQS

[Joseph Percivall (JIRA)]

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

Joseph Percivall commented on NIFI-2250:


Hello [~jgresock], thanks for reporting this and adding a patch. I'm not that 
familiar with SQS but are there any performance considerations we should 
information the user of when they change URLs often with EL? or, phrased 
another way, is the library being used cache anything that gets removed when 
the URL is changed between calls?

> Add EL support to Queue URL in GetSQS
> -
>
> Key: NIFI-2250
> URL: https://issues.apache.org/jira/browse/NIFI-2250
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Joseph Gresock
>Assignee: Joseph Gresock
>Priority: Minor
> Attachments: 0001-NIFI-2250-Enabling-EL-on-GetSQS-Queue-URL.patch
>
>
> Allowing EL support in the Queue URL would allow for more dynamic 
> configuration of SQS queues (i.e., a different queue in a production vs a 
> staging environment).



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

[jira] [Commented] (NIFI-619) update MonitorActivity processor to be cluster friendly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-619:
-

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

https://github.com/apache/nifi/pull/575#discussion_r70840662
  
--- Diff: 
nifi-api/src/main/java/org/apache/nifi/components/ValidationContext.java ---
@@ -99,4 +100,9 @@
  * @return the identifier of the ProcessGroup that the component being 
validated lives in
  */
 String getProcessGroupIdentifier();
+
+/**
+ * @return the {@link NodeTypeProvider} which can be used to detect 
the node type of this NiFi instance.
+ */
+NodeTypeProvider getNodeTypeProvider();
--- End diff --

Agreed. I was thinking it'd be too much. Exposing primary state was not 
what I wanted, though.. Processor's property descriptors and validators are 
often defined in static scope, and I thought if ValidationContext provides 
cluster or not, it's useful.

I'll remove this.


> update MonitorActivity processor to be cluster friendly
> ---
>
> Key: NIFI-619
> URL: https://issues.apache.org/jira/browse/NIFI-619
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Brandon DeVries
>Assignee: Koji Kawamura
>Priority: Minor
> Fix For: 1.0.0
>
>
> This processor should be able to be used to monitor activity across the 
> cluster.  In its current state, alerting is based on activity of a single 
> node, not the entire cluster.
> For example, in a 2 node cluster, if system A is getting data from a given 
> flow and system B is not, system B will alert for lack of activity even 
> though the flow is functioning "normally".
> The ideal behavior would be fore an alert to be generated only if both 
> systems did not see data in the specified time.



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

[jira] [Commented] (NIFI-2115) Enhanced About Box Version Information

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2115:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/583
  
I did not push my updates correctly yesterday, I just fixed the branch.


> Enhanced About Box Version Information
> --
>
> Key: NIFI-2115
> URL: https://issues.apache.org/jira/browse/NIFI-2115
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI, Tools and Build
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
>
> The UI's About dialog and underlying API provide the version of NiFi, like 
> "0.7.0-SNAPSHOT".  For many bug reports and troubleshooting requests, this is 
> not very precise, especially around rapidly changing code or 
> platform-dependent behavior.  It would help if NiFi captured and displayed 
> additional information:  
> * NiFi build commit hash
> * NiFi build branch
> * NiFi build date/time
> * Java Version
> * Java Vendor (Oracle, OpenJDK)
> * OS
> Then a simple copy/paste from the about box would provide very specific 
> information about a particular NiFi installation and which code it was 
> derived from.



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

[GitHub] nifi issue #583: NIFI-2115 Detailed Version Info for About Box

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/583
  
I did not push my updates correctly yesterday, I just fixed the branch.


---
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 #654: Addressing issue with enabling/disabling Controller ...

[mcgilman]

GitHub user mcgilman opened a pull request:

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

Addressing issue with enabling/disabling Controller Services

NIFI-2261:
- Addressed issue enabling/disabling controller services where the wrong 
URI was referenced.
- Addressed with the update revisions in the controller service references.
- Addressed issue with showing the disconnected from cluster dialog on page 
load.
- Addressed issue with URI when adding a dynamic property.

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

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

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

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


commit e380aa6e503c2b7d910b53ad62ba1429c71b3007
Author: Matt Gilman 
Date:   2016-07-14T16:43:18Z

NIFI-2261
- Addressed issue enabling/disabling controller services where the wrong 
URI was referenced.
- Addressed with the update revisions in the controller service references.
- Addressed issue with showing the disconnected from cluster dialog on page 
load.
- Addressed issue with URI when adding a dynamic property.




---
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-2261) Enabling or Disabling Controller Service gives Parse Error in browser

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2261:
--

GitHub user mcgilman opened a pull request:

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

Addressing issue with enabling/disabling Controller Services

NIFI-2261:
- Addressed issue enabling/disabling controller services where the wrong 
URI was referenced.
- Addressed with the update revisions in the controller service references.
- Addressed issue with showing the disconnected from cluster dialog on page 
load.
- Addressed issue with URI when adding a dynamic property.

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

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

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

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


commit e380aa6e503c2b7d910b53ad62ba1429c71b3007
Author: Matt Gilman 
Date:   2016-07-14T16:43:18Z

NIFI-2261
- Addressed issue enabling/disabling controller services where the wrong 
URI was referenced.
- Addressed with the update revisions in the controller service references.
- Addressed issue with showing the disconnected from cluster dialog on page 
load.
- Addressed issue with URI when adding a dynamic property.




> Enabling or Disabling Controller Service gives Parse Error in browser
> -
>
> Key: NIFI-2261
> URL: https://issues.apache.org/jira/browse/NIFI-2261
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Whenever I attempt to enable or disable a controller service, the action 
> succeeds, but the browser then shows a "Parse Error" page, showing a bunch of 
> HTML. It appears that HTML is sent back instead of JSON.



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

[jira] [Commented] (NIFI-2115) Enhanced About Box Version Information

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2115:
---

i do agree not tagging this to 1.0 yet is ideal so if you're willing to hold 
off on tagging a release version i am definitely on board.

As for clusters my point is that some clusters will have heterogenous makeup 
among nodes in terms of build version, java version, etc.. and in such cases 
how do we render that difference given the about box in a cluster settings is 
speaking on behalf of the whole cluster.

having said all this - these are useful bits of data and we should definitely 
progress this.

> Enhanced About Box Version Information
> --
>
> Key: NIFI-2115
> URL: https://issues.apache.org/jira/browse/NIFI-2115
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI, Tools and Build
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
>
> The UI's About dialog and underlying API provide the version of NiFi, like 
> "0.7.0-SNAPSHOT".  For many bug reports and troubleshooting requests, this is 
> not very precise, especially around rapidly changing code or 
> platform-dependent behavior.  It would help if NiFi captured and displayed 
> additional information:  
> * NiFi build commit hash
> * NiFi build branch
> * NiFi build date/time
> * Java Version
> * Java Vendor (Oracle, OpenJDK)
> * OS
> Then a simple copy/paste from the about box would provide very specific 
> information about a particular NiFi installation and which code it was 
> derived from.



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

[jira] [Updated] (NIFI-2109) Update radio buttons, checkboxes, etc. to angular/material design

[Rob Moran (JIRA)]

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

Rob Moran updated NIFI-2109:

Attachment: inputCheckbox.png

For a quick win we can update inputCheckbox.png to better match the new UI. See 
attached file.

> Update radio buttons, checkboxes, etc. to angular/material design
> -
>
> Key: NIFI-2109
> URL: https://issues.apache.org/jira/browse/NIFI-2109
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
>Priority: Minor
> Attachments: inputCheckbox.png
>
>




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

[jira] [Commented] (NIFI-619) update MonitorActivity processor to be cluster friendly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-619:
-

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

https://github.com/apache/nifi/pull/575#discussion_r70837879
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/FlowController.java
 ---
@@ -1004,7 +1004,7 @@ public ProcessorNode createProcessor(final String 
type, String id, final boolean
 creationSuccessful = false;
 }
 
-final ValidationContextFactory validationContextFactory = new 
StandardValidationContextFactory(controllerServiceProvider);
+final ValidationContextFactory validationContextFactory = new 
StandardValidationContextFactory(controllerServiceProvider, this);
--- End diff --

But yes, if one tries to cast it as FlowController, it's possible..


> update MonitorActivity processor to be cluster friendly
> ---
>
> Key: NIFI-619
> URL: https://issues.apache.org/jira/browse/NIFI-619
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Brandon DeVries
>Assignee: Koji Kawamura
>Priority: Minor
> Fix For: 1.0.0
>
>
> This processor should be able to be used to monitor activity across the 
> cluster.  In its current state, alerting is based on activity of a single 
> node, not the entire cluster.
> For example, in a 2 node cluster, if system A is getting data from a given 
> flow and system B is not, system B will alert for lack of activity even 
> though the flow is functioning "normally".
> The ideal behavior would be fore an alert to be generated only if both 
> systems did not see data in the specified time.



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

[jira] [Assigned] (NIFI-2226) Controller Services: table in Properties tab is cut-off

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2226:
-

Assignee: Scott Aslan

> Controller Services:  table in Properties tab is cut-off
> 
>
> Key: NIFI-2226
> URL: https://issues.apache.org/jira/browse/NIFI-2226
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
> Environment: Mac OS X, Chrome
>Reporter: Andrew Lim
>Assignee: Scott Aslan
>Priority: Minor
>  Labels: UI
> Fix For: 1.0.0
>
> Attachments: NIFI-2226_propertiesCutoff.png
>
>
> Steps to reproduce:
> 1. Use Administration drop-down menu and select "Controller Settings"
> 2. Go to Controller Services tab and select "+"
> 3. Select a service to create ie. DBCPConnectionPool.  Select Add.
> 4. Select the Edit pencil icon for this service.
> 5. Select the Properties tab
> 6. The table in this tab is not fully visible
> See attached screenshot.  If you switch to Settings tab and then back to 
> Properties tab, the full table is then displayed.  Resizing the browser 
> window also displays the full table.
> Note: Issue is not always reproducible.  Seems to depend on whether the 
> Properties tab has been properly rendered previously.  However, I've seen 
> this show the issue fairly consistently:  while in the Controller Services 
> tab, select the View Details "i" icon and go to the properties tab, then 
> exit.  Then select the Edit pencil icon for the service and go to the 
> properties tab.



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

[jira] [Commented] (NIFI-619) update MonitorActivity processor to be cluster friendly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-619:
-

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

https://github.com/apache/nifi/pull/575#discussion_r70837645
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/FlowController.java
 ---
@@ -1004,7 +1004,7 @@ public ProcessorNode createProcessor(final String 
type, String id, final boolean
 creationSuccessful = false;
 }
 
-final ValidationContextFactory validationContextFactory = new 
StandardValidationContextFactory(controllerServiceProvider);
+final ValidationContextFactory validationContextFactory = new 
StandardValidationContextFactory(controllerServiceProvider, this);
--- End diff --

I don't like it, too. So I passed it as NodeTypeProvider, only isClustered 
and isPrimaryNode are accessible.


> update MonitorActivity processor to be cluster friendly
> ---
>
> Key: NIFI-619
> URL: https://issues.apache.org/jira/browse/NIFI-619
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Brandon DeVries
>Assignee: Koji Kawamura
>Priority: Minor
> Fix For: 1.0.0
>
>
> This processor should be able to be used to monitor activity across the 
> cluster.  In its current state, alerting is based on activity of a single 
> node, not the entire cluster.
> For example, in a 2 node cluster, if system A is getting data from a given 
> flow and system B is not, system B will alert for lack of activity even 
> though the flow is functioning "normally".
> The ideal behavior would be fore an alert to be generated only if both 
> systems did not see data in the specified time.



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

[jira] [Updated] (NIFI-2227) Queue Listing - View button missing in FlowFile Details Dialog

[Scott Aslan (JIRA)]

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

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

> Queue Listing - View button missing in FlowFile Details Dialog
> --
>
> Key: NIFI-2227
> URL: https://issues.apache.org/jira/browse/NIFI-2227
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>




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

[jira] [Commented] (NIFI-2145) When saving flow, NiFi should allow the flow to automatically be backed up

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2145:
--

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/614
  
@markap14 @JPercivall Glad to hear! Thank you for reviewing and merging!


> When saving flow, NiFi should allow the flow to automatically be backed up
> --
>
> Key: NIFI-2145
> URL: https://issues.apache.org/jira/browse/NIFI-2145
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Core Framework
>Reporter: Mark Payne
>Assignee: Koji Kawamura
> Fix For: 1.0.0
>
>
> Each time that a user updates the NiFi flow, the new flow is written to the 
> flow.xml.gz on each node. When this occurs, we should provide the option of 
> also writing the flow.xml.gz to an 'archive' folder, using a filename based 
> on the current time. We should also ensure that we keep old flows for X 
> (configurable) amount of time and only use a max of some configurable amount 
> of disk space.
> StandardXMLFlowConfigurationDAO (in nifi-framework-core) already has a method 
> for `save(FlowController controller, boolean archive)` but 'false' is always 
> passed as the 'archive' field. We should instead pass in `true` if configured 
> to archive. Additionally, we should change the archive filename so that it is 
> based on a user-readable date/time, such as 
> flow-2016-06-29-11-10-50am.xml.gz, for instance, for a flow that was saved at 
> 11:10:50 AM on June 29, 2016. This allows an admin to easily revert a flow 
> back to how it was at some point in history.
> Changes required to implement this include:
> 1. Update nifi.properties to include new properties (with the suggested 
> defaults that may need to be adjusted):
> - nifi.flow.configuration.archive.enabled=true
> - nifi.flow.configuration.archive.max.time=30 days
> - nifi.flow.configuration.archive.max.storage=500 MB
> There already is a property named `nifi.flow.configuration.archive.dir` that 
> should be used to specify where to save the archived flow. This is used 
> currently only when the user clicks the 'archive' button in the UI.
> 2. Update StandardFlowService.saveFlowChanges(TimeUnit delayUnit, long delay) 
> so that it passes a value of `true` for the 'archive' flag when calling the 
> overridden saveFlowChanges method in the case that the 
> `nifi.flow.configuration.archive.enabled` property is set to true (default).
> 3. Update StandardXMLFlowConfigurationDAO.createArchiveFile() to use a more 
> user-friendly filename, as described above.
> 4. Update StandardXMLFlowConfigurationDAO.save() so that the `if (archive) {` 
> branch first cleans up old/expired flows so that the `archive` directory is 
> smaller than the configured max storage space and so that any archived flow 
> that is older than the configured `nifi.flow.configuration.archive.max.time` 
> property is removed.



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

[GitHub] nifi pull request #614: NIFI-2145: Auto flow.xml archive

[ijokarumawak]

Github user ijokarumawak closed the pull request at:

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


---
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-2145) When saving flow, NiFi should allow the flow to automatically be backed up

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2145:
--

Github user ijokarumawak closed the pull request at:

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


> When saving flow, NiFi should allow the flow to automatically be backed up
> --
>
> Key: NIFI-2145
> URL: https://issues.apache.org/jira/browse/NIFI-2145
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Core Framework
>Reporter: Mark Payne
>Assignee: Koji Kawamura
> Fix For: 1.0.0
>
>
> Each time that a user updates the NiFi flow, the new flow is written to the 
> flow.xml.gz on each node. When this occurs, we should provide the option of 
> also writing the flow.xml.gz to an 'archive' folder, using a filename based 
> on the current time. We should also ensure that we keep old flows for X 
> (configurable) amount of time and only use a max of some configurable amount 
> of disk space.
> StandardXMLFlowConfigurationDAO (in nifi-framework-core) already has a method 
> for `save(FlowController controller, boolean archive)` but 'false' is always 
> passed as the 'archive' field. We should instead pass in `true` if configured 
> to archive. Additionally, we should change the archive filename so that it is 
> based on a user-readable date/time, such as 
> flow-2016-06-29-11-10-50am.xml.gz, for instance, for a flow that was saved at 
> 11:10:50 AM on June 29, 2016. This allows an admin to easily revert a flow 
> back to how it was at some point in history.
> Changes required to implement this include:
> 1. Update nifi.properties to include new properties (with the suggested 
> defaults that may need to be adjusted):
> - nifi.flow.configuration.archive.enabled=true
> - nifi.flow.configuration.archive.max.time=30 days
> - nifi.flow.configuration.archive.max.storage=500 MB
> There already is a property named `nifi.flow.configuration.archive.dir` that 
> should be used to specify where to save the archived flow. This is used 
> currently only when the user clicks the 'archive' button in the UI.
> 2. Update StandardFlowService.saveFlowChanges(TimeUnit delayUnit, long delay) 
> so that it passes a value of `true` for the 'archive' flag when calling the 
> overridden saveFlowChanges method in the case that the 
> `nifi.flow.configuration.archive.enabled` property is set to true (default).
> 3. Update StandardXMLFlowConfigurationDAO.createArchiveFile() to use a more 
> user-friendly filename, as described above.
> 4. Update StandardXMLFlowConfigurationDAO.save() so that the `if (archive) {` 
> branch first cleans up old/expired flows so that the `archive` directory is 
> smaller than the configured max storage space and so that any archived flow 
> that is older than the configured `nifi.flow.configuration.archive.max.time` 
> property is removed.



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

[GitHub] nifi issue #614: NIFI-2145: Auto flow.xml archive

[ijokarumawak]

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/614
  
@markap14 @JPercivall Glad to hear! Thank you for reviewing and merging!


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

[jira] [Updated] (NIFI-2257) Refresh UpdateAttribute Processor advanced shell

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2257:
---
Fix Version/s: 1.0.0

> Refresh UpdateAttribute Processor advanced shell
> 
>
> Key: NIFI-2257
> URL: https://issues.apache.org/jira/browse/NIFI-2257
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>




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

[jira] [Commented] (NIFI-2115) Enhanced About Box Version Information

[James Wing (JIRA)]

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

James Wing commented on NIFI-2115:
--

I will provide some screenshots.  Would you please elaborate a bit on what is 
either desirable cluster support or pitfalls to avoid?  I have not yet 
implemented any features specific to clusters.  Perhaps we're not ready to tag 
this for 1.0.

> Enhanced About Box Version Information
> --
>
> Key: NIFI-2115
> URL: https://issues.apache.org/jira/browse/NIFI-2115
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI, Tools and Build
>Affects Versions: 1.0.0
>Reporter: James Wing
>Assignee: James Wing
>Priority: Minor
>
> The UI's About dialog and underlying API provide the version of NiFi, like 
> "0.7.0-SNAPSHOT".  For many bug reports and troubleshooting requests, this is 
> not very precise, especially around rapidly changing code or 
> platform-dependent behavior.  It would help if NiFi captured and displayed 
> additional information:  
> * NiFi build commit hash
> * NiFi build branch
> * NiFi build date/time
> * Java Version
> * Java Vendor (Oracle, OpenJDK)
> * OS
> Then a simple copy/paste from the about box would provide very specific 
> information about a particular NiFi installation and which code it was 
> derived from.



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

[jira] [Commented] (NIFI-2087) Provenance Repository still removing events from Lucene Index

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2087:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/652
  
I see this change only taking effect when the repo is initialized. Is there 
really no other place that should be updated?


> Provenance Repository still removing events from Lucene Index
> -
>
> Key: NIFI-2087
> URL: https://issues.apache.org/jira/browse/NIFI-2087
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> NIFI-756 was implemented in NiFi 0.3.0 to change the way in which we remove 
> events from the Lucene Indexes. It appears, though, that we still are using 
> the DeleteIndexAction to remove events from the Lucene Index, in addition to 
> the code that was added. As a result, we are removing events from the lucene 
> index, in addition to the newer mechanism of just deleting the index files 
> when they are no longer relevant.
> We should be able to simply stop using the DeleteIndexAction in 
> PersistentProvenanceRepository and then test by starting NiFi with a small 
> index shard size (say 25 MB), create a lot of data, such that some of the 
> data ages off. We should  then be able to verify that queries no longer show 
> the data and be able to look in the provenance repository directory to verify 
> that the old index-* directories are getting deleted.



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

[GitHub] nifi issue #652: NIFI-2087: Do not update the lucene index to delete expired...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/652
  
I see this change only taking effect when the repo is initialized. Is there 
really no other place that should be updated?


---
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-2173) LDAP provider referral strategy typo in Code

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2173:
--

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/629
  
I'll test this with an LDAP server when I get a chance :)


> LDAP provider referral strategy typo in Code
> 
>
> Key: NIFI-2173
> URL: https://issues.apache.org/jira/browse/NIFI-2173
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.6.0
>Reporter: Matthew Clarke
>Priority: Minor
>  Labels: newbie
> Fix For: 1.0.0
>
>
> The LDAP referral strategy set in the login-identity-providers.xml file 
> should support IGNORE, FOLLOW, or THROW.  If the referral strategy is set to 
> IGNORE, NiFi will fail to start and complain that the possible values are 
> [follow, ignore, throw].  The issue is that the code has a typo where IGNORE 
> is spelled INGORE.  
> WORKAROUND: Users can get around the issue by configuring the referral 
> strategy for INGORE.



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

[jira] [Commented] (NIFI-2227) Queue Listing - View button missing in FlowFile Details Dialog

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2227:
--

GitHub user scottyaslan opened a pull request:

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

[NIFI-2227] fix race condition for showing the view button on the flo…

…w file details dialog

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

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

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

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


commit 0e6e7b96a2b1613f573b924d100c6685f761daea
Author: Scott Aslan 
Date:   2016-07-14T15:57:22Z

[NIFI-2227] fix race condition for showing the view button on the flow file 
details dialog




> Queue Listing - View button missing in FlowFile Details Dialog
> --
>
> Key: NIFI-2227
> URL: https://issues.apache.org/jira/browse/NIFI-2227
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>




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

[GitHub] nifi issue #529: NIFI-2028: Fixed Site-to-Site Transit URI

[ijokarumawak]

Github user ijokarumawak commented on the issue:

https://github.com/apache/nifi/pull/529
  
@JPercivall Fixed conflicts and tested with the latest code base. Please 
take a look. Thanks!


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

[jira] [Commented] (NIFI-619) update MonitorActivity processor to be cluster friendly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-619:
-

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

https://github.com/apache/nifi/pull/575#discussion_r70831015
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/FlowController.java
 ---
@@ -1004,7 +1004,7 @@ public ProcessorNode createProcessor(final String 
type, String id, final boolean
 creationSuccessful = false;
 }
 
-final ValidationContextFactory validationContextFactory = new 
StandardValidationContextFactory(controllerServiceProvider);
+final ValidationContextFactory validationContextFactory = new 
StandardValidationContextFactory(controllerServiceProvider, this);
--- End diff --

I really don't like passing the FlowController itself. Why can't it just 
pass the value? Or if it needs to be able to be updated, it could pass a shared 
reference.


> update MonitorActivity processor to be cluster friendly
> ---
>
> Key: NIFI-619
> URL: https://issues.apache.org/jira/browse/NIFI-619
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Brandon DeVries
>Assignee: Koji Kawamura
>Priority: Minor
> Fix For: 1.0.0
>
>
> This processor should be able to be used to monitor activity across the 
> cluster.  In its current state, alerting is based on activity of a single 
> node, not the entire cluster.
> For example, in a 2 node cluster, if system A is getting data from a given 
> flow and system B is not, system B will alert for lack of activity even 
> though the flow is functioning "normally".
> The ideal behavior would be fore an alert to be generated only if both 
> systems did not see data in the specified time.



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

[jira] [Resolved] (NIFI-1947) Update Cluster Awareness

[Matt Gilman (JIRA)]

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

Matt Gilman resolved NIFI-1947.
---
Resolution: Fixed

> Update Cluster Awareness
> 
>
> Key: NIFI-1947
> URL: https://issues.apache.org/jira/browse/NIFI-1947
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> With the NCM removed for version 1.0.0, we now have a situation where a user 
> can navigate to one node in a cluster while the node is disconnected. If the 
> node is then reconnected, the UI does not update to indicate to the user that 
> the node is now part of a cluster.



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

[jira] [Resolved] (NIFI-2082) When a node is disconnected from cluster, it should be made extremely obvious in the UI

[Matt Gilman (JIRA)]

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

Matt Gilman resolved NIFI-2082.
---
Resolution: Fixed

> When a node is disconnected from cluster, it should be made extremely obvious 
> in the UI
> ---
>
> Key: NIFI-2082
> URL: https://issues.apache.org/jira/browse/NIFI-2082
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Matt Gilman
>Priority: Critical
> Fix For: 1.0.0
>
> Attachments: nifi-2082_cluster-warning.png, 
> nifi-2082_disconnected-node-dialog-2.png, 
> nifi-2082_disconnected-node-dialog.png
>
>
> Because we now have a zero-master clustering paradigm, it's possible to open 
> the UI on a node that is disconnected from the cluster. In this case, changes 
> made to the UI will be accepted, but they will not be replicated to the 
> cluster. As a result, the flow will be out-of-sync with the cluster, and in 
> order to get the node back to the cluster, the changes would have to be 
> undone and the work potentially lost (user could create a template to save 
> the changes but may not know what all they changed).
> The UI should make it very obvious that the node is disconnected and that any 
> changes that made will not be replicated to the cluster.



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

[GitHub] nifi issue #652: NIFI-2087: Do not update the lucene index to delete expired...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/652
  
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-1947) Update Cluster Awareness

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1947:
--

Github user asfgit closed the pull request at:

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


> Update Cluster Awareness
> 
>
> Key: NIFI-1947
> URL: https://issues.apache.org/jira/browse/NIFI-1947
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> With the NCM removed for version 1.0.0, we now have a situation where a user 
> can navigate to one node in a cluster while the node is disconnected. If the 
> node is then reconnected, the UI does not update to indicate to the user that 
> the node is now part of a cluster.



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

[jira] [Commented] (NIFI-1947) Update Cluster Awareness

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-1947 NIFI-2082:
- Making it more obviously when a nodes cluster state changes.
- Showing which node is the cluster coordinator.

This closes #651


> Update Cluster Awareness
> 
>
> Key: NIFI-1947
> URL: https://issues.apache.org/jira/browse/NIFI-1947
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> With the NCM removed for version 1.0.0, we now have a situation where a user 
> can navigate to one node in a cluster while the node is disconnected. If the 
> node is then reconnected, the UI does not update to indicate to the user that 
> the node is now part of a cluster.



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

[GitHub] nifi pull request #651: UI - Cluster Awareness

[asfgit]

Github user asfgit closed the pull request at:

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


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