Re: [VOTE] Release Apache NiFi Registry 0.5.0
+1, binding comments: hashes and signature good build and tests good L good verified integration and basic flow versioning functionality On Fri, Aug 23, 2019 at 4:15 PM Marc Parisi wrote: > +1 ( binding ) > > Performed checks as described in the helper guide, performing my usual > testing. Looks great! > > On Fri, Aug 23, 2019 at 3:54 PM Matt Gilman > wrote: > > > +1 (binding) > > > > Ran through helper. Verified recent improvements to ignore case when > > defining groups from a directory server. Tested other basic operations. > > Looked great. > > > > Thanks for RMing Bryan!! > > > > On Wed, Aug 21, 2019 at 2:31 PM Bryan Bende wrote: > > > > > Hello, > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi Registry nifi-registry-0.5.0. > > > > > > The source zip, including signatures, digests, etc. can be found at: > > > https://repository.apache.org/content/repositories/orgapachenifi-1147 > > > > > > The Git tag is nifi-registry-0.5.0-RC1 > > > The Git commit ID is 8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > > > > > > > > > https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > > > > > > Checksums of nifi-registry-0.5.0-source-release.zip: > > > SHA256: > 804948c2f3d6d32f88c37c1827d1c9c2d1f842f0ef7e7d953d24e76b152a093b > > > SHA512: > > > > > > 0ae202b64ad3b3ab3dadb71b9dea210ac4c8eb1cf3922f10a71d175df75ec069e8a039bcc961d1969a6ac7417da4cc5bd4d0cc1e8515d88be6bd55b7c8c9bce9 > > > > > > Release artifacts are signed with the following key: > > > https://people.apache.org/keys/committer/bbende.asc > > > > > > KEYS file available here: > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > 28 issues were closed/resolved for this release: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12345561 > > > > > > Release note highlights can be found here: > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.5.0 > > > > > > The vote will be open for 72 hours. > > > Please download the release candidate and evaluate the necessary items > > > including checking hashes, signatures, build from source, and test. > > > Then please vote: > > > > > > [ ] +1 Release this package as nifi-registry-0.5.0 > > > [ ] +0 no opinion > > > [ ] -1 Do not release this package because... > > > > > >
Re: NiFi 1.8.0 and Registry 0.5
Good to know, thanks. On Fri, Aug 23, 2019 at 4:17 PM Bryan Bende wrote: > Not that I'm aware of. If you are using 0.4.0 registry then I would > expect 0.5.0 to drop in fine. > > On Fri, Aug 23, 2019 at 4:13 PM Mike Thomsen > wrote: > > > > Are there any expected API incompatibilities between the two? > > > > Thanks, > > > > Mike >
Re: NiFi 1.8.0 and Registry 0.5
Not that I'm aware of. If you are using 0.4.0 registry then I would expect 0.5.0 to drop in fine. On Fri, Aug 23, 2019 at 4:13 PM Mike Thomsen wrote: > > Are there any expected API incompatibilities between the two? > > Thanks, > > Mike
NiFi 1.8.0 and Registry 0.5
Are there any expected API incompatibilities between the two? Thanks, Mike
Re: [VOTE] Release Apache NiFi Registry 0.5.0
+1 (binding) Ran through helper. Verified recent improvements to ignore case when defining groups from a directory server. Tested other basic operations. Looked great. Thanks for RMing Bryan!! On Wed, Aug 21, 2019 at 2:31 PM Bryan Bende wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache > NiFi Registry nifi-registry-0.5.0. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1147 > > The Git tag is nifi-registry-0.5.0-RC1 > The Git commit ID is 8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > > https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > > Checksums of nifi-registry-0.5.0-source-release.zip: > SHA256: 804948c2f3d6d32f88c37c1827d1c9c2d1f842f0ef7e7d953d24e76b152a093b > SHA512: > 0ae202b64ad3b3ab3dadb71b9dea210ac4c8eb1cf3922f10a71d175df75ec069e8a039bcc961d1969a6ac7417da4cc5bd4d0cc1e8515d88be6bd55b7c8c9bce9 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/bbende.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 28 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12345561 > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.5.0 > > The vote will be open for 72 hours. > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, and test. > Then please vote: > > [ ] +1 Release this package as nifi-registry-0.5.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
How to generate usage documentation for custom Processors
Hello,
I'm having trouble generating documentation for a set of custom NiFi
processors. I posted a question with all the details here on Stack
Overflow.
https://stackoverflow.com/questions/57530465/how-to-generate-usage-documentation-for-custom-processors
Below is a copy of what I posted. Thanks for any help with this.
David P.
I have created several custom NiFi processors, but have been unable to
get usage documentation to be generated. 'Usage' documentation refers
to right clicking on a processor and selecting 'Usage', which should
bring up documentation about that specific processor. The
documentation panel is displayed, but none of my custom processors are
present.
I used several NiFi documentation tags on my custom processor classes
including several Read/Written attributes. The code compiles and unit
tests without any issues. The build reports
[INFO] Generating documentation for NiFi extensions in the NAR...
According to the developer guide documentation is supposed to
automatically be generated.
I also tried creating an additionalDetails.html file and putting it in
the nar according the documentation.
This file should exist within a directory whose name is the
fully-qualified name of the Processor, and this directory’s parent
should be named docs and exist in the root of the Processor’s jar.
However, that broke NiFi and I found this in the logs.
=== End Processor types ===
2019-08-16 15:16:36,100 WARN [main]
org.apache.nifi.web.server.JettyServer Failed to start web server...
shutting down.
java.lang.NullPointerException: null
at
org.apache.nifi.documentation.DocGenerator.generate(DocGenerator.java:62)
at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:932)
at org.apache.nifi.NiFi.(NiFi.java:158)
at org.apache.nifi.NiFi.(NiFi.java:72)
at org.apache.nifi.NiFi.main(NiFi.java:297)
2019-08-16 15:16:36,100 INFO [Thread-1] org.apache.nifi.NiFi
Initiating shutdown of Jetty web server...
I'm using the standard nifi-nar-maven-plugin to generate the nar file.
Here's a snippet of my pom.xmlfile.
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;>;
4.0.0
com.myorg
nifi-mylib
nar
0.0.3
nifi-mylib
UTF-8
1.8
1.8
1.9.2
org.apache.nifi
nifi-api
${nifi.version}
...
org.apache.nifi
nifi-nar-maven-plugin
1.3.1
true
org.apache.maven.plugins
maven-surefire-plugin
2.15
The generated .nar (without the additionalDetails.html file) load
correctly and appear in the list of processors. It's just the Usage
documentation that I can't get to work.
Re: [VOTE] Release Apache NiFi Registry 0.5.0
+1 binding. Did the checks described above and created a few buckets. On Fri, Aug 23, 2019 at 10:30 AM Pierre Villard wrote: > +1 (binding) - thanks for RM'ing Bryan! > > Went through the release helper guide and tested basic registry operations > in a secured environment with a various set of providers configuration. > > Pierre > > Le ven. 23 août 2019 à 16:24, Andrew Lim a > écrit : > > > +1 (non-binding) > > > > -Ran full clean install on OS X (10.14.2) > > -Performed basic integration testing with a secured NiFi instance > (1.9.2): > > adding registry clients, placing a process group under version control, > > saving different versions, changing versions, importing a version, > stopping > > version control, changing bucket policies > > -Tested new public bucket feature > > -Tested more granular proxy policies > > > > Drew > > > > > On Aug 21, 2019, at 1:54 PM, Bryan Bende wrote: > > > > > > Hello, > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi Registry nifi-registry-0.5.0. > > > > > > The source zip, including signatures, digests, etc. can be found at: > > > https://repository.apache.org/content/repositories/orgapachenifi-1147 > > > > > > The Git tag is nifi-registry-0.5.0-RC1 > > > The Git commit ID is 8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > > > > > > https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > > > > > > Checksums of nifi-registry-0.5.0-source-release.zip: > > > SHA256: > 804948c2f3d6d32f88c37c1827d1c9c2d1f842f0ef7e7d953d24e76b152a093b > > > SHA512: > > > 0ae202b64ad3b3ab3dadb71b9dea210ac4c8eb1cf3922f10a71d175df75ec069e8a039bcc961d1969a6ac7417da4cc5bd4d0cc1e8515d88be6bd55b7c8c9bce9 > > > > > > Release artifacts are signed with the following key: > > > https://people.apache.org/keys/committer/bbende.asc > > > > > > KEYS file available here: > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > 28 issues were closed/resolved for this release: > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12345561 > > > > > > Release note highlights can be found here: > > > > > > https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.5.0 > > > > > > The vote will be open for 72 hours. > > > Please download the release candidate and evaluate the necessary items > > > including checking hashes, signatures, build from source, and test. > > > Then please vote: > > > > > > [ ] +1 Release this package as nifi-registry-0.5.0 > > > [ ] +0 no opinion > > > [ ] -1 Do not release this package because... > > > > >
Re: nifi deploy automation - variables pass through (incl controller services)
Well there are two different encryption parts here - encryption-at-rest and encryption-in-transit... Encryption-at-rest would have to be part of your script that is calling the REST API. Somehow you create a config file with encrypted values, and your script needs to read those in an decrypt them in memory and then put them into the content that will be sent in the HTTP PUT or POST request. Encryption-in-transit would be handled by the fact that you would be making an HTTPS request to NiFi, so the contents of the POST or PUT request are encrypted in transit. This is the same thing that is happening if you were in the NiFi UI and typed in a password into the sensitive property field. On Fri, Aug 23, 2019 at 11:35 AM sivasankar Reddy wrote: > > Hi Bryan, > > Thanks for the reply. > Able to get the json object and set the property for Password. However value > of password can be either referred from config file (its plain string visible > in config). Is there any way that password is encrypted and this set property > can take decrypted value. > > this way we ensure that password is sensitive. Any other ideas to achieve this > > > Regards, > Siva > > > > On 2019/08/22 17:38:37, Bryan Bende wrote: > > The parameters work is on-going and will be in the next release which > > is 1.10.0. Releases don't really have specific timelines, but > > generally they happen every few months. Most likely 1.10.0 is a couple > > of weeks away, but depends on when active work is completed and when > > someone volunteers to make a release. > > > > There is no timeline for the "set-property" command since it was just > > suggested as a new feature in this email thread :) It requires someone > > creating a JIRA and deciding to work on it. > > > > All of the functionality in the CLI and NiPyAPI, and even NiFi's own > > UI, is based on the REST API. So you can still perform a "set > > property" by using the REST API to modify the configuration of a > > processor, the CLI would just make it easier so that you wouldn't have > > to understand the lower level API details. The best way to understand > > the API calls is to us the UI while you have Chrome Dev Tools open, > > and then perform the action you are interested in and look at the > > requests made on the Network tab. You'll be able to see what URLs are > > called and what the request and response bodies look like. > > > > On Thu, Aug 22, 2019 at 11:46 AM sivasankar Reddy > > wrote: > > > > > > Hi Bryan, > > > > > > Thanks for the reply. looks like even set-property will be a new feature, > > > as current CLI doesn't have that. > > > > > > Could you please share timelines of these features if its in roadmap. > > > 1. "set-property" > > > 2. “parameters” > > > > > > The only option currently is set to set sensitive parameters manually? or > > > any other option through CLI > > > > > > Regards, > > > Siva > > > > > > On 2019/08/22 04:10:46, Bryan Bende wrote: > > > > Currently there isn’t a good way with the CLI, we would need to add a > > > > command like set-property that took the id of a component, and the name > > > > and > > > > value for a property. > > > > > > > > The next release will have a new feature called “parameters” which will > > > > solve this problem. You’ll be able to use a parameter in a sensitive > > > > property and then use CLI to set parameter values. > > > > > > > > On Wed, Aug 21, 2019 at 12:29 PM sivasankar Reddy > > > > wrote: > > > > > > > > > Hi Bryan, > > > > > > > > > > Thanks for the update. Could you please mention about > > > > > sensitive parameters aspect from deployment point of view using CLI. > > > > > > > > > > How to set the sensitive parameters values after pg-import. > > > > > > > > > > Regards, > > > > > Siva > > > > > > > > > > On 2019/08/21 11:47:49, Bryan Bende wrote: > > > > > > It does not, I was saying we could easily improve the command to add > > > > > those > > > > > > parameters. > > > > > > > > > > > > On Wed, Aug 21, 2019 at 6:36 AM sivasankar Reddy > > > > > > > > > > > > wrote: > > > > > > > > > > > > > Hi Bryan, > > > > > > > > > > > > > > Thanks for the update. Does the existing pg-import takes optional > > > > > params > > > > > > > for x/y coordinates. If yes can you share the sample command as > > > > > pg-import > > > > > > > --help doesn't has this info. > > > > > > > > > > > > > > Regards, > > > > > > > siva > > > > > > > > > > > > > > > > > > > > > On 2019/08/20 22:19:23, Bryan Bende wrote: > > > > > > > > Hello, > > > > > > > > > > > > > > > > 1) pg-import will keeping finding a location that does not > > > > > > > > overlap > > > > > with > > > > > > > any > > > > > > > > existing process groups, so it is more of auto layout. We could > > > > > easily > > > > > > > add > > > > > > > > optional params for x/y coordinates. > > > > > > > > > > > > > > > > 2) Both are fine choices.. CLI is more geared towards simple > > > > > commands, > > > > > > > > where as with NiPyApi you could more easily
Re: nifi deploy automation - variables pass through (incl controller services)
Hi Bryan, Thanks for the reply. Able to get the json object and set the property for Password. However value of password can be either referred from config file (its plain string visible in config). Is there any way that password is encrypted and this set property can take decrypted value. this way we ensure that password is sensitive. Any other ideas to achieve this Regards, Siva On 2019/08/22 17:38:37, Bryan Bende wrote: > The parameters work is on-going and will be in the next release which > is 1.10.0. Releases don't really have specific timelines, but > generally they happen every few months. Most likely 1.10.0 is a couple > of weeks away, but depends on when active work is completed and when > someone volunteers to make a release. > > There is no timeline for the "set-property" command since it was just > suggested as a new feature in this email thread :) It requires someone > creating a JIRA and deciding to work on it. > > All of the functionality in the CLI and NiPyAPI, and even NiFi's own > UI, is based on the REST API. So you can still perform a "set > property" by using the REST API to modify the configuration of a > processor, the CLI would just make it easier so that you wouldn't have > to understand the lower level API details. The best way to understand > the API calls is to us the UI while you have Chrome Dev Tools open, > and then perform the action you are interested in and look at the > requests made on the Network tab. You'll be able to see what URLs are > called and what the request and response bodies look like. > > On Thu, Aug 22, 2019 at 11:46 AM sivasankar Reddy > wrote: > > > > Hi Bryan, > > > > Thanks for the reply. looks like even set-property will be a new feature, > > as current CLI doesn't have that. > > > > Could you please share timelines of these features if its in roadmap. > > 1. "set-property" > > 2. “parameters” > > > > The only option currently is set to set sensitive parameters manually? or > > any other option through CLI > > > > Regards, > > Siva > > > > On 2019/08/22 04:10:46, Bryan Bende wrote: > > > Currently there isn’t a good way with the CLI, we would need to add a > > > command like set-property that took the id of a component, and the name > > > and > > > value for a property. > > > > > > The next release will have a new feature called “parameters” which will > > > solve this problem. You’ll be able to use a parameter in a sensitive > > > property and then use CLI to set parameter values. > > > > > > On Wed, Aug 21, 2019 at 12:29 PM sivasankar Reddy > > > wrote: > > > > > > > Hi Bryan, > > > > > > > > Thanks for the update. Could you please mention about > > > > sensitive parameters aspect from deployment point of view using CLI. > > > > > > > > How to set the sensitive parameters values after pg-import. > > > > > > > > Regards, > > > > Siva > > > > > > > > On 2019/08/21 11:47:49, Bryan Bende wrote: > > > > > It does not, I was saying we could easily improve the command to add > > > > those > > > > > parameters. > > > > > > > > > > On Wed, Aug 21, 2019 at 6:36 AM sivasankar Reddy > > > > > > > > > > wrote: > > > > > > > > > > > Hi Bryan, > > > > > > > > > > > > Thanks for the update. Does the existing pg-import takes optional > > > > params > > > > > > for x/y coordinates. If yes can you share the sample command as > > > > pg-import > > > > > > --help doesn't has this info. > > > > > > > > > > > > Regards, > > > > > > siva > > > > > > > > > > > > > > > > > > On 2019/08/20 22:19:23, Bryan Bende wrote: > > > > > > > Hello, > > > > > > > > > > > > > > 1) pg-import will keeping finding a location that does not overlap > > > > with > > > > > > any > > > > > > > existing process groups, so it is more of auto layout. We could > > > > easily > > > > > > add > > > > > > > optional params for x/y coordinates. > > > > > > > > > > > > > > 2) Both are fine choices.. CLI is more geared towards simple > > > > commands, > > > > > > > where as with NiPyApi you could more easily write complex logic in > > > > > > Python. > > > > > > > With CLI you would write a wrapper shell script that made > > > > > > > individual > > > > > > calls > > > > > > > to the CLI. I think it is really just a matter of preference. > > > > > > > > > > > > > > -Bryan > > > > > > > > > > > > > > > > > > > > > On Tue, Aug 20, 2019 at 5:11 PM sivasankar Reddy < > > > > mail2ms...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Hi Bryan, > > > > > > > > > > > > > > > > Thanks for your input. I would like to know more > > > > > > > > > > > > > > > > 1. how does CLI pg-import works if already canvas has 100 to > > > > > > > > 150 > > > > > > flows. > > > > > > > > Will CLI pg-import always place the flow in canvas which can be > > > > easily > > > > > > > > located. As nipyapi has location(x,y) during deploy flow. > > > > > > > > > > > > > > > > 2. From enterprise usage, do you recommend toolkit CLI vs > > > > > > > > nipyapi, > > > > it > > > > > > > >
Re: [VOTE] Release Apache NiFi Registry 0.5.0
+1 (binding) - thanks for RM'ing Bryan! Went through the release helper guide and tested basic registry operations in a secured environment with a various set of providers configuration. Pierre Le ven. 23 août 2019 à 16:24, Andrew Lim a écrit : > +1 (non-binding) > > -Ran full clean install on OS X (10.14.2) > -Performed basic integration testing with a secured NiFi instance (1.9.2): > adding registry clients, placing a process group under version control, > saving different versions, changing versions, importing a version, stopping > version control, changing bucket policies > -Tested new public bucket feature > -Tested more granular proxy policies > > Drew > > > On Aug 21, 2019, at 1:54 PM, Bryan Bende wrote: > > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi Registry nifi-registry-0.5.0. > > > > The source zip, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachenifi-1147 > > > > The Git tag is nifi-registry-0.5.0-RC1 > > The Git commit ID is 8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > > > https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > > > > Checksums of nifi-registry-0.5.0-source-release.zip: > > SHA256: 804948c2f3d6d32f88c37c1827d1c9c2d1f842f0ef7e7d953d24e76b152a093b > > SHA512: > 0ae202b64ad3b3ab3dadb71b9dea210ac4c8eb1cf3922f10a71d175df75ec069e8a039bcc961d1969a6ac7417da4cc5bd4d0cc1e8515d88be6bd55b7c8c9bce9 > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/bbende.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > 28 issues were closed/resolved for this release: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12345561 > > > > Release note highlights can be found here: > > > https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.5.0 > > > > The vote will be open for 72 hours. > > Please download the release candidate and evaluate the necessary items > > including checking hashes, signatures, build from source, and test. > > Then please vote: > > > > [ ] +1 Release this package as nifi-registry-0.5.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... > >
Re: [VOTE] Release Apache NiFi Registry 0.5.0
+1 (non-binding) -Ran full clean install on OS X (10.14.2) -Performed basic integration testing with a secured NiFi instance (1.9.2): adding registry clients, placing a process group under version control, saving different versions, changing versions, importing a version, stopping version control, changing bucket policies -Tested new public bucket feature -Tested more granular proxy policies Drew > On Aug 21, 2019, at 1:54 PM, Bryan Bende wrote: > > Hello, > > I am pleased to be calling this vote for the source release of Apache > NiFi Registry nifi-registry-0.5.0. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1147 > > The Git tag is nifi-registry-0.5.0-RC1 > The Git commit ID is 8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > > Checksums of nifi-registry-0.5.0-source-release.zip: > SHA256: 804948c2f3d6d32f88c37c1827d1c9c2d1f842f0ef7e7d953d24e76b152a093b > SHA512: > 0ae202b64ad3b3ab3dadb71b9dea210ac4c8eb1cf3922f10a71d175df75ec069e8a039bcc961d1969a6ac7417da4cc5bd4d0cc1e8515d88be6bd55b7c8c9bce9 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/bbende.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 28 issues were closed/resolved for this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12345561 > > Release note highlights can be found here: > https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.5.0 > > The vote will be open for 72 hours. > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, and test. > Then please vote: > > [ ] +1 Release this package as nifi-registry-0.5.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because...
nifi-stateless failurePort usage
Hello devs, I've been working with nifi-stateless quite a bit recently because it's something we would like to start using after the 1.10 release. I've come across a few things that I was hoping for some clarification on from someone else who is familiar with these features before I create a jira and start working on a fix. I've had some trouble with the failurePorts configuration. My flows are not exiting when flowfiles are sent to the failure port. From the code [1], it looks like failure ports must be at the root PG level of the flow. Has anyone else been able to get failurePorts to work as expected? I also have an open PR [2] that is ready for another round of review. It would be great to get this merged before 1.10 if possible. Thanks! David [1] https://github.com/apache/nifi/blob/master/nifi-stateless/nifi-stateless-core/src/main/java/org/apache/nifi/stateless/core/StatelessFlow.java#L242-L251 [2] https://github.com/apache/nifi/pull/3651 -- Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Re: [VOTE] Release Apache NiFi Registry 0.5.0
Thanks for working on this, Bryan. +1(non-binding). - Verified hashes - Confirmed a build - Started secured NiFi Registry - Tested version control operations for some dataflows - Browsed public bucket as anonymous user - Created a public bucket, and browsed it as anonymous user - Used DatabaseFlowPersistenceProvider, and connected to the same external DB from two NiFi Registry instances On 2019/08/21 17:54:48, Bryan Bende wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache > NiFi Registry nifi-registry-0.5.0. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1147 > > The Git tag is nifi-registry-0.5.0-RC1 > The Git commit ID is 8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16 > > Checksums of nifi-registry-0.5.0-source-release.zip: > SHA256: 804948c2f3d6d32f88c37c1827d1c9c2d1f842f0ef7e7d953d24e76b152a093b > SHA512: > 0ae202b64ad3b3ab3dadb71b9dea210ac4c8eb1cf3922f10a71d175df75ec069e8a039bcc961d1969a6ac7417da4cc5bd4d0cc1e8515d88be6bd55b7c8c9bce9 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/bbende.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 28 issues were closed/resolved for this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12345561 > > Release note highlights can be found here: > https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.5.0 > > The vote will be open for 72 hours. > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, and test. > Then please vote: > > [ ] +1 Release this package as nifi-registry-0.5.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >
