Joe, One additional note for 1.19.1, the following Jira issue and associated pull request just merged resolve a regression in Kafka component configuration when using SCRAM-SHA-256 or SCRAM-SHA-512 as the SASL Mechanism:
https://issues.apache.org/jira/browse/NIFI-10919 Regards, David Handermann On Wed, Nov 30, 2022 at 1:55 PM Joe Witt <joe.w...@gmail.com> wrote: > Grabbed all the goods from main post 1.19 and have them on branch > 'support/nifi-1.19' > > Waiting on https://issues.apache.org/jira/browse/NIFI-10914 and then > will roll with the 1.19.1 RC. > > Thanks > > On Wed, Nov 30, 2022 at 8:23 AM Joe Witt <joe.w...@gmail.com> wrote: > > > > Team, > > > > I'm thinking it might be worthwhile to spin up a 1.19.1. Want to be > > respectful of everyone's time as I realize these votes aren't always > > easy to participate in. > > > > The main reason has to do with the registry/client changes and how > > that has been creating problems for people as they upgrade past 1.16. > > We thought it was sorted in 1.19 but not so - as shown in > > https://issues.apache.org/jira/browse/NIFI-10874. For those watching > > in Slack this has been biting several users lately. > > > > I'll sweep up existing already landed items that are easily ported over. > > > > I do realize we've got the nar plugin being updated to help detect > > dupe dependencies in nar chains as well as to help with reproducible > > builds but we could pull that in for 1.19.2 if we have one but > > certainly 1.20. > > > > Thanks >
