[jira] [Commented] (NIFI-2034) NiFi is always loading a specific version of httpcore to classpath
[
https://issues.apache.org/jira/browse/NIFI-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
> org.apache.http.impl
[jira] [Commented] (NIFI-1148) Add processor to GetEmail supporting IMAP and POP3
[ https://issues.apache.org/jira/browse/NIFI-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[ https://issues.apache.org/jira/browse/NIFI-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Comment Edited] (NIFI-2028) Site-to-Site Transit URI is inconsistent
[ https://issues.apache.org/jira/browse/NIFI-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378567#comment-15378567 ] Koji Kawamura edited comment on NIFI-2028 at 7/14/16 11:13 PM: --- [~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. Hostname is masked for privacy reason, but both have same value. was (Author: ijokarumawak): [~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] [Commented] (NIFI-2028) Site-to-Site Transit URI is inconsistent
[ https://issues.apache.org/jira/browse/NIFI-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[ 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
[ 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
[ 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
[ 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-2028) Site-to-Site Transit URI is inconsistent
[ https://issues.apache.org/jira/browse/NIFI-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura updated NIFI-2028: Description: 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| was: 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| > 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: > - 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.por
[jira] [Updated] (NIFI-1896) Extract Extension API into separate module
[
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
[
https://issues.apache.org/jira/browse/NIFI-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
[jira] [Commented] (NIFI-1896) Extract Extension API into separate module
[
https://issues.apache.org/jira/browse/NIFI-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378513#comment-15378513
]
ASF subversion and git services commented on NIFI-1896:
---
Commit d1129706e235548daaf4eecf7001b244300761e9 in nifi's branch
refs/heads/master from [~aldrin]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d112970 ]
NIFI-1896 This closes #650. Refactored nifi-api into nifi-framework-api and
other locations. The nifi-api is specific to that which is needed for intended
extension points.
> 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...
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
[ 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
[ https://issues.apache.org/jira/browse/NIFI-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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...
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
[ https://issues.apache.org/jira/browse/NIFI-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378482#comment-15378482 ] ASF GitHub Bot commented on NIFI-2020: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/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-2020) Enhance JoltTransformJSON processor to support custom transforms
[ https://issues.apache.org/jira/browse/NIFI-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[ https://issues.apache.org/jira/browse/NIFI-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[ https://issues.apache.org/jira/browse/NIFI-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[ https://issues.apache.org/jira/browse/NIFI-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
[GitHub] nifi issue #587: NIFI-2116 Initial Draft for Spanish readme.md
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. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (NIFI-2222) Jetty reversal of KeyStore, Key passwords in nifi.properties
[ https://issues.apache.org/jira/browse/NIFI-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Wing resolved NIFI-. -- Resolution: Fixed Assignee: Bryan Rosander Fix Version/s: 1.0.0 > 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 >Assignee: Bryan Rosander > Fix For: 1.0.0 > > > 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] [Commented] (NIFI-2116) Translate Documentation Into Spanish
[ https://issues.apache.org/jira/browse/NIFI-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378388#comment-15378388 ] ASF GitHub Bot commented on NIFI-2116: -- Github user olegz commented on the issue: https://github.com/apache/nifi/pull/587 I would really love to merge this one as I truly believe these types of PRs are so important to grow the community, but I don't speak Spanish, it would be nice if another Spanish-speaking community member would go through it. > 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)
[GitHub] nifi issue #632: NIFI-2222 - reversing SslContext properties set by keyStore...
Github user jvwing commented on the issue: https://github.com/apache/nifi/pull/632 The functionality works, correctly handling different keystore and key passwords. The JettyServerTest tests look good, and are a needed addition to the package. All tests and contrib-check pass. Thank you, @brosander. --- 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-2222) Jetty reversal of KeyStore, Key passwords in nifi.properties
[ https://issues.apache.org/jira/browse/NIFI-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378387#comment-15378387 ] ASF GitHub Bot commented on NIFI-: -- Github user jvwing commented on the issue: https://github.com/apache/nifi/pull/632 The functionality works, correctly handling different keystore and key passwords. The JettyServerTest tests look good, and are a needed addition to the package. All tests and contrib-check pass. Thank you, @brosander. > 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-2266) GetHTTP and PutHTTP use hard-coded TLS protocol version
Andy LoPresto created NIFI-2266:
---
Summary: GetHTTP and PutHTTP use hard-coded TLS protocol version
Key: NIFI-2266
URL: https://issues.apache.org/jira/browse/NIFI-2266
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Affects Versions: 0.6.1, 0.7.0
Reporter: Andy LoPresto
Assignee: Andy LoPresto
Fix For: 1.0.0
As pointed out on the mailing list [1], the {{GetHTTP}} (and likely
{{PutHTTP}}) processors use a hard-coded TLS protocol version. {{PostHTTP}}
also did this and was fixed by [NIFI-1688].
The same fix should apply here and unit tests already exist which can be
applied to the other processors as well.
For future notice, {{InvokeHTTP}} is a better processor for generic HTTP
operations and has supported reading the TLS protocol version from the
{{SSLContextService}} for some time.
[1]
https://lists.apache.org/thread.html/a48e2ebbc2231d685491ae6b856c760620efca5bff2c7249f915b24d@%3Cdev.nifi.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi issue #587: NIFI-2116 Initial Draft for Spanish readme.md
Github user olegz commented on the issue: https://github.com/apache/nifi/pull/587 I would really love to merge this one as I truly believe these types of PRs are so important to grow the community, but I don't speak Spanish, it would be nice if another Spanish-speaking community member would go through 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-2222) Jetty reversal of KeyStore, Key passwords in nifi.properties
[ https://issues.apache.org/jira/browse/NIFI-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
[GitHub] nifi pull request #632: NIFI-2222 - reversing SslContext properties set by k...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/632 --- 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-2222) Jetty reversal of KeyStore, Key passwords in nifi.properties
[ https://issues.apache.org/jira/browse/NIFI-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378382#comment-15378382 ] ASF subversion and git services commented on NIFI-: --- Commit 1da18a3f40a45a5896c1a409024bf46ec1e4b7da in nifi's branch refs/heads/master from [~bryanrosan...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=1da18a3 ] NIFI- - Fixing SslContextFactory Properties set by keyStorePasswd and keyPasswd This closes #632 Signed-off-by: James Wing > 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 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
[ 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
[ 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
[ https://issues.apache.org/jira/browse/NIFI-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378349#comment-15378349 ] ASF GitHub Bot commented on NIFI-1688: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/624 > 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
[ https://issues.apache.org/jira/browse/NIFI-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[ https://issues.apache.org/jira/browse/NIFI-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
[GitHub] nifi issue #624: NIFI-1688 PostHTTP processor now uses protocol specified by...
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! --- 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 #624: NIFI-1688 PostHTTP processor now uses protocol speci...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/624 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Assigned] (NIFI-2107) Other panels like 'content-viewer' still using old style
[ 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] [Updated] (NIFI-1413) NiFi nodes should not fail to start just because its templates are not in-sync with the Cluster.
[ https://issues.apache.org/jira/browse/NIFI-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-1413: --- Assignee: Mark Payne > 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 >Assignee: 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-2086) Provenance Event window: selected tab is not highlighted properly due to misaligned border
[ https://issues.apache.org/jira/browse/NIFI-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Updated] (NIFI-2045) ConsumeMQTT can lose a message if session commit fails
[ https://issues.apache.org/jira/browse/NIFI-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-2045: -- Fix Version/s: 1.0.0 > ConsumeMQTT can lose a message if session commit fails > -- > > Key: NIFI-2045 > URL: https://issues.apache.org/jira/browse/NIFI-2045 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Bryan Rosander >Assignee: Bryan Rosander >Priority: Critical > Fix For: 1.0.0 > > > ConsumeMQTT removes the received message from the queue before committing the > session. This means that if the session commit fails and the session rolls > back, the message will be lost. > https://github.com/apache/nifi/blob/f47af1ce8336c9305916f00738976f3505b01b0b/nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java#L292 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2045) ConsumeMQTT can lose a message if session commit fails
[ https://issues.apache.org/jira/browse/NIFI-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-2045: -- Assignee: Bryan Rosander > ConsumeMQTT can lose a message if session commit fails > -- > > Key: NIFI-2045 > URL: https://issues.apache.org/jira/browse/NIFI-2045 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Bryan Rosander >Assignee: Bryan Rosander >Priority: Critical > Fix For: 1.0.0 > > > ConsumeMQTT removes the received message from the queue before committing the > session. This means that if the session commit fails and the session rolls > back, the message will be lost. > https://github.com/apache/nifi/blob/f47af1ce8336c9305916f00738976f3505b01b0b/nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java#L292 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1868) Add support for Hive Streaming
[ https://issues.apache.org/jira/browse/NIFI-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-1868: --- Status: Open (was: Patch Available) > Add support for Hive Streaming > -- > > Key: NIFI-1868 > URL: https://issues.apache.org/jira/browse/NIFI-1868 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Matt Burgess >Assignee: Matt Burgess > Fix For: 1.0.0 > > > Traditionally adding new data into Hive requires gathering a large amount of > data onto HDFS and then periodically adding a new partition. This is > essentially a “batch insertion”. Insertion of new data into an existing > partition is not permitted. Hive Streaming API allows data to be pumped > continuously into Hive. The incoming data can be continuously committed in > small batches of records into an existing Hive partition or table. Once data > is committed it becomes immediately visible to all Hive queries initiated > subsequently. > This case is to add a PutHiveStreaming processor to NiFi, to leverage the > Hive Streaming API to allow continuous streaming of data into a Hive > partition/table. -- 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
[ 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
[ https://issues.apache.org/jira/browse/NIFI-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-1989: -- Assignee: Puspendu Banerjee > 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
[ 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)
[jira] [Commented] (NIFI-1989) Need to align commons-io artifact group as per MVNCENTRAL-244
[ https://issues.apache.org/jira/browse/NIFI-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378282#comment-15378282 ] ASF subversion and git services commented on NIFI-1989: --- Commit 6d2168049a1dceefe0ca4277954b35c0861fdacb in nifi's branch refs/heads/master from [~puspendu.baner...@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=6d21680 ] fixes NIFI-1989 This closes #514 Signed-off-by: jpercivall > 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)
[GitHub] nifi pull request #514: fixes NIFI-1989
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. ---
[jira] [Commented] (NIFI-1989) Need to align commons-io artifact group as per MVNCENTRAL-244
[ https://issues.apache.org/jira/browse/NIFI-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378285#comment-15378285 ] ASF GitHub Bot commented on NIFI-1989: -- Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/514 Haha, glad it helped > 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
[ https://issues.apache.org/jira/browse/NIFI-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378284#comment-15378284 ] ASF GitHub Bot commented on NIFI-1989: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/514 > 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-1989) Need to align commons-io artifact group as per MVNCENTRAL-244
[ https://issues.apache.org/jira/browse/NIFI-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-1989: --- Resolution: Fixed Status: Resolved (was: Patch Available) > 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)
[GitHub] nifi issue #514: fixes NIFI-1989
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
[ https://issues.apache.org/jira/browse/NIFI-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
[GitHub] nifi issue #514: fixes 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 :) --- 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-2107) Other panels like 'content-viewer' still using old style
[ 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] [Commented] (NIFI-2107) Other panels like 'content-viewer' still using old style
[ https://issues.apache.org/jira/browse/NIFI-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378262#comment-15378262 ] Rob Moran commented on NIFI-2107: - For *.message-pane* class change (background property value) #d1dee5 to #ff Replace *bg-error.png* with the new version (attached) > 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 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2227) Queue Listing - View button missing in FlowFile Details Dialog
[ 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)
[jira] [Commented] (NIFI-1688) PostHTTP does not honor SSLContextService Protocols
[ https://issues.apache.org/jira/browse/NIFI-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378211#comment-15378211 ] ASF GitHub Bot commented on NIFI-1688: -- Github user apiri commented on the issue: https://github.com/apache/nifi/pull/624 reviewing > 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)
[GitHub] nifi issue #624: NIFI-1688 PostHTTP processor now uses protocol specified by...
Github user apiri commented on the issue: https://github.com/apache/nifi/pull/624 reviewing --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-2062) Upgrade AWS SDK
[ https://issues.apache.org/jira/browse/NIFI-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-2062: -- Resolution: Fixed Status: Resolved (was: Patch Available) > 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-2062) Upgrade AWS SDK
[ https://issues.apache.org/jira/browse/NIFI-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378186#comment-15378186 ] ASF GitHub Bot commented on NIFI-2062: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/562 > 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-2062) Upgrade AWS SDK
[ https://issues.apache.org/jira/browse/NIFI-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378185#comment-15378185 ] ASF subversion and git services commented on NIFI-2062: --- Commit a7c5b88a470d832e1690faede9a5b2f606196342 in nifi's branch refs/heads/master from [~jameswing] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=a7c5b88 ] NIFI-2062 AWS SDK Update: * Updated the AWS SDK dependency version to 1.11.8 * Removed GetDynamoDBTest references to JsonObject class dropped from AWS SDK * Fixed integration test ITPutSNS.testPublish() - exception from not evaluating expressions * Ignored integration test ITPutS3Object.testS3MultipartAgeoff() - did not work before or after SDK update This closes #562. Signed-off-by: Aldrin Piri > 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)
[GitHub] nifi pull request #562: NIFI-2062 AWS SDK Update:
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/562 --- 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
[ https://issues.apache.org/jira/browse/NIFI-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378183#comment-15378183 ] ASF GitHub Bot commented on NIFI-1989: -- 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. > 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)
[GitHub] nifi issue #514: fixes NIFI-1989
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:
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
[ https://issues.apache.org/jira/browse/NIFI-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[
https://issues.apache.org/jira/browse/NIFI-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[
https://issues.apache.org/jira/browse/NIFI-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
[jira] [Updated] (NIFI-1413) NiFi nodes should not fail to start just because its templates are not in-sync with the Cluster.
[ https://issues.apache.org/jira/browse/NIFI-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-1413: --- Resolution: Fixed Status: Resolved (was: Patch Available) > 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)
[GitHub] nifi pull request #649: Nifi 1413
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.
[ https://issues.apache.org/jira/browse/NIFI-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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.
[ https://issues.apache.org/jira/browse/NIFI-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
[GitHub] nifi issue #514: fixes 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 --- 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-1157) Remove deprecated classes and methods
[ https://issues.apache.org/jira/browse/NIFI-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Witt updated NIFI-1157: -- Labels: migration (was: ) > 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 > Labels: migration > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1157) Remove deprecated classes and methods
[
https://issues.apache.org/jira/browse/NIFI-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[ https://issues.apache.org/jira/browse/NIFI-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Updated] (NIFI-2226) Controller Services: table in Properties tab is cut-off
[ https://issues.apache.org/jira/browse/NIFI-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-2226: -- Resolution: Fixed Status: Resolved (was: Patch Available) > 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-1989) Need to align commons-io artifact group as per MVNCENTRAL-244
[ https://issues.apache.org/jira/browse/NIFI-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
[GitHub] nifi issue #514: fixes 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 --- 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-2109) Update radio buttons, checkboxes, etc. to angular/material design
[ https://issues.apache.org/jira/browse/NIFI-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan updated NIFI-2109: -- Resolution: Fixed Status: Resolved (was: Patch Available) > 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] [Updated] (NIFI-2087) Provenance Repository still removing events from Lucene Index
[ 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-2226) Controller Services: table in Properties tab is cut-off
[ https://issues.apache.org/jira/browse/NIFI-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378119#comment-15378119 ] ASF subversion and git services commented on NIFI-2226: --- 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 > 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-2227) Queue Listing - View button missing in FlowFile Details Dialog
[ https://issues.apache.org/jira/browse/NIFI-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[ https://issues.apache.org/jira/browse/NIFI-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[ https://issues.apache.org/jira/browse/NIFI-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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 ...
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. ---
[jira] [Commented] (NIFI-2087) Provenance Repository still removing events from Lucene Index
[ https://issues.apache.org/jira/browse/NIFI-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378114#comment-15378114 ] ASF subversion and git services commented on NIFI-2087: --- Commit 2540573d77c026585eed03bf0d7cd2f042bb1df2 in nifi's branch refs/heads/master from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2540573 ] NIFI-2087: Do not update the lucene index to delete expired events. Instead, just wait for the entire index to expire and remove the files for that index. This is much more efficient. This closes #652 Signed-off-by: jpercivall > 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 pull request #653: [NIFI-2227] [NIFI-2109] [NIFI-2226]
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
[ https://issues.apache.org/jira/browse/NIFI-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[ 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
[ https://issues.apache.org/jira/browse/NIFI-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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 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)
[GitHub] nifi issue #652: NIFI-2087: Do not update the lucene index to delete expired...
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/652 +1 Did a contrib check build, visually verified and ran a lot of data with a small index size and saw it work as expected. Will merge in. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2087) Provenance Repository still removing events from Lucene Index
[ https://issues.apache.org/jira/browse/NIFI-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378096#comment-15378096 ] ASF GitHub Bot commented on NIFI-2087: -- Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/652 +1 Did a contrib check build, visually verified and ran a lot of data with a small index size and saw it work as expected. Will merge in. > 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] [Created] (NIFI-2263) Update History to work in a Cluster
Matt Gilman created NIFI-2263: - Summary: Update History to work in a Cluster Key: NIFI-2263 URL: https://issues.apache.org/jira/browse/NIFI-2263 Project: Apache NiFi Issue Type: Bug Components: Core Framework, Core UI Reporter: Matt Gilman Assignee: Matt Gilman Priority: Blocker Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2115) Enhanced About Box Version Information
[ 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)
