Re: [Discuss] NiFi 2.0 milestones, where we are?

[Steven Matison]

This is awesome to hear.  I recently moved all my personal stuff into 2.0
space and everything working smoothly as expected.  Now I can play with new
and forget old.


Amazing work from everyone who has helped the 2.x project get so far so
fast!!




On Fri, Aug 9, 2024 at 11:21 AM Douglas Reid 
wrote:

> Thanks Joe.What’s a rough estimate to wrap up the final bits of work?
>
>
> > On Aug 9, 2024, at 10:58 AM, Joe Witt  wrote:
> >
> > It is incredibly tempting to keep removing crusty bits like the XML and
> S2S
> > as we are genuinely so much better off now having made so much tech debt
> > progress.  Huge thanks to you in particular, David!  But I do agree with
> > your view.
> >
> > I think right on the heels of the last vestige of old UI/content viewing
> we
> > push for the official 2.0 release.
> >
> > I'd actually think we consider a 3.0 to be one year later which dumps
> > complex config models and S2S (at least the client impl) and continues
> > cleanup but otherwise incurs no user/migration impact.  But that is a
> > fairly off the cuff mention.
> >
> > Thanks
> >
> > On Fri, Aug 9, 2024 at 7:21 AM David Handermann <
> exceptionfact...@apache.org>
> > wrote:
> >
> >> Arpad,
> >>
> >> Thanks for initiating the discussion! I think we are getting very
> >> close to ready for a GA release of NiFi 2.0.
> >>
> >> The last major element I am aware of right now is some reworking of
> >> content viewer integration. Jira issue NIFI-13632 [1] highlights some
> >> general issues to be addressed, bringing the content viewer
> >> integration in line with the rest of the redesigned web user
> >> interface. I will defer to Matt Gilman and others for details.  I'm
> >> not aware of anything else in particular, but this particular area is
> >> important as it relates to the contract between the main application
> >> and content viewers.
> >>
> >> Beyond that, there are other framework issues I would like to address
> >> in the future, such as the configuration structure that requires
> >> multiple XML files, and the Site-to-Site client library. However, in
> >> the interest of keeping changes scoped, I believe those can be
> >> addressed down the road.
> >>
> >> With that background, as soon as we are in a good position with the
> >> content viewer integration, we should proceed to preparing for a
> >> release.
> >>
> >> Regards,
> >> David Handermann
> >>
> >> [1] https://issues.apache.org/jira/browse/NIFI-13632
> >>
> >> On Thu, Aug 8, 2024 at 5:57 PM Arpad Boda  wrote:
> >>>
> >>> Team,
> >>>
> >>> Tremendous amount of effort has been put into NiFi 2.0 so far and I
> >> haven't
> >>> seen breaking changes introduced during the last few weeks, so I wonder
> >>> where you think we are in the process of making it final(GA)?
> >>> Do you see features missing, things that need to be either updated or
> >>> deprecated, breaking api changes introduced?
> >>>
> >>> Don't get me wrong, I have no intent to push the community to release
> 2.0
> >>> as soon as we can, the goal of this thread is to have a common
> >>> understanding of where we are in the process and what we need to
> achieve
> >> to
> >>> get there.
> >>>
> >>> Thanks in advance for sharing your thoughts, opinions!
> >>>
> >>> Cheers,
> >>> Arpad
> >>
>
>

Re: [discuss] What to do with the Cassandra components

[Steven Matison]

That was kinda where i got stuck and fell out on my branch/jira.  Mike and
I wanted to make a new controller service , without backward compatibility;
and remove the duplicate driver/connection properties found in some of the
processors.

I agree taking out all old stuff and making new controller service makes
most sense.  4.x and 5.x should be mostly backwards compatible to 2&3.x
with how it’s used within current processors.



On Tue, Mar 19, 2024 at 10:49 AM Matt Burgess  wrote:

> The abstraction is to isolate Java API changes, not protocol compatibility
> Changing to the java-driver comes with a number of changes to the code (see
> Steven's and my branches), if we can abstract that API it should lead to
> more maintainable code in the future by not having to change any
> processors, just the controller service implementation.
>
>
> On Tue, Mar 19, 2024 at 10:14 AM Mike Thomsen 
> wrote:
>
> >
> >
> https://opensource.docs.scylladb.com/stable/using-scylla/drivers/cql-drivers/scylla-java-driver.html
> >
> > Directly quoting Scylla docs here:
> >
> > > The Scylla Java Driver is a drop-in replacement for the DataStax Java
> > Driver. As such, no code changes are needed to use this driver.
> >
> > On Tue, Mar 19, 2024 at 10:13 AM Mike Thomsen 
> > wrote:
> >
> > > Matt,
> > >
> > > I don't think we need to really "abstract above" the drivers because
> the
> > > Java DataStax driver appears to support 4.X all the way back to 2.X, as
> > > well as the enterprise versions from DataStax
> > >
> > > https://docs.datastax.com/en/driver-matrix/docs/java-drivers.html
> > >
> > > Similar situation with Scylla. When I looked at the driver, it appeared
> > to
> > > copy verbatim the entire public API of that driver. So I think before
> we
> > > dive into abstractions, it's worth doing a bit more validation of these
> > > details. IMHO, this might be a much lighter lift than anticipated.
> > >
> > >
> > > On Mon, Mar 18, 2024 at 4:30 PM Matt Burgess 
> > wrote:
> > >
> > >> Totally agree, that's what my branch does (see link in previous
> email).
> > >> The
> > >> more I work with it, the more I think I can abstract it further from
> > their
> > >> JDBC-like API but I started with a bunch of delegate classes then I
> > figure
> > >> I'll see where I can consolidate to more abstract concepts. If I don't
> > >> have
> > >> to support Cassandra 3 with the new API, so much the better.
> > >>
> > >> Regards,
> > >> Matt
> > >>
> > >> On Mon, Mar 18, 2024 at 4:14 PM David Handermann <
> > >> exceptionfact...@apache.org> wrote:
> > >>
> > >> > Matt et al,
> > >> >
> > >> > It is good to see the background effort on moving Cassandra
> > >> > capabilities in a supportable direction.
> > >> >
> > >> > I think new Cassandra components will require a significant
> departure
> > >> > from current Controller Service abstractions. Right now, the
> existing
> > >> > service interface does not provide a clean abstraction from the
> > >> > Cassandra library, which is part of the reason for the current
> > >> > coupling to the legacy driver version.
> > >> >
> > >> > Following up from Joe's comments, it seems like the cleanest way
> > >> > forward is to deprecate the current bundle on the 1.x branch, and
> > >> > remove the current bundle from the main branch. That will provide a
> > >> > clean slate for new Service and Processor implementations, without
> > >> > concern for uncertain compatibility questions.
> > >> >
> > >> > Regards,
> > >> > David Handermann
> > >> >
> > >> > On Mon, Mar 18, 2024 at 2:35 PM Matt Burgess 
> > >> wrote:
> > >> > >
> > >> > > What do y'all think about removing the individual connection
> > >> properties
> > >> > > from the Cassandra processors for NiFi 2.0 and requiring a
> > >> > > CassandraSessionProvider instead? I think we started doing that
> > >> elsewhere
> > >> > > (Elasticsearch maybe?), I noticed duplicate code in the
> > >> > > CassandraSessionProvider and AbstractCassandraProcessor, if we
> keep
> > >> those
> > &

Re: [discuss] What to do with the Cassandra components

[Steven Matison]

I got through quite a bit of work to enable 4.x…

The 3.x pieces that were not backwards compatible is very edge use case and
could have been done slightly differently but with work around.

https://github.com/steven-matison/nifi/tree/nifi-10120-1






On Fri, Mar 15, 2024 at 2:30 PM Matt Burgess  wrote:

> Oops used the wrong email address so if there have been responses to the
> Cassandra thread since mine I missed them, my bad!
>
> On Fri, Mar 15, 2024 at 2:00 PM Matt Burgess  wrote:
>
> > I believe the CQL protocol is backwards compatible but the Java API is
> > not. For example "com.datastax.driver.core.Session" is now
> > "com.datastax.oss.driver.api.core.session.Session" and there is no more
> > "Cluster" class. Might be fairly trivial to fix though, if that's the
> path
> > of least resistance.
> >
> > On Fri, Mar 15, 2024 at 1:40 PM Joe Witt  wrote:
> >
> >> Matt
> >>
> >> I dont know a ton about Cassandra but when I looked at client/driver
> notes
> >> for 4+ it said it was compatible all the way back to 3.x.   Not sure
> what
> >> that means but it surely seems worth exploring.  Also I dont know if the
> >> 4.x drivers get rid of the vulnerable bits.
> >>
> >> Thanks
> >>
> >> On Fri, Mar 15, 2024 at 10:39 AM Matt Burgess 
> >> wrote:
> >>
> >> > At the very least we should upgrade to Cassandra 3.11.6:
> >> >
> https://github.com/apache/cassandra/blob/cassandra-3.11.16/CHANGES.txt
> >> >
> >> > On Fri, Mar 15, 2024 at 1:31 PM Matt Burgess 
> >> wrote:
> >> >
> >> > > If the community agrees to get rid of Cassandra 3 that'll save me
> >> effort
> >> > > on the refactor after I add Cassandra 4 :) Otherwise those
> >> > > vulnerabilities would only be in a "new" Cassandra 3 services NAR
> that
> >> > > would not be included in the convenience binary.
> >> > >
> >> > > On Fri, Mar 15, 2024 at 1:28 PM Joe Witt 
> wrote:
> >> > >
> >> > >> Mike, Matt,
> >> > >>
> >> > >> Happy to hear you both have active efforts or are interested in
> doing
> >> > so.
> >> > >> Can you help me understand more specifically what that means for
> the
> >> > >> current set of components?
> >> > >>
> >> > >> The CVE hits are concerning and long standing.  Supporting
> Cassandra
> >> 3
> >> > >> implies the current set of dependencies would remain too right?
> >> > >>
> >> > >> Is the current set of components we have ones we want to retain?
> We
> >> > >> certainly need Cassandra components - but are the ones we have now
> >> the
> >> > >> right ones?
> >> > >>
> >> > >> Thanks
> >> > >> Joe
> >> > >>
> >> > >> On Fri, Mar 15, 2024 at 10:25 AM Matt Burgess <
> mattyb...@apache.org>
> >> > >> wrote:
> >> > >>
> >> > >> > I'm actively working this, I pushed my branch up in case anyone
> >> wants
> >> > to
> >> > >> > take a look [1]. The idea is to abstract the Cassandra API "up a
> >> > couple
> >> > >> > levels" and provide implementations for Cassandra 3, 4, and
> >> eventually
> >> > >> 5.
> >> > >> > For JDBC-like interfaces this is a PITA because of the API
> >> (Statement,
> >> > >> > PreparedStatement, BoundStatement, ResultSet, etc.) but I'm
> hoping
> >> we
> >> > >> can
> >> > >> > find a common pattern for abstracting the third-party library
> >> > >> > implementation and API from the NiFi component (Processor,
> >> > >> > ControllerService, etc.) API. I think we're doing something
> similar
> >> > for
> >> > >> > Kafka?
> >> > >> >
> >> > >> > Regards,
> >> > >> > Matt
> >> > >> >
> >> > >> > [1] https://github.com/mattyb149/nifi/tree/cassy4
> >> > >> >
> >> > >> >
> >> > >> > On Fri, Mar 15, 2024 at 8:43 AM Mike Thomsen <
> >> mikerthom...@gmail.com>
> >> > >> > wrote:
> >> >

Re: [VOTE] Release Apache NiFi 1.23.1 (RC1)

[Steven Matison]

+1 non binding

Verified source release checksums
Built w/ java version 17 *Apache Maven 3.9.2*
Checks completed

NiFi 1.23.1 started and imported test flow

Thanks David and Team for another release!!

On Tue, Aug 15, 2023 at 2:07 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.23.1.
>
> Please review the following guide for how to verify a release candidate
> build:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>
> The source being voted upon and the convenience binaries are available on
> the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.23.1/
>
> The build artifacts are available on the Apache Nexus Repository:
>
> https://repository.apache.org/content/repositories/orgapachenifi-1234
>
> Git Tag: nifi-1.23.1-RC1
> Git Commit ID: f739e9dd2d476b3c0df5a806ff1dffd24be52916
> GitHub Commit Link:
>
> https://github.com/apache/nifi/commit/f739e9dd2d476b3c0df5a806ff1dffd24be52916
>
> Checksums of nifi-1.23.1-source-release.zip:
>
> SHA256: 01f5f67a9f9703232f6fe260f6c1da73f3e3a0764b8e8464f915cfad168278e6
> SHA512:
>
> f8a010ad5a5dd1f71fe04e5d2bf1c6637d2d0a8a7c580a0ff4dbd76c12c2e5ab4ac43e1f5314f9fca85cebe1606bd5e7ae0a8b62f577ddc68696ebd0155d
>
> Release artifacts are signed with the following key:
>
> https://people.apache.org/keys/committer/exceptionfactory.asc
>
> KEYS file available here:
>
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 51 issues were closed/resolved for this release:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353541
>
> Release note highlights can be found here:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.23.1
>
> 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.23.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: [VOTE] Release Apache NiFi 1.23.0 (RC3)

[Steven Matison]

+1 non binding

Verified source release checksums
Built w/ java version 17 *Apache Maven 3.9.2*
Checks completed

NiFi 1.23 started and imported test flow

Thanks David and Team for another release!!

On Tue, Jul 25, 2023 at 5:32 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.23.0.
>
> Please review the following guide for how to verify a release candidate
> build:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>
> The source being voted upon and the convenience binaries are available on
> the Apache Distribution Repository:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.23.0/
>
> The build artifacts are available on the Apache Nexus Repository:
>
> https://repository.apache.org/content/repositories/orgapachenifi-1233
>
> Git Tag: nifi-1.23.0-RC3
> Git Commit ID: 27a690a30a6ae77c217a47ac0601e85970777ca2
> GitHub Commit Link:
>
> https://github.com/apache/nifi/commit/27a690a30a6ae77c217a47ac0601e85970777ca2
>
> Checksums of nifi-1.23.0-source-release.zip:
>
> SHA256: 39c97d89804b005cc995c56a87a3df6f68c44ee42114dffe756bbac90a3593cf
> SHA512:
>
> f256ca731a67435e9883626931abc58f28cda9deb6a7d0a84ed97b78104e43b3b638ee2297d79f92bf5a1e19f62cc78e0a886fa0094593ab34b21d658c59eadd
>
> Release artifacts are signed with the following key:
>
> https://people.apache.org/keys/committer/exceptionfactory.asc
>
> KEYS file available here:
>
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 132 issues were closed/resolved for this release:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353320
>
> Release note highlights can be found here:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.23.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.23.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: [VOTE] Release Apache NiFi 1.23.0 (RC2)

[Steven Matison]

+1 non binding

Verified source release checksums
Built w/ java version 17 *Apache Maven 3.9.2*
Checks completed

NiFi 1.23 started and imported test flow

Thanks David and Team for another release!!

On Fri, Jul 21, 2023 at 11:03 AM Krisztina Zsihovszki 
wrote:

> +1 (non-binding)
>
> - Verified signatures and hashes
> - Ran build using Maven 3.9.3
> - Ran build on macOS 12.6.3 with AdoptOpenJDK build 17.0.7+7-LTS, unit
> tests passed
> - Ran build on macOS 12.6.3 with AdoptOpenJDK build 11.0.2+9, unit tests
> passed
>
> Verified the following tickets:
>
> [NIFI-11670] - Encrypted Content Repository is very slow when FlowFiles
> have a non-zero Content Claim Offset
> [NIFI-11655] - GenerateRecord doesn't generate floats and doubles correctly
> when a schema is supplied
>
>
> On Fri, Jul 21, 2023 at 3:44 AM Matt Burgess  wrote:
>
> > +1 (binding), verified hashes, keys, and commit IDs, ran flows to
> > verify NIFI-11783 [1], NIFI-11807 [2], and verified no regression in
> > NIFI-11621 [3].
> >
> > Apache Maven 3.9.1 (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> > Maven home: /Users/mburgess/.sdkman/candidates/maven/current
> > Java version: 17.0.7, vendor: Oracle Corporation, runtime:
> > /Users/mburgess/.sdkman/candidates/java/17.0.7-oracle
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac"
> >
> > Thanks for RM'ing David!
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-11783
> > [2] https://issues.apache.org/jira/browse/NIFI-11807
> > [3] https://issues.apache.org/jira/browse/NIFI-11621
> >
> > On Thu, Jul 20, 2023 at 8:16 PM David Handermann
> >  wrote:
> > >
> > > Team,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.23.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1231
> > >
> > > The source being voted upon and the convenience binaries can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.23.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.23.0-RC2
> > > The Git commit ID is 2c707ad4e35fa7086024b966f279c8d4da486144
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=2c707ad4e35fa7086024b966f279c8d4da486144
> > >
> >
> https://github.com/apache/nifi/commit/2c707ad4e35fa7086024b966f279c8d4da486144
> > >
> > > Checksums of nifi-1.23.0-source-release.zip:
> > > SHA256:
> 79d8a2cc6f3c2e2b6a31398d2347a0fa5e2849cd47058f6ee7798b231c114b94
> > > SHA512:
> > >
> >
> d80ecab0eb5721ceca1f8840902841fd33ff173ca2c6aff8beefeac6dddc3fe865f2dca9d1e985b339ad75a19ebafffc95d637840957258ae80961bf8db5b0ac
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/exceptionfactory.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 115 issues were closed/resolved for this release:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353320
> > >
> > > Release note highlights can be found here:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.23.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.23.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> >
>

Re: [ANNOUNCE] New nifi PMC Member Nandor Soma Abonyi

[Steven Matison]

Congrats , such an accomplishment !!



On Wed, Jun 28, 2023 at 7:17 AM Andrew Lim 
wrote:

> Congrats!
>
> > On Jun 26, 2023, at 7:10 PM, Joe Witt  wrote:
> >
> > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Nandor
> > has accepted the PMC's invitation to join the Apache NiFi PMC. We greatly
> > appreciate the PR reviews and code contributions and release management
> > work of Nandor.
> >
> > Please join us in congratulating and welcoming Nandor to the Apache NiFi
> > PMC.
> >
> > Congratulations Nandor!
>
>

Re: [VOTE] Release Apache NiFi 1.22.0 (RC1)

[Steven Matison]

+1 non binding

Verified source release checksums
Built w/ java version 17 *Apache Maven 3.9.2*
Checks completed

NiFi 1.22 started and imported test flow to verify NIFI-11608 as expected

Thanks Joe!!

On Wed, Jun 7, 2023 at 9:07 AM Mathew Kiprop 
wrote:

> Hello,
>
> +1 non-binding
>
> Run through the verification process. Everything checks out well.
> Built NiFi with java version 1.8.0_362-8u372-ga~us1-0ubuntu1~22.04-b09
> and apache-maven-3.9.2.
> Started NiFi and created basic flows.
> Verified
> - DBCP Verification Error - Fails to configure data source[1]
> - Bulletin causes UI to think it cannot refresh [2]
> - Expose JMX metrics from NiFi JVM [3]
>
> Tested new ModifyCompression Processor[4]. (My concern on this is that when
> you specify an incompatible input compression strategy, the processing
> fails with no useful message for the user to do the needful). It does not
> seem to be a blocker to me for the release.
>
> Thanks Joe for RM'ing.
>
>
> [1] https://issues.apache.org/jira/browse/NIFI-11547
> [2] https://issues.apache.org/jira/browse/NIFI-11560
> [3] https://issues.apache.org/jira/browse/NIFI-11385
> [4] https://issues.apache.org/jira/browse/NIFI-11466
>
> On Wed, Jun 7, 2023 at 12:38 AM Joe Witt  wrote:
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.22.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1228
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.22.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.22.0-RC1
> > The Git commit ID is 71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8
> >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8
> >
> >
> https://github.com/apache/nifi/commit/71e3ea9f2c58d0cf2ce6824c388f2bd3e917dfc8
> >
> > Checksums of nifi-1.22.0-source-release.zip:
> > SHA256: d63a5f1db95160434670f112a0ee6e06fa141182bd0f12f0e58e3229991f3743
> > SHA512:
> >
> >
> 5f6da64e75a2d5446f1f274fe3de7e97290f5b916eabbc0491a99c6db33f74fbdea001b403044e75bc5c2183fb0500dfc143d0f4cba19d3511f866fff774d7f5
> >
> > 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
> >
> > 186 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353069
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.22.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.22.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>

Re: [discuss] NiFi support for Hadoop ecosystem components

[Steven Matison]

I waited to respond becuase I wanted to see the conversation before jumping
in.

As a user, fan, and consultant I am super excited to even know context
around nifi 2.0 and entire modernization effort that is already on going to
end of 1.x. I am also thankful to be working on some of it myself too.
This is an amazing time for nifi.

In respect of anyone using "old nifi" this topic is super concerning, but
to me this is not more concerning than why you are still using older
versions and/or why are you needing deep backward compatibility with new
versions that are several years from where you are.  Are you not also
modernizing?

Those things aside, my choice is #1.  I speak for those using current
version all way back to some of oldest versions you could imagine are still
online.These people will continue to operate nifi the way they need it
in those versions.  If and when they decide to take a new version, they
will, and they will also deal with the inherit challenges to modernize.
Many of them work completely outside of community and will do that
themselves or rely on a vendor who can support that path for them.





On Wed, Mar 29, 2023 at 11:03 AM Chakravarty, G  wrote:

> One of our primary reasons for using Nifi is that it plays nicely with
> connecting with on-prem HDFS/Hive/Kudu data stores. Also, it appears that
> although the on-prem hadoop/hive tech stack is somewhat less popular now,
> the same hdfs/hive technology is appearing in the cloud under different
> names: Google Dataproc, AWS EMR, Azure HDinsight, Iceberg etc. Some type of
> generic components where the Hadoop processors connectivity to Nifi is
> maintained while individual vendors maintain their own connectivity to
> their products will be a good option if possible.
>
> GC
>
> 
> From: Isha Lamboo 
> Sent: Monday, March 27, 2023 9:04 AM
> To: dev@nifi.apache.org 
> Subject: RE: [discuss] NiFi support for Hadoop ecosystem components
>
> From the perspective of a NiFi administrator:
>
> Removing the xxxHDFS processors anytime soon (2.0) would be a huge issue
> for us. It shouldn't be, the last Hadoop cluster in our environments was
> shut down earlier this year. Hive was already gone more than a year ago.
> But we still have 1000+ HDFS processors in use to manage the Azure
> Datalake. Azure-specific processors have been available for a while, but
> there was no business case to migrating solutions that were working fine.
>
> Getting the required development time/budget to migrate all those flows to
> the Azure processors doesn't look very realistic. This would have to be a
> gradual "replace when you need to change and test the flow anyway" affair.
> Until that finishes, we'd be stuck on the 1.x branch since we're not using
> vendor support.
>
> Option #2 would be vastly preferable to #1 for this simple and dumb reason.
>
> Disregarding our technical debt issues, I agree that it makes sense for
> NiFi instances with a lot of Hadoop integration to depend on vendors for
> their specific flavor of Hadoop, while core NiFi moves forward without all
> of that complexity.
>
> Regards,
>
> Isha
>
> -Oorspronkelijk bericht-
> Van: Nandor Soma Abonyi 
> Verzonden: maandag 27 maart 2023 12:31
> Aan: dev@nifi.apache.org
> Onderwerp: Re: [discuss] NiFi support for Hadoop ecosystem components
>
> Thank you for raising this topic, Joe!
>
> While I understand the desire to remove Hadoop components, I have mixed
> feelings about removing one of the core parts of the Big Data world from
> the project. I'm unsure for how many users we could make a hard time
> removing those components. It seems to be a too significant shift in our
> philosophy.
> We can already see in the above example that somebody would not use NiFi
> if we'd removed them.
>
> Furthermore, although Hadoop has been buried multiple times, new
> technologies seem to still depend on it. For example, Iceberg, in which
> case I'm worried about the consequences of removing the support for an
> increasingly popular technology.
>
> So I wonder whether it is possible to find a forward-looking solution that
> could serve all projects. I've always found configuring Hadoop and friends
> too tricky and I thought it was primarily for historical reasons. The
> issues you describe could easily result from such a thing. I assume that
> over time, new and new things have been added on top of the existing
> implementation without significant refactoring.
>
> My - probably utopistic - idea would be to contact the Hadoop and Hive
> teams and share the issues we are dealing with. Probably we are not alone
> in these problems, but I don't know whether they are aware of them. Even if
> they are, I think approaching them is worth the chance. Who knows where we
> will end up if somebody representing the NiFi project does that?
>
> Regards,
> Nandor Soma Abonyi
>
>
> > On Mar 24, 2023, at 10:40 PM, Jeremy Dyer  wrote:
> >
> > I think option 2 is the best way to handle this

Re: [VOTE] Adopt NiFi 2.0 Proposed Release Goals

[Steven Matison]

+1 (non-binding)

On Tue, Dec 13, 2022 at 7:45 AM Tony Kurc  wrote:

> +1 (binding)
>
> On Mon, Dec 12, 2022, 12:02 PM David Handermann <
> exceptionfact...@apache.org>
> wrote:
>
> > Team,
> >
> > Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> > recent discussion thread [2], I am calling this vote to adopt the
> following
> > as Release Goals for NiFi 2.0:
> >
> > 1. Remove Java 8 support and require Java 11
> > 2. Remove deprecated components
> > 3. Remove deprecated component properties
> > 4. Remove components integrating with unmaintained services
> > 5. Remove compatibility classes and methods
> > 6. Remove flow.xml.gz in favor of flow.json.gz
> > 7. Remove duplicative features
> > 8. Upgrade internal Java API references
> > 9. Reorganize standard components
> > 10. Implement migration tools for upgrading flows
> >
> > A positive vote indicates agreement on these goals and the initiation of
> > the following actions:
> >
> > 1. Rename NiFi 2.0 Proposed Release Goals to NiFi 2.0 Release Goals
> > 2. Create version 1 branch in Git for subsequent support releases on the
> > version 1 series
> > 3. Update the current main branch in Git to version 2.0.0-SNAPSHOT
> >
> > The vote will be open for 72 hours and follow standard procedures for
> > release votes.
> >
> > Please review the linked goals and discussions for background.
> >
> > [ ] +1 Adopt NiFi 2.0 Release Goals
> > [ ] +0 No opinion
> > [ ] -1 Do not adopt NiFi 2.0 Release Goals for the following reasons...
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Proposed+Release+Goals
> > [2] https://lists.apache.org/thread/xo77p9t3xg4k70356xrqbdg4m9sg7sf8
> >
>

Re: New NiFi PMC Member Nathan Gough

[Steven Matison]

Congrats Nathan!!

On Wed, Sep 7, 2022 at 12:37 PM Kevin Doran  wrote:

>  Congrats Nathan!
>
> On Sep 7, 2022 at 12:24:17, Otto Fowler  wrote:
>
> > Congratulations, thanks for all you do
> >
> >
> >
> >
> > From: David Handermann 
> > 
> > Reply: dev@nifi.apache.org  
> > Date: September 7, 2022 at 12:10:21
> > To: dev@nifi.apache.org  
> > Subject:  New NiFi PMC Member Nathan Gough
> >
> > Apache NiFi Community,
> >
> > On behalf of the Apache NiFi Project Management Committee, I am very
> > pleased to announce that Nathan Gough has accepted the invitation to join
> > the PMC.
> >
> > Nathan has been a consistent contributor to the project since 2018. In
> > addition to developing features and fixes, he regularly reviews pull
> > requests and assists others through mailing lists and Slack
> conversations.
> > He also plays an active role in reviewing and updating security reports
> for
> > the project.
> >
> > Please join us in congratulating and welcoming Nathan to the Apache NiFi
> > PMC. Congratulations Nathan!
> >
>

Re: nifi.apache.org website

[Steven Matison]

Just getting back to his thread with an update.

There is a Jira for site migration to new platform

https://issues.apache.org/jira/browse/NIFI-6848

We have a slack channel on the NiFi Slack for discussion

#apachenifiwebsite

There is a PR for all of the bare minimum changes to roll current site in
Hugo Framework.

https://github.com/apache/nifi-site/pull/61

If you want to roll an example of the new hugo site, follow README on my
repo

https://github.com/steven-matison/nifi-site


Suggestions, comments, and feedback are welcome.




On Mon, Mar 21, 2022 at 9:03 AM Bryan Bende  wrote:

> I left a comment on the JIRA, but all NARs are released to Maven
> central on each release. The profiles just determine what is included
> in the assembly. So users can still get any of the non-included NARs
> by downloading it from Maven central, it just isn't obvious how to
> find it.
>
> On Mon, Mar 21, 2022 at 8:18 AM Mike Thomsen 
> wrote:
> >
> > Pierre raised an interesting idea here:
> > https://issues.apache.org/jira/browse/NIFI-7360
> >
> > We might want to consider a process for allowing a directory of
> > downloadable NARs from third parties as a stop-gap while the Registry
> > gets fleshed out on providing access to NARs.
> >
> > On Wed, Mar 16, 2022 at 5:04 PM Matt Gilman 
> wrote:
> > >
> > > Thanks Jon. The invite link for Slack is at the bottom of this page
> [1].
> > >
> > > [1] https://nifi.apache.org/mailing_lists.html
> > >
> > > On Wed, Mar 16, 2022 at 4:46 PM Jonathan Conti-Vock <
> > > jonathan.contiv...@gmail.com> wrote:
> > >
> > > > Thanks for the update Steven. Correct me if I'm wrong, but I'll need
> > > > someone to invite me as a guest to follow along in the slack channel,
> > > > correct? I would be happy to and interested in lending my UI/UX
> experience
> > > > to this conversation.
> > > >
> > > > Cheers,
> > > >
> > > > Jon
> > > >
> > > > On Wed, Mar 16, 2022 at 3:39 PM Steven Matison <
> steven.mati...@gmail.com>
> > > > wrote:
> > > >
> > > > > Just a quick update on this thread.  Progress has been made and we
> have
> > > > an
> > > > > initial hugo framework able to run the current site.
> > > > >
> > > > > Please join us in follow on conversation in #apachenifiwebsite on
> slack!
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Mar 11, 2022 at 8:25 AM Joe Witt 
> wrote:
> > > > >
> > > > > > done.  and added you
> > > > > >
> > > > > > On Fri, Mar 11, 2022 at 6:17 AM Steven Matison <
> > > > steven.mati...@gmail.com
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > So glad there is such an interest in this.
> > > > > > >
> > > > > > > Can we move discussion into a slack channel dedicated to this
> topic?
> > > > > > >
> > > > > > > On Wed, Mar 9, 2022 at 2:47 PM Steven Matison <
> > > > > steven.mati...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Sounds awesome, gimme some time to go through everything you
> guys
> > > > > have
> > > > > > > > shared.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Wed, Mar 9, 2022 at 2:28 PM Andrew Lim <
> > > > > andrewlim.apa...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Hi Steven,
> > > > > > > >>
> > > > > > > >> Excited by your interest in this! A Jira was created to
> migrate
> > > > the
> > > > > > NiFi
> > > > > > > >> website to ASF git build/deploy [1]. I’ve been meaning to
> work on
> > > > it
> > > > > > but
> > > > > > > >> haven’t had the cycles.
> > > > > > > >>
> > > > > > > >> In my research on static-site generators, Hugo [2] came up
> as a
> > > > very
> > > > > > > >> strong candidate especially due to its speed. There are 10
> Apache
> > > > > &g

Re: Upgrading Cassandra driver and bringing in breaking changes with it

[Steven Matison]

Sure, as long as you can help guide me in the right direction.   I'll send
you a slack msg...

On Tue, Jun 14, 2022 at 7:40 AM Mike Thomsen  wrote:

> Steve,
>
> Do you want to break up the ticket into a controller service ticket
> and an update ticket for the processors? You could do the former while
> I do the latter if you want to get your hands dirty making a
> contribution here.
>
> Thanks,
>
> Mike
>
> On Fri, Jun 10, 2022 at 4:32 PM Steven Matison 
> wrote:
> >
> > I'd like to get in on this one if you guys need anything.
> >
> >
> >
> > On Fri, Jun 10, 2022 at 4:12 PM David Handermann <
> > exceptionfact...@apache.org> wrote:
> >
> > > Mike,
> > >
> > > Thanks for digging into this issue! I agree that simplifying the
> > > implementation makes going forward. The newer driver version involves
> > > changes in the Controller Service method signatures either way, so
> > > streamlining the connection handling approach would be helpful.
> > >
> > > Based on feedback, perhaps summarizing the planned implementation in
> the
> > > Jira issue would be helpful.
> > >
> > > Regards,
> > > David Handermann
> > >
> > > On Fri, Jun 10, 2022 at 3:06 PM Mike Thomsen 
> > > wrote:
> > >
> > > > https://issues.apache.org/jira/browse/NIFI-9770
> > > >
> > > > Based on David's description saying it will require some deep changes
> > > > to how various properties are configured, I think this ticket would
> be
> > > > a good time to simplify the Cassandra bundle in general to just use a
> > > > controller service to configure the connection. (Current approach is
> > > > controller service or manual configuration on a per-processor basis).
> > > >
> > > > Thoughts?
> > > >
> > >
>

Re: Upgrading Cassandra driver and bringing in breaking changes with it

[Steven Matison]

I'd like to get in on this one if you guys need anything.



On Fri, Jun 10, 2022 at 4:12 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Mike,
>
> Thanks for digging into this issue! I agree that simplifying the
> implementation makes going forward. The newer driver version involves
> changes in the Controller Service method signatures either way, so
> streamlining the connection handling approach would be helpful.
>
> Based on feedback, perhaps summarizing the planned implementation in the
> Jira issue would be helpful.
>
> Regards,
> David Handermann
>
> On Fri, Jun 10, 2022 at 3:06 PM Mike Thomsen 
> wrote:
>
> > https://issues.apache.org/jira/browse/NIFI-9770
> >
> > Based on David's description saying it will require some deep changes
> > to how various properties are configured, I think this ticket would be
> > a good time to simplify the Cassandra bundle in general to just use a
> > controller service to configure the connection. (Current approach is
> > controller service or manual configuration on a per-processor basis).
> >
> > Thoughts?
> >
>

Re: nifi.apache.org website

[Steven Matison]

Just a quick update on this thread.  Progress has been made and we have an
initial hugo framework able to run the current site.

Please join us in follow on conversation in #apachenifiwebsite on slack!



On Fri, Mar 11, 2022 at 8:25 AM Joe Witt  wrote:

> done.  and added you
>
> On Fri, Mar 11, 2022 at 6:17 AM Steven Matison 
> wrote:
>
> > So glad there is such an interest in this.
> >
> > Can we move discussion into a slack channel dedicated to this topic?
> >
> > On Wed, Mar 9, 2022 at 2:47 PM Steven Matison 
> > wrote:
> >
> > > Sounds awesome, gimme some time to go through everything you guys have
> > > shared.
> > >
> > >
> > >
> > > On Wed, Mar 9, 2022 at 2:28 PM Andrew Lim 
> > > wrote:
> > >
> > >> Hi Steven,
> > >>
> > >> Excited by your interest in this! A Jira was created to migrate the
> NiFi
> > >> website to ASF git build/deploy [1]. I’ve been meaning to work on it
> but
> > >> haven’t had the cycles.
> > >>
> > >> In my research on static-site generators, Hugo [2] came up as a very
> > >> strong candidate especially due to its speed. There are 10 Apache
> > websites
> > >> that currently use Hugo [3]. Apache Jena is one of them and that team
> > >> documented their migration steps on their wiki [4].
> > >>
> > >> Perhaps you could do some research and share your findings. If we can
> > get
> > >> a working version of the current NiFi website in a chosen generator,
> we
> > can
> > >> get a Discuss thread going in the community similar to what Apache
> Jena
> > did
> > >> [5].
> > >>
> > >> I would love to help with the migration as well as a refresh of the
> > site!
> > >>
> > >> -Drew
> > >>
> > >>
> > >> [1] https://issues.apache.org/jira/browse/NIFI-6848 <
> > >> https://issues.apache.org/jira/browse/NIFI-6848>
> > >> [2] https://gohugo.io/ <https://gohugo.io/>
> > >> [3]
> > >>
> https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories
> > <
> > >> https://github.com/search?q=topic:hugo+org:apache&type=Repositories>
> > >> [4]
> > >>
> >
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> > >> <
> > >>
> >
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> > >> >
> > >> [5] https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr
> <
> > >> https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr>
> > >>
> > >>
> > >> > On Mar 9, 2022, at 1:59 PM, David Handermann <
> > >> exceptionfact...@apache.org> wrote:
> > >> >
> > >> > Hi Steven,
> > >> >
> > >> > Thanks for your interest! This would also be a great opportunity to
> > >> > streamline the HTML generation approach to use something like Hugo
> or
> > >> > similar static-site generation system.
> > >> >
> > >> > Regards,
> > >> > David Handermann
> > >> >
> > >> > On Wed, Mar 9, 2022 at 12:44 PM Joe Witt 
> wrote:
> > >> >
> > >> >> Steven
> > >> >>
> > >> >> To say this is super welcome is an understatement.  We definitely
> > need
> > >> the
> > >> >> facelift you mention and we need to get off the old website
> mechanism
> > >> and
> > >> >> onto the newer one the ASF wants projects using.  This would be
> > >> awesome!
> > >> >>
> > >> >> Thanks!
> > >> >>
> > >> >>
> > >> >> On Wed, Mar 9, 2022 at 11:40 AM Steven Matison <
> > >> steven.mati...@gmail.com>
> > >> >> wrote:
> > >> >>
> > >> >>> Hey Dev Team,
> > >> >>>
> > >> >>>  Is there any way I could assist with modernizing the
> > >> >> nifi.apache.org
> > >> >>> website?
> > >> >>>
> > >> >>> Its 2022 and I think a facelift is in order...  I have a ton of
> > >> >> experience
> > >> >>> with web-dev and super passionate about NiFi.  This would be
> > >> something I
> > >> >>> would love to be a part of.
> > >> >>>
> > >> >>> Thanks,
> > >> >>>
> > >> >>> Steven
> > >> >>>
> > >> >>
> > >>
> > >>
> >
>

Re: nifi.apache.org website

[Steven Matison]

So glad there is such an interest in this.

Can we move discussion into a slack channel dedicated to this topic?

On Wed, Mar 9, 2022 at 2:47 PM Steven Matison 
wrote:

> Sounds awesome, gimme some time to go through everything you guys have
> shared.
>
>
>
> On Wed, Mar 9, 2022 at 2:28 PM Andrew Lim 
> wrote:
>
>> Hi Steven,
>>
>> Excited by your interest in this! A Jira was created to migrate the NiFi
>> website to ASF git build/deploy [1]. I’ve been meaning to work on it but
>> haven’t had the cycles.
>>
>> In my research on static-site generators, Hugo [2] came up as a very
>> strong candidate especially due to its speed. There are 10 Apache websites
>> that currently use Hugo [3]. Apache Jena is one of them and that team
>> documented their migration steps on their wiki [4].
>>
>> Perhaps you could do some research and share your findings. If we can get
>> a working version of the current NiFi website in a chosen generator, we can
>> get a Discuss thread going in the community similar to what Apache Jena did
>> [5].
>>
>> I would love to help with the migration as well as a refresh of the site!
>>
>> -Drew
>>
>>
>> [1] https://issues.apache.org/jira/browse/NIFI-6848 <
>> https://issues.apache.org/jira/browse/NIFI-6848>
>> [2] https://gohugo.io/ <https://gohugo.io/>
>> [3]
>> https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories <
>> https://github.com/search?q=topic:hugo+org:apache&type=Repositories>
>> [4]
>> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
>> <
>> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
>> >
>> [5] https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr <
>> https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr>
>>
>>
>> > On Mar 9, 2022, at 1:59 PM, David Handermann <
>> exceptionfact...@apache.org> wrote:
>> >
>> > Hi Steven,
>> >
>> > Thanks for your interest! This would also be a great opportunity to
>> > streamline the HTML generation approach to use something like Hugo or
>> > similar static-site generation system.
>> >
>> > Regards,
>> > David Handermann
>> >
>> > On Wed, Mar 9, 2022 at 12:44 PM Joe Witt  wrote:
>> >
>> >> Steven
>> >>
>> >> To say this is super welcome is an understatement.  We definitely need
>> the
>> >> facelift you mention and we need to get off the old website mechanism
>> and
>> >> onto the newer one the ASF wants projects using.  This would be
>> awesome!
>> >>
>> >> Thanks!
>> >>
>> >>
>> >> On Wed, Mar 9, 2022 at 11:40 AM Steven Matison <
>> steven.mati...@gmail.com>
>> >> wrote:
>> >>
>> >>> Hey Dev Team,
>> >>>
>> >>>  Is there any way I could assist with modernizing the
>> >> nifi.apache.org
>> >>> website?
>> >>>
>> >>> Its 2022 and I think a facelift is in order...  I have a ton of
>> >> experience
>> >>> with web-dev and super passionate about NiFi.  This would be
>> something I
>> >>> would love to be a part of.
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Steven
>> >>>
>> >>
>>
>>

Contributor Access

[Steven Matison]

Hi just requesting access

username stevenmatison

Thanks,

Steven

Re: nifi.apache.org website

[Steven Matison]

Sounds awesome, gimme some time to go through everything you guys have
shared.



On Wed, Mar 9, 2022 at 2:28 PM Andrew Lim 
wrote:

> Hi Steven,
>
> Excited by your interest in this! A Jira was created to migrate the NiFi
> website to ASF git build/deploy [1]. I’ve been meaning to work on it but
> haven’t had the cycles.
>
> In my research on static-site generators, Hugo [2] came up as a very
> strong candidate especially due to its speed. There are 10 Apache websites
> that currently use Hugo [3]. Apache Jena is one of them and that team
> documented their migration steps on their wiki [4].
>
> Perhaps you could do some research and share your findings. If we can get
> a working version of the current NiFi website in a chosen generator, we can
> get a Discuss thread going in the community similar to what Apache Jena did
> [5].
>
> I would love to help with the migration as well as a refresh of the site!
>
> -Drew
>
>
> [1] https://issues.apache.org/jira/browse/NIFI-6848 <
> https://issues.apache.org/jira/browse/NIFI-6848>
> [2] https://gohugo.io/ <https://gohugo.io/>
> [3]
> https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories <
> https://github.com/search?q=topic:hugo+org:apache&type=Repositories>
> [4]
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> <
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> >
> [5] https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr <
> https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr>
>
>
> > On Mar 9, 2022, at 1:59 PM, David Handermann <
> exceptionfact...@apache.org> wrote:
> >
> > Hi Steven,
> >
> > Thanks for your interest! This would also be a great opportunity to
> > streamline the HTML generation approach to use something like Hugo or
> > similar static-site generation system.
> >
> > Regards,
> > David Handermann
> >
> > On Wed, Mar 9, 2022 at 12:44 PM Joe Witt  wrote:
> >
> >> Steven
> >>
> >> To say this is super welcome is an understatement.  We definitely need
> the
> >> facelift you mention and we need to get off the old website mechanism
> and
> >> onto the newer one the ASF wants projects using.  This would be awesome!
> >>
> >> Thanks!
> >>
> >>
> >> On Wed, Mar 9, 2022 at 11:40 AM Steven Matison <
> steven.mati...@gmail.com>
> >> wrote:
> >>
> >>> Hey Dev Team,
> >>>
> >>>  Is there any way I could assist with modernizing the
> >> nifi.apache.org
> >>> website?
> >>>
> >>> Its 2022 and I think a facelift is in order...  I have a ton of
> >> experience
> >>> with web-dev and super passionate about NiFi.  This would be something
> I
> >>> would love to be a part of.
> >>>
> >>> Thanks,
> >>>
> >>> Steven
> >>>
> >>
>
>

nifi.apache.org website

[Steven Matison]

Hey Dev Team,

  Is there any way I could assist with modernizing the nifi.apache.org
website?

Its 2022 and I think a facelift is in order...  I have a ton of experience
with web-dev and super passionate about NiFi.  This would be something I
would love to be a part of.

Thanks,

Steven

Re: InvokeHTTP : how to set a bearer token auth

[Steven Matison]

Check out this article here:

https://pierrevillard.com/2017/01/31/nifi-and-oauth-2-0-to-request-wordpress-api/
 



TL;DR; you simply add the property you want to the processor.   You just need 
to make sure you get it formatted correctly.  I would recommend or assume you 
already have examples, for example a sample postman call, so just duplicate the 
same headers until NiFi connects.





> On Mar 4, 2022, at 8:52 AM, Nicola Biadene 
>  wrote:
> 
> Dear all,
>  
> how can I set a bearer token on a InvokeHTTP operator?
>  
> I cannot find documentation and a field referring to this parameter.
>  
>  
> Regards.
>  
>  
> Nicola Biadene
> Software Engineer
> nicola.biad...@targatelematics.com 
> 
> 
> Targa Telematics S.p.A.
> Via E. Reginato, 87 – 31100 Treviso – Italia
> Tel. +39 0422 247 911
>  <>www.targatelematics.com 
>  
>  
>   
>  
>  
> 
>  
>   <>
> Stampa questa eMail solo se realmente necessario
>  
> Le informazioni contenute nella comunicazione che precede possono essere 
> riservate e sono, comunque, destinate esclusivamente alla persona o all'ente 
> sopraindicati. La diffusione, distribuzione e/o copiatura del documento 
> trasmesso da parte di qualsiasi soggetto diverso dal destinatario è proibita. 
> La sicurezza e la correttezza dei messaggi di posta elettronica non possono 
> essere garantite. Se avete ricevuto questo messaggio per errore, Vi preghiamo 
> di contattarci immediatamente e di eliminarlo dai vostri sistemi. Informativa 
> sulla privacy  di Targa Telematics 
> S.p.A.
>  
> 
> Please consider your environmental responsibility before printing this eMail
>  
> This communication is intended only for use by the addressee. It may contain 
> confidential or privileged information. Transmission cannot be guaranteed to 
> be secure or error-free. If you receive this communication unintentionally, 
> please inform us immediately and delete it from your systems. Targa 
> Telematics S.p.A. privacy policy 
> .

Re: MiNiFi Java -> NiFi

[Steven Matison]

Way to GO!!!  This is awesome stuff.


Steven Matison | Data Architect
Mobile 321.848.4926
steven.mati...@datastax.com | datastax.com

> On Apr 28, 2021, at 2:08 PM, Matt Burgess  wrote:
> 
> All,
> 
> Now that [1] is merged, MiNiFi Java is now officially in the NiFi
> codebase! Thanks to all who participated in discussions, reviews, and
> testing. Here are some notes on what this means going forward:
> 
> - All future releases of MiNiFi Java will be in lockstep with NiFi,
> the next release version will be 1.14.0 rather than 0.6.0. MiNiFi Java
> artifacts will be built and published as part of the NiFi release
> process. This will allow MiNiFi to immediately benefit from
> improvements/fixes in NiFi components instead of occasionally updating
> the NiFi dependency version in MiNiFi Java.
> 
> - Although we will continue to track issues in Jira under the MINIFI
> project, PRs should be submitted against the nifi repo's main branch.
> If you have an open PR against the nifi-minifi repo, you can port it
> to the nifi repo by adding ".patch" to the URL of your PR, downloading
> the patch, and applying it to a branch in your fork of the nifi repo,
> for example:
> 
> git checkout -b MINIFI-541
> git apply --directory='minifi' ~/195.patch
> 
> Sooner than later we'll make the nifi-minifi repo read-only so no more
> PRs can be submitted against it, and we can update NiFi's PR template
> to refer to MINIFI Jira cases as well.
> 
> There's still work to be done of course, contributions and PR reviews
> are most welcome!
> 
> Regards,
> Matt
> 
> [1] https://github.com/apache/nifi/pull/4933

Re: Jira contributor access request

[Steven Matison]

I would like this level of access now too please.

Username: ds-steven-matison


TY sir!!


Steven Matison | Data Architect
Mobile 321.848.4926
steven.mati...@datastax.com | datastax.com

> On Nov 12, 2020, at 1:49 PM, Pierre Villard  
> wrote:
> 
> Hey Chris,
> 
> I just added you, thanks!
> 
> Pierre
> 
> Le jeu. 12 nov. 2020 à 19:29, Chris Sampson
>  a écrit :
> 
>> Please grant me Jira contributor access, username: Chris S
>> 
>> 
>> Cheers,
>> 
>> Chris Sampson
>>