+1 (binding)

Performed my usual checks. Thanks for RM’ing, Pierre.

Thanks,
Kevin

On Thu, Jun 18, 2026 at 5:58 PM Andrew Lim <[email protected]>
wrote:

> I had similar issues trying to configure and run the "KafkaToS3" connector.
> The documentation for this specific connector says "If using SASL
> authentication, provide your username and password credentials." No mention
> of how to configure the SASL Password property to use secrets.
>
> I agree more documentation is needed on how to use Connectors that is
> accessible in the User Guide . For example, how does a user make their own
> connectors available to add/use?
>
> Outside of Connectors:
>
> +1 (binding)
>
> -Verified Core UI and Documentation changes
> -Ran basic flows successfully
>
> Drew
>
> On Thu, Jun 18, 2026 at 5:33 PM Matt Burgess <[email protected]> wrote:
>
> > I did have some questions around Connectors though:
> >
> > 1) I can't find any documentation in the User Guide or elsewhere, just
> some
> > in the only existing connector. It doesn't explain how to get "secrets"
> to
> > populate the SASL Password property for example. Not sure what the
> > mechanism is but if a user just wants to provide a password without
> setting
> > up a Secrets Manager or whatever, we should have some simple
> implementation
> > for whatever mechanism is used, just to provide a password. For Connector
> > documentation, am I missing something or is that coming later?
> > 2) I couldn't find an "Experimental" tag, annotation, or doc. If this
> isn't
> > experimental, is the community expected to support these right away like
> > all other components?
> > 3) If I go to the canvas and look at ConsumeKafka then try to follow the
> > Kafka3ConnectionService with the "Go To" link, it doesn't work. Should I
> > write up a Jira?
> >
> > I think in general we should make sure Connectors are dead-simple to
> > configure or we may not see much adoption. Just my two cents :)
> >
> > Thanks,
> > Matt
> >
> >
> > On Thu, Jun 18, 2026 at 1:12 PM Matt Burgess <[email protected]>
> wrote:
> >
> > > +1 (binding) Ran through the release helper and all my usual test
> flows.
> > >
> > > Thanks for RM'ing Pierre!
> > >
> > > On Mon, Jun 15, 2026 at 10:39 PM Pierre Villard <
> > > [email protected]> wrote:
> > >
> > >> Team,
> > >>
> > >> I am pleased to be calling this vote for the source release of Apache
> > >> NiFi 2.10.0.
> > >>
> > >> Please review the following guide for how to verify a release
> candidate
> > >> build:
> > >>
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
> > >>
> > >> The source being voted on the and the convenience binaries are
> > >> available on the Apache Distribution Repository:
> > >>
> > >> https://dist.apache.org/repos/dist/dev/nifi/nifi-2.10.0
> > >>
> > >> The build artifacts are available on the Apache Nexus Repository:
> > >>
> > >> https://repository.apache.org/content/repositories/orgapachenifi-1360
> > >>
> > >> Git Tag: nifi-2.10.0-RC2
> > >> Git Commit ID: 2baff691128fa782983fb79bb1087adff027a4c1
> > >> GitHub Commit Link:
> > >>
> > >>
> >
> https://github.com/apache/nifi/commit/2baff691128fa782983fb79bb1087adff027a4c1
> > >>
> > >> Hash of nifi-2.10.0-source-release.zip
> > >>
> > >> SHA512:
> > >>
> >
> 33af676d50d9eb1c81d0b3cedb7a908c36a491a7e5abea25acb7e93876324ecd3d3834ea9ac00d26ed8e2377e3f5f719e2a57ae59a3cdab44ad824c8bdf32d23
> > >>
> > >> Release artifacts are signed with the following key:
> > >>
> > >> https://people.apache.org/keys/committer/pvillard.asc
> > >>
> > >> KEYS file is available on the Apache Distribution Repository:
> > >>
> > >> https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >>
> > >> Issues resolved for this version: 164
> > >>
> > >>
> > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12356833
> > >>
> > >> Release note highlights can be found on the project wiki:
> > >>
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.10.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-2.10.0
> > >> [] +0 no opinion
> > >> [] -1 Do not release this package because...
> > >>
> > >> Thanks,
> > >> Pierre
> > >>
> > >
> >
>

Reply via email to