Re: [VOTE] Release Apache NiFi 1.11.0 (rc3)

[Marc Parisi]

+1 (binding)

Ran through helper guide for validation.

Built on pop os and osx.

Ran a high throughout test flow, where I encountered no regressions across
several record oriented processors and non secure site to site.

Thanks,
Marc


On Tue, Jan 21, 2020, 4:43 PM Andrew Lim  wrote:

> +1 (non-binding)
>
> -Ran full clean install on OS X (Catalina 10.15.2)
> -Tested secure NiFi with secure NiFi Registry
> -Ran basic flows successfully
> -Reviewed core UI and documentation fixes/updates
>
> In setting up my secure NiFi and secure NiFi registry, I used the NiFi TLS
> Toolkit [1] to create my config files and certs. I was able to access the
> UIs of both apps using Safari but not able to with Chrome due to a
> NET::ERR_CERT_REVOKED error which I had never seen before.  Turns out this
> is a known issue on Catalina [2]. MacOSX 10.15 requires certs to be valid
> for 825 days or less and a minimum 2048 bit key.  By default, the TLS
> Toolkit sets the validity to 1095 days and the number of bits for generated
> keys to 2048. Creating new certs with the required 825 validity solved the
> issue. I will add a note to the Toolkit Guide for this new requirement [3].
>
> Drew
>
> [1]
> https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#tls_toolkit
> <
> https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#tls_toolkit
> >
> [2] https://support.apple.com/en-us/HT210176 <
> https://support.apple.com/en-us/HT210176>
> [3] https://issues.apache.org/jira/browse/NIFI-7053 <
> https://issues.apache.org/jira/browse/NIFI-7053>
>
>
> > On Jan 19, 2020, at 3:21 PM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > nifi-1.11.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1155
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.0/
> >
> > A helpful reminder on how the release candidate verification process
> works:
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >
> > The Git tag is nifi-1.11.0-RC3
> > The Git commit ID is 633408bce7ad34dad727ed9c4edfd36a224f3f12
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=633408bce7ad34dad727ed9c4edfd36a224f3f12
> >
> > Checksums of nifi-1.11.0-source-release.zip:
> > SHA256: 0e2d77265fc7cedfbdb9588df1dd7f456fd18b6288d65eb5e21befe23af7c567
> > SHA512:
> >
> 4880fa3482b3e8d8eed439848fe0a6596826d7ad46425a91b0dd4a4bcd178259327380b24045b7991dbdf8449abdfdda145786b6863eb603f6cef3b9e0ae8ec1
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 129 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12346451
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.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-1.11.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

Re: [VOTE] Release Apache NiFi 1.11.0 (rc3)

[Andrew Lim]

+1 (non-binding)

-Ran full clean install on OS X (Catalina 10.15.2)
-Tested secure NiFi with secure NiFi Registry
-Ran basic flows successfully
-Reviewed core UI and documentation fixes/updates

In setting up my secure NiFi and secure NiFi registry, I used the NiFi TLS 
Toolkit [1] to create my config files and certs. I was able to access the UIs 
of both apps using Safari but not able to with Chrome due to a 
NET::ERR_CERT_REVOKED error which I had never seen before.  Turns out this is a 
known issue on Catalina [2]. MacOSX 10.15 requires certs to be valid for 825 
days or less and a minimum 2048 bit key.  By default, the TLS Toolkit sets the 
validity to 1095 days and the number of bits for generated keys to 2048. 
Creating new certs with the required 825 validity solved the issue. I will add 
a note to the Toolkit Guide for this new requirement [3].

Drew

[1] https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#tls_toolkit 

[2] https://support.apple.com/en-us/HT210176 

[3] https://issues.apache.org/jira/browse/NIFI-7053 



> On Jan 19, 2020, at 3:21 PM, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.11.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1155
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.0/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.11.0-RC3
> The Git commit ID is 633408bce7ad34dad727ed9c4edfd36a224f3f12
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=633408bce7ad34dad727ed9c4edfd36a224f3f12
> 
> Checksums of nifi-1.11.0-source-release.zip:
> SHA256: 0e2d77265fc7cedfbdb9588df1dd7f456fd18b6288d65eb5e21befe23af7c567
> SHA512:
> 4880fa3482b3e8d8eed439848fe0a6596826d7ad46425a91b0dd4a4bcd178259327380b24045b7991dbdf8449abdfdda145786b6863eb603f6cef3b9e0ae8ec1
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 129 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12346451
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.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-1.11.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: [VOTE] Release Apache NiFi 1.11.0 (rc3)

[Matt Burgess]

+1 (binding)

Ran through release helper, tried various flows including some new
features (PutRecord, e.g.) PutRecord might not have made the
improvements list, changelog, release notes, etc. for 1.11 due to an
omission in Jira, but the Jira has since been corrected [1]

-Matt

[1] https://issues.apache.org/jira/browse/NIFI-6947

On Sun, Jan 19, 2020 at 3:21 PM Joe Witt  wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.11.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1155
>
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.0/
>
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>
> The Git tag is nifi-1.11.0-RC3
> The Git commit ID is 633408bce7ad34dad727ed9c4edfd36a224f3f12
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=633408bce7ad34dad727ed9c4edfd36a224f3f12
>
> Checksums of nifi-1.11.0-source-release.zip:
> SHA256: 0e2d77265fc7cedfbdb9588df1dd7f456fd18b6288d65eb5e21befe23af7c567
> SHA512:
> 4880fa3482b3e8d8eed439848fe0a6596826d7ad46425a91b0dd4a4bcd178259327380b24045b7991dbdf8449abdfdda145786b6863eb603f6cef3b9e0ae8ec1
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 129 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12346451
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.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-1.11.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: [VOTE] Release Apache NiFi 1.11.0 (rc3)

[Shayne Burgess]

+1

- Deploy on 3 node cluster in Azure
- Ran test data flow with high throughput
- Verified new changes in RC3

Looks good! Nice work everyone

On Tue, Jan 21, 2020 at 6:11 AM Arpad Boda  wrote:

> +1
>
>- Verified signature, checksums.
>- Built properly.
>- Started NiFi, sent flowfiles from MiNiFi, designed flow to handle
>them.
>
>
> Created https://issues.apache.org/jira/browse/NIFI-7049 in the meanwhile
> as:
>
>- SFTP tests can fail on "clean" hosts
>- The underlying behavior seems to be unintentional and error-prone
>
>
> I don't consider it as a blocker as it has been working this way for quite
> a while.
>
>
> On Tue, Jan 21, 2020 at 1:33 AM Andy LoPresto 
> wrote:
>
> > +1, binding.
> >
> > Verified normal signatures and checksums, deployed instance, and verified
> > selected Jiras were included in the build.
> >
> > Pierre, I opened NIFI-7048 to resolve the issue you documented below.
> > Thanks.
> >
> > Andy LoPresto
> > alopre...@apache.org
> > alopresto.apa...@gmail.com
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
> > > On Jan 20, 2020, at 11:33 AM, Pierre Villard <
> > pierre.villard...@gmail.com> wrote:
> > >
> > > +1 (binding) release this package as nifi-1.11.0
> > >
> > > Went through the usual check process. Also deployed a 3-nodes secured
> > > cluster with OIDC behind a load balancer with Terraform on Google
> Cloud.
> > > Tested various flows. It looks good to me.
> > >
> > > Some notes - I did run into a test failure (that I didn't have before)
> > but
> > > it was because JAVA_HOME was not set properly. I copy the error in case
> > it
> > > happens to someone else. This is on recently added tests:
> > >
> > > [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed:
> > > 0.666 s <<< FAILURE! - in
> org.apache.nifi.io.socket.SSLContextFactoryTest
> > > [ERROR]
> > >
> >
> testShouldVerifyKeystoreWithEmptyKeyPassword(org.apache.nifi.io.socket.SSLContextFactoryTest)
> > > Time elapsed: 0.051 s  <<< ERROR!
> > > java.io.FileNotFoundException: null/jre/lib/security/cacerts (No such
> > file
> > > or directory)
> > > at
> > >
> >
> org.apache.nifi.io.socket.SSLContextFactoryTest.testShouldVerifyKeystoreWithEmptyKeyPassword(SSLContextFactoryTest.groovy:162)
> > > [ERROR]
> > >
> >
> testShouldVerifyKeystoreWithDifferentKeyPassword(org.apache.nifi.io.socket.SSLContextFactoryTest)
> > > Time elapsed: 0.002 s  <<< ERROR!
> > > java.io.FileNotFoundException: null/jre/lib/security/cacerts (No such
> > file
> > > or directory)
> > > at
> > >
> >
> org.apache.nifi.io.socket.SSLContextFactoryTest.testShouldVerifyKeystoreWithDifferentKeyPassword(SSLContextFactoryTest.groovy:138)
> > > [ERROR]
> > >
> >
> testShouldVerifyKeystoreWithSameKeyPassword(org.apache.nifi.io.socket.SSLContextFactoryTest)
> > > Time elapsed: 0.001 s  <<< ERROR!
> > > java.io.FileNotFoundException: null/jre/lib/security/cacerts (No such
> > file
> > > or directory)
> > > at
> > >
> >
> org.apache.nifi.io.socket.SSLContextFactoryTest.testShouldVerifyKeystoreWithSameKeyPassword(SSLContextFactoryTest.groovy:113)
> > >
> > > Also, during the build, I spotted an ERROR message (that does not
> prevent
> > > the completion of the build). We might want to solve this for the next
> > > release:
> > >  [INFO] --- frontend-maven-plugin:1.4:npm (npm install) @
> > > nifi-jolt-transform-json-ui ---
> > >  [INFO] Running 'npm --cache-min Infinity install' in
> > >
> >
> /Users/pierrevillard/tmp/nifi-1.11.0/nifi-nar-bundles/nifi-standard-bundle/nifi-jolt-transform-json-ui/target/frontend-working-directory
> > >  [WARNING] npm WARN deprecated angular-ui-router@0.2.18: This npm
> > package
> > > 'angular-ui-router' has been renamed to '@uirouter/angularjs'. Please
> > > update your package.json. See
> > > https://ui-router.github.io/blog/uirouter-scoped-packages/
> > >  [ERROR] npm notice created a lockfile as package-lock.json. You should
> > > commit this file.
> > >  [WARNING] npm WARN nifi-jolt-transform-json-ui@ No license field.
> > >  [ERROR]
> > >
> > > Thanks for taking care of the release Joe!
> > >
> > > Le lun. 20 janv. 2020 à 03:21, Joe Witt  a écrit :
> > >
> > >> Hello,
> > >>
> > >> I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > >> nifi-1.11.0.
> > >>
> > >> The source zip, including signatures, digests, etc. can be found at:
> > >> https://repository.apache.org/content/repositories/orgapachenifi-1155
> > >>
> > >> The source being voted upon and the convenience binaries can be found
> > at:
> > >> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.0/
> > >>
> > >> A helpful reminder on how the release candidate verification process
> > works:
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > >>
> > >> The Git tag is nifi-1.11.0-RC3
> > >> The Git commit ID is 633408bce7ad34dad727ed9c4edfd36a224f3f12
> > >>
> > >>
> >
> 

NiFi Invoke Http processor with oauth2

[Great Info]

Hi,

I am using NiFi invokeHttp processor to send the data to some other third
party server. The third party server is oauth2 protected, so I need to
login and get the JWT token after getting it, invoke http needs to add it
in header *'Authorization:"JWTtoken"'* before sending to third-party server
and refresh it when it expires.

When I went through NiFi invokehttp processor it does not have any option
for oauth2 flow options.

During search I got few links oauth
, this
is very big flow to get a token which is adding more nifi processor stuffs
, and nifi-jira  link shows there
is some Jira ticket on the same but I could not find same in recent NiFi.
Hence is there a better flow to handle oauth2 when sending the data to
other third party server.

Regards

Indra

Re: NiFi Extension Registry?

[Bryan Bende]

The work for that would be part of NiFi so I don't think it is tied to
any specific registry release.

The REST APIs are already there in NiFi Registry, that is what the CLI
command for 'download-bundle' is calling.

On Tue, Jan 21, 2020 at 10:02 AM Mike Thomsen  wrote:
>
> Is that slated for the 1.0 release?
>
> On Tue, Jan 21, 2020 at 9:33 AM Bryan Bende  wrote:
>
> > Hi Mike,
> >
> > There is no automatic retrieval from registry yet. Currently you would
> > have to use CLI commands, or curl/scripts, to download the desired
> > NARs from registry into the extensions folder on each node.
> >
> > Thanks,
> >
> > Bryan
> >
> > On Tue, Jan 21, 2020 at 7:34 AM Mike Thomsen 
> > wrote:
> > >
> > > Bryan,
> > >
> > > I tried this workflow:
> > >
> > > 1. Add NAR to extensions folder.
> > > 2. Add to canvas.
> > > 3. Stop NiFi and remove NAR and $NIFI/work to clear it out.
> > > 4. Restart NiFi
> > >
> > > The NAR was not pulled from the v0.5 Registry I had running. Is that
> > > expected behavior in 1.10 and 1.11?
> > >
> > > Thanks,
> > >
> > > Mike
> > >
> > > On Mon, Oct 14, 2019 at 4:33 PM Bryan Bende  wrote:
> > >
> > > > Hi Shalin,
> > > >
> > > > There is a minimal version of an extension registry as part of NiFi
> > > > Registry 0.5.0. You can see an example of how to upload a NAR in the
> > > > user guide [1].
> > > >
> > > > The issue is that in order to use those end-points, your NAR needs to
> > > > be built with NiFi 1.10.0 which hasn't been released yet. So we are
> > > > still in a little bit of a waiting period, but you could always build
> > > > NiFi master and set your NAR to use nifi-api 1.10.0-SNAPSHOT if you
> > > > wanted to try it out.
> > > >
> > > > Thanks,
> > > >
> > > > Bryan
> > > >
> > > > [1]
> > > >
> > https://nifi.apache.org/docs/nifi-registry-docs/html/user-guide.html#manage-bundles
> > > >
> > > > On Mon, Oct 14, 2019 at 4:22 PM Shalin Mehta 
> > > > wrote:
> > > > >
> > > > >  Hey all,
> > > > >
> > > > > I'm starting to cut my teeth on the extensibility of NiFi through
> > Custom
> > > > > Processors, and one of the big things on my mind is being able to
> > manage
> > > > a
> > > > > catalog of them across an organization.
> > > > >
> > > > > While watching the "BYOP" presentation given by Andy at DataWorks
> > Summit
> > > > > Barcelona earlier this year (awesome presentation, by the way!),
> > there
> > > > was
> > > > > a really quick note of a future Extension Registry within NiFi
> > Registry.
> > > > I
> > > > > dug around a bit and only came up with this Confluence page outlining
> > > > ideas
> > > > > for such a thing:
> > > > >
> > > > >
> > > >
> > https://cwiki.apache.org/confluence/display/NIFI/Extension+Repositories+%28aka+Extension+Registry%29+for+Dynamically-loaded+Extensions
> > > > >
> > > > > Is there any more information out there around this effort, such as
> > > > updated
> > > > > notes or specific Jira(s) about it? I'd love to get a better sense of
> > > > what
> > > > > the community has in mind, and what the state of the addition is like
> > > > these
> > > > > days. Rolling my own incarnation through process and supporting
> > tools is
> > > > > where my head is currently sitting, but something more "permanent"
> > and in
> > > > > line with the direction of the Project is way more appealing.
> > > > >
> > > > > Thanks much in advance,
> > > > >
> > > > > Shalin
> > > >
> >

Call for presentations for ApacheCon North America 2020 now open

[Rich Bowen]

Dear Apache enthusiast,

(You’re receiving this message because you are subscribed to one or more 
project mailing lists at the Apache Software Foundation.)


The call for presentations for ApacheCon North America 2020 is now open 
at https://apachecon.com/acna2020/cfp


ApacheCon will be held at the Sheraton, New Orleans, September 28th 
through October 2nd, 2020.


As in past years, ApacheCon will feature tracks focusing on the various 
technologies within the Apache ecosystem, and so the call for 
presentations will ask you to select one of those tracks, or “General” 
if the content falls outside of one of our already-organized tracks. 
These tracks are:


Karaf
Internet of Things
Fineract
Community
Content Delivery
Solr/Lucene (Search)
Gobblin/Big Data Integration
Ignite
Observability
Cloudstack
Geospatial
Graph
Camel/Integration
Flagon
Tomcat
Cassandra
Groovy
Web/httpd
General/Other

The CFP will close Friday, May 1, 2020 8:00 AM (America/New_York time).

Submit early, submit often, at https://apachecon.com/acna2020/cfp

Rich, for the ApacheCon Planners

Re: NiFi Extension Registry?

[Mike Thomsen]

Is that slated for the 1.0 release?

On Tue, Jan 21, 2020 at 9:33 AM Bryan Bende  wrote:

> Hi Mike,
>
> There is no automatic retrieval from registry yet. Currently you would
> have to use CLI commands, or curl/scripts, to download the desired
> NARs from registry into the extensions folder on each node.
>
> Thanks,
>
> Bryan
>
> On Tue, Jan 21, 2020 at 7:34 AM Mike Thomsen 
> wrote:
> >
> > Bryan,
> >
> > I tried this workflow:
> >
> > 1. Add NAR to extensions folder.
> > 2. Add to canvas.
> > 3. Stop NiFi and remove NAR and $NIFI/work to clear it out.
> > 4. Restart NiFi
> >
> > The NAR was not pulled from the v0.5 Registry I had running. Is that
> > expected behavior in 1.10 and 1.11?
> >
> > Thanks,
> >
> > Mike
> >
> > On Mon, Oct 14, 2019 at 4:33 PM Bryan Bende  wrote:
> >
> > > Hi Shalin,
> > >
> > > There is a minimal version of an extension registry as part of NiFi
> > > Registry 0.5.0. You can see an example of how to upload a NAR in the
> > > user guide [1].
> > >
> > > The issue is that in order to use those end-points, your NAR needs to
> > > be built with NiFi 1.10.0 which hasn't been released yet. So we are
> > > still in a little bit of a waiting period, but you could always build
> > > NiFi master and set your NAR to use nifi-api 1.10.0-SNAPSHOT if you
> > > wanted to try it out.
> > >
> > > Thanks,
> > >
> > > Bryan
> > >
> > > [1]
> > >
> https://nifi.apache.org/docs/nifi-registry-docs/html/user-guide.html#manage-bundles
> > >
> > > On Mon, Oct 14, 2019 at 4:22 PM Shalin Mehta 
> > > wrote:
> > > >
> > > >  Hey all,
> > > >
> > > > I'm starting to cut my teeth on the extensibility of NiFi through
> Custom
> > > > Processors, and one of the big things on my mind is being able to
> manage
> > > a
> > > > catalog of them across an organization.
> > > >
> > > > While watching the "BYOP" presentation given by Andy at DataWorks
> Summit
> > > > Barcelona earlier this year (awesome presentation, by the way!),
> there
> > > was
> > > > a really quick note of a future Extension Registry within NiFi
> Registry.
> > > I
> > > > dug around a bit and only came up with this Confluence page outlining
> > > ideas
> > > > for such a thing:
> > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/display/NIFI/Extension+Repositories+%28aka+Extension+Registry%29+for+Dynamically-loaded+Extensions
> > > >
> > > > Is there any more information out there around this effort, such as
> > > updated
> > > > notes or specific Jira(s) about it? I'd love to get a better sense of
> > > what
> > > > the community has in mind, and what the state of the addition is like
> > > these
> > > > days. Rolling my own incarnation through process and supporting
> tools is
> > > > where my head is currently sitting, but something more "permanent"
> and in
> > > > line with the direction of the Project is way more appealing.
> > > >
> > > > Thanks much in advance,
> > > >
> > > > Shalin
> > >
>

Regarding NiFi Summary UI

[Ashwinee Tijare]

Hello Team,
So far, it has been really nice experience with the advanced tool “Apache 
NiFi”. We could progressed on a good amount on work. But now, it is time to 
build some monitoring and alerting mechanism from the flow.
Could you please guide me on my question?  I want to use the endpoints exposed 
by the NiFi REST API to create a structured representation of the flow 
contained in a single NiFi instance (process groups, processors, connections, 
ports, etc...). This will make it possible for us to have a machine readable 
view of the flow that can be used for monitoring & alerting system. I thought 
this should be possible by querying the root flow, and then looping through all 
of the process groups. Is this correct?

1.Is it possible that we can query on NiFi Summary UI?

2.What is its end point API?

Regards,
Ashwinee Tijare.




The information contained in this message is intended only for the recipient, 
and may be a confidential attorney-client communication or may otherwise be 
privileged and confidential and protected from disclosure. If the reader of 
this message is not the intended recipient, or an employee or agent responsible 
for delivering this message to the intended recipient, please be aware that any 
dissemination or copying of this communication is strictly prohibited. If you 
have received this communication in error, please immediately notify us by 
replying to the message and deleting it from your computer. S Global Inc. 
reserves the right, subject to applicable local law, to monitor, review and 
process the content of any electronic message or information sent to or from 
S Global Inc. e-mail addresses without informing the sender or recipient of 
the message. By sending electronic message or information to S Global Inc. 
e-mail addresses you, as the sender, are consenting to S Global Inc. 
processing any of your personal data therein.

Re: NiFi Extension Registry?

[Bryan Bende]

Hi Mike,

There is no automatic retrieval from registry yet. Currently you would
have to use CLI commands, or curl/scripts, to download the desired
NARs from registry into the extensions folder on each node.

Thanks,

Bryan

On Tue, Jan 21, 2020 at 7:34 AM Mike Thomsen  wrote:
>
> Bryan,
>
> I tried this workflow:
>
> 1. Add NAR to extensions folder.
> 2. Add to canvas.
> 3. Stop NiFi and remove NAR and $NIFI/work to clear it out.
> 4. Restart NiFi
>
> The NAR was not pulled from the v0.5 Registry I had running. Is that
> expected behavior in 1.10 and 1.11?
>
> Thanks,
>
> Mike
>
> On Mon, Oct 14, 2019 at 4:33 PM Bryan Bende  wrote:
>
> > Hi Shalin,
> >
> > There is a minimal version of an extension registry as part of NiFi
> > Registry 0.5.0. You can see an example of how to upload a NAR in the
> > user guide [1].
> >
> > The issue is that in order to use those end-points, your NAR needs to
> > be built with NiFi 1.10.0 which hasn't been released yet. So we are
> > still in a little bit of a waiting period, but you could always build
> > NiFi master and set your NAR to use nifi-api 1.10.0-SNAPSHOT if you
> > wanted to try it out.
> >
> > Thanks,
> >
> > Bryan
> >
> > [1]
> > https://nifi.apache.org/docs/nifi-registry-docs/html/user-guide.html#manage-bundles
> >
> > On Mon, Oct 14, 2019 at 4:22 PM Shalin Mehta 
> > wrote:
> > >
> > >  Hey all,
> > >
> > > I'm starting to cut my teeth on the extensibility of NiFi through Custom
> > > Processors, and one of the big things on my mind is being able to manage
> > a
> > > catalog of them across an organization.
> > >
> > > While watching the "BYOP" presentation given by Andy at DataWorks Summit
> > > Barcelona earlier this year (awesome presentation, by the way!), there
> > was
> > > a really quick note of a future Extension Registry within NiFi Registry.
> > I
> > > dug around a bit and only came up with this Confluence page outlining
> > ideas
> > > for such a thing:
> > >
> > >
> > https://cwiki.apache.org/confluence/display/NIFI/Extension+Repositories+%28aka+Extension+Registry%29+for+Dynamically-loaded+Extensions
> > >
> > > Is there any more information out there around this effort, such as
> > updated
> > > notes or specific Jira(s) about it? I'd love to get a better sense of
> > what
> > > the community has in mind, and what the state of the addition is like
> > these
> > > days. Rolling my own incarnation through process and supporting tools is
> > > where my head is currently sitting, but something more "permanent" and in
> > > line with the direction of the Project is way more appealing.
> > >
> > > Thanks much in advance,
> > >
> > > Shalin
> >

Re: [VOTE] Release Apache NiFi 1.11.0 (rc3)

[Arpad Boda]

+1

   - Verified signature, checksums.
   - Built properly.
   - Started NiFi, sent flowfiles from MiNiFi, designed flow to handle
   them.


Created https://issues.apache.org/jira/browse/NIFI-7049 in the meanwhile as:

   - SFTP tests can fail on "clean" hosts
   - The underlying behavior seems to be unintentional and error-prone


I don't consider it as a blocker as it has been working this way for quite
a while.


On Tue, Jan 21, 2020 at 1:33 AM Andy LoPresto  wrote:

> +1, binding.
>
> Verified normal signatures and checksums, deployed instance, and verified
> selected Jiras were included in the build.
>
> Pierre, I opened NIFI-7048 to resolve the issue you documented below.
> Thanks.
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> > On Jan 20, 2020, at 11:33 AM, Pierre Villard <
> pierre.villard...@gmail.com> wrote:
> >
> > +1 (binding) release this package as nifi-1.11.0
> >
> > Went through the usual check process. Also deployed a 3-nodes secured
> > cluster with OIDC behind a load balancer with Terraform on Google Cloud.
> > Tested various flows. It looks good to me.
> >
> > Some notes - I did run into a test failure (that I didn't have before)
> but
> > it was because JAVA_HOME was not set properly. I copy the error in case
> it
> > happens to someone else. This is on recently added tests:
> >
> > [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed:
> > 0.666 s <<< FAILURE! - in org.apache.nifi.io.socket.SSLContextFactoryTest
> > [ERROR]
> >
> testShouldVerifyKeystoreWithEmptyKeyPassword(org.apache.nifi.io.socket.SSLContextFactoryTest)
> > Time elapsed: 0.051 s  <<< ERROR!
> > java.io.FileNotFoundException: null/jre/lib/security/cacerts (No such
> file
> > or directory)
> > at
> >
> org.apache.nifi.io.socket.SSLContextFactoryTest.testShouldVerifyKeystoreWithEmptyKeyPassword(SSLContextFactoryTest.groovy:162)
> > [ERROR]
> >
> testShouldVerifyKeystoreWithDifferentKeyPassword(org.apache.nifi.io.socket.SSLContextFactoryTest)
> > Time elapsed: 0.002 s  <<< ERROR!
> > java.io.FileNotFoundException: null/jre/lib/security/cacerts (No such
> file
> > or directory)
> > at
> >
> org.apache.nifi.io.socket.SSLContextFactoryTest.testShouldVerifyKeystoreWithDifferentKeyPassword(SSLContextFactoryTest.groovy:138)
> > [ERROR]
> >
> testShouldVerifyKeystoreWithSameKeyPassword(org.apache.nifi.io.socket.SSLContextFactoryTest)
> > Time elapsed: 0.001 s  <<< ERROR!
> > java.io.FileNotFoundException: null/jre/lib/security/cacerts (No such
> file
> > or directory)
> > at
> >
> org.apache.nifi.io.socket.SSLContextFactoryTest.testShouldVerifyKeystoreWithSameKeyPassword(SSLContextFactoryTest.groovy:113)
> >
> > Also, during the build, I spotted an ERROR message (that does not prevent
> > the completion of the build). We might want to solve this for the next
> > release:
> >  [INFO] --- frontend-maven-plugin:1.4:npm (npm install) @
> > nifi-jolt-transform-json-ui ---
> >  [INFO] Running 'npm --cache-min Infinity install' in
> >
> /Users/pierrevillard/tmp/nifi-1.11.0/nifi-nar-bundles/nifi-standard-bundle/nifi-jolt-transform-json-ui/target/frontend-working-directory
> >  [WARNING] npm WARN deprecated angular-ui-router@0.2.18: This npm
> package
> > 'angular-ui-router' has been renamed to '@uirouter/angularjs'. Please
> > update your package.json. See
> > https://ui-router.github.io/blog/uirouter-scoped-packages/
> >  [ERROR] npm notice created a lockfile as package-lock.json. You should
> > commit this file.
> >  [WARNING] npm WARN nifi-jolt-transform-json-ui@ No license field.
> >  [ERROR]
> >
> > Thanks for taking care of the release Joe!
> >
> > Le lun. 20 janv. 2020 à 03:21, Joe Witt  a écrit :
> >
> >> Hello,
> >>
> >> I am pleased to be calling this vote for the source release of Apache
> NiFi
> >> nifi-1.11.0.
> >>
> >> The source zip, including signatures, digests, etc. can be found at:
> >> https://repository.apache.org/content/repositories/orgapachenifi-1155
> >>
> >> The source being voted upon and the convenience binaries can be found
> at:
> >> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.0/
> >>
> >> A helpful reminder on how the release candidate verification process
> works:
> >>
> >>
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >>
> >> The Git tag is nifi-1.11.0-RC3
> >> The Git commit ID is 633408bce7ad34dad727ed9c4edfd36a224f3f12
> >>
> >>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=633408bce7ad34dad727ed9c4edfd36a224f3f12
> >>
> >> Checksums of nifi-1.11.0-source-release.zip:
> >> SHA256: 0e2d77265fc7cedfbdb9588df1dd7f456fd18b6288d65eb5e21befe23af7c567
> >> SHA512:
> >>
> >>
> 4880fa3482b3e8d8eed439848fe0a6596826d7ad46425a91b0dd4a4bcd178259327380b24045b7991dbdf8449abdfdda145786b6863eb603f6cef3b9e0ae8ec1
> >>
> >> Release artifacts are signed with the following key:
> >> 

Re: Question regarding site-to-site on NiFi 0.7.2

[Mike Thomsen]

> I cannot use a more recent version now due to the machine limitations
(Java version)

Can you share why you have that limitation?

On Tue, Jan 21, 2020 at 7:48 AM Fábio Coelho  wrote:

> Hello,
>
>
>
> First of all thank you for the amazing framework.
>
>
>
> I’m building a prototype with NiFi 0.7.2, I cannot use a more recent
> version now due to the machine limitations (Java version), and I’m trying
> to implement a site-to-site (not secure) connection to send a flow file
> (from one NiFi instance to another NiFi instance).
>
>
>
> I think I have almost everything correctly, but when I try to send a file
> from the client to the server I’m getting: java.net.ConnectException:
> Connection refused.
>
>
>
> All the documentation that I’m finding for site-to-site configurations are
> related with the latest versions of NiFi, where the toolkit is also
> present.
>
> Is there any place where I can find the configurations to setup correctly
> a s2s on NiFi 0.7.2 ?
>
>
>
> Thanks in advance
>
>
>
> *Kind regards,*
>
> *Fábio Coelho*
> *[image:
> https://webmail.alten.nl/webmail/api/download/attachment/7bb5a8ae-2841-4696-b16c-04b7570a15ed/68/0-6/image001.png?version=702=f9dba15a4a5efae4d7172ff0ef32d5f782ad16accf97ff43bedccd939bb24e34]*
>
> *Technical Consultant*
> ALTEN Technology
>
> Technical Software
>
> T +351 966930118
> Hurksestraat 45 – 5652 AH Eindhoven
>
> [image: cid:image002.jpg@01CBC93F.72379900]
>
>
>
>
>
> www.alten.nl  [image: image015]
>  [image: image013]
>  [image: image011]
>  [image: image009]
> 
>
>
>
>
>

Question regarding site-to-site on NiFi 0.7.2

[Fábio Coelho]

Hello,

First of all thank you for the amazing framework.

I'm building a prototype with NiFi 0.7.2, I cannot use a more recent version 
now due to the machine limitations (Java version), and I'm trying to implement 
a site-to-site (not secure) connection to send a flow file (from one NiFi 
instance to another NiFi instance).

I think I have almost everything correctly, but when I try to send a file from 
the client to the server I'm getting: java.net.ConnectException: Connection 
refused.

All the documentation that I'm finding for site-to-site configurations are 
related with the latest versions of NiFi, where the toolkit is also present.
Is there any place where I can find the configurations to setup correctly a s2s 
on NiFi 0.7.2 ?

Thanks in advance

Kind regards,
Fábio Coelho
[https://webmail.alten.nl/webmail/api/download/attachment/7bb5a8ae-2841-4696-b16c-04b7570a15ed/68/0-6/image001.png?version=702=f9dba15a4a5efae4d7172ff0ef32d5f782ad16accf97ff43bedccd939bb24e34]
Technical Consultant
ALTEN Technology
Technical Software
T +351 966930118
Hurksestraat 45 - 5652 AH Eindhoven
[cid:image002.jpg@01CBC93F.72379900]


www.alten.nl  [image015] 
  [image013] 
  [image011] 
  [image009] 

Re: NiFi Extension Registry?

[Mike Thomsen]

Bryan,

I tried this workflow:

1. Add NAR to extensions folder.
2. Add to canvas.
3. Stop NiFi and remove NAR and $NIFI/work to clear it out.
4. Restart NiFi

The NAR was not pulled from the v0.5 Registry I had running. Is that
expected behavior in 1.10 and 1.11?

Thanks,

Mike

On Mon, Oct 14, 2019 at 4:33 PM Bryan Bende  wrote:

> Hi Shalin,
>
> There is a minimal version of an extension registry as part of NiFi
> Registry 0.5.0. You can see an example of how to upload a NAR in the
> user guide [1].
>
> The issue is that in order to use those end-points, your NAR needs to
> be built with NiFi 1.10.0 which hasn't been released yet. So we are
> still in a little bit of a waiting period, but you could always build
> NiFi master and set your NAR to use nifi-api 1.10.0-SNAPSHOT if you
> wanted to try it out.
>
> Thanks,
>
> Bryan
>
> [1]
> https://nifi.apache.org/docs/nifi-registry-docs/html/user-guide.html#manage-bundles
>
> On Mon, Oct 14, 2019 at 4:22 PM Shalin Mehta 
> wrote:
> >
> >  Hey all,
> >
> > I'm starting to cut my teeth on the extensibility of NiFi through Custom
> > Processors, and one of the big things on my mind is being able to manage
> a
> > catalog of them across an organization.
> >
> > While watching the "BYOP" presentation given by Andy at DataWorks Summit
> > Barcelona earlier this year (awesome presentation, by the way!), there
> was
> > a really quick note of a future Extension Registry within NiFi Registry.
> I
> > dug around a bit and only came up with this Confluence page outlining
> ideas
> > for such a thing:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Extension+Repositories+%28aka+Extension+Registry%29+for+Dynamically-loaded+Extensions
> >
> > Is there any more information out there around this effort, such as
> updated
> > notes or specific Jira(s) about it? I'd love to get a better sense of
> what
> > the community has in mind, and what the state of the addition is like
> these
> > days. Rolling my own incarnation through process and supporting tools is
> > where my head is currently sitting, but something more "permanent" and in
> > line with the direction of the Project is way more appealing.
> >
> > Thanks much in advance,
> >
> > Shalin
>