Re: Build of 2.x failing on Centos 7

2024-04-19 Thread Michael Moser 
Perhaps this was an unintentional change to the nifi-web-ui from the
NIFI-13035 PR that was merged recently?

-- Mike


On Fri, Apr 19, 2024 at 12:06 PM Dan S  wrote:

> Thanks David!
>  I did not have this problem the other day when I submitted a PR for
> NIFI-12960.
>
> On Fri, Apr 19, 2024 at 12:02 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Dan,
> >
> > Reviewing the previous thread, the last reply from Matt Gilman still
> > applies [1] meaning that CentOS 7 is not recent enough to support the
> > version of Node.js required.
> >
> > CentOS 7 is also scheduled for End of Life [2] on June 30, 2024. Based
> > on the compatibility issues with the core OS libraries, I would not
> > expect CentOS 7 to be supported for building NiFi 2.0.
> >
> > Regards,
> > David Handermann
> >
> > [1] https://lists.apache.org/thread/jdmw7dsjryyf8vbjgq84tl8kpv68pplr
> > [2] https://www.redhat.com/en/topics/linux/centos-linux-eol
> >
> > On Fri, Apr 19, 2024 at 10:51 AM Dan S  wrote:
> > >
> > > I am trying to build the 2.x branch for a PR I am trying to submit for
> > > NIFI-13069 and it is failing. Here are the messages I see from the
> build
> > >
> > > [INFO]
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > /lib64/libm.so.6: version `GLIBC_2.27' not found (required by
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > [INFO]
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > [INFO]
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > [INFO]
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > [INFO]
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > /lib64/libc.so.6: version `GLIBC_2.27' not found (required by
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > [INFO]
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > /lib64/libc.so.6: version `GLIBC_2.28' not found (required by
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > [INFO]
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > /lib64/libc.so.6: version `GLIBC_2.25' not found (required by
> > >
> >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > >
> > > [ERROR] Failed to execute goal
> > > com.github.eirslett:frontend-maven-plugin:1.14.2:npm (npm install) on
> > > project nifi-web-ui: Failed to run task: 'npm run ci' failed.
> > > org.apache.commons.exec.ExecuteException: Process exited with an
> error: 1
> > > (Exit value: 1) -> [Help 1]
> > >
> > > This seems the same problem I had back In November 2023 on this thread
> > > 
> > > Please advise.
> >
>

Re: Build of 2.x failing on Centos 7

2024-04-19 Thread Michael Moser 
Thanks for explaining the intent, David, and it makes perfect sense.

-- Mike


On Fri, Apr 19, 2024 at 12:26 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Mike,
>
> The change was intentional from my understanding as Node.js 16 reached
> end of life last year [1]. Registry should also be updated to build
> with a more recent version of Node.js, but I believe there are some
> details to sort out before that can be changed.
>
> Regards,
> David Handermann
>
> [1] https://nodejs.org/en/blog/announcements/nodejs16-eol
>
> On Fri, Apr 19, 2024 at 11:12 AM David Handermann
>  wrote:
> >
> > Dan,
> >
> > Reviewing recent changes, NIFI-13035 [1] updated the frontend build
> > process to use Node.js 21 for both the current nifi-web-ui and the new
> > nifi-web-frontend modules. For that reason, a more recent OS and glibc
> > version is now required.
> >
> > Regards,
> > David Handermann
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-13035
> >
> > On Fri, Apr 19, 2024 at 11:06 AM Dan S  wrote:
> > >
> > > Thanks David!
> > >  I did not have this problem the other day when I submitted a PR for
> > > NIFI-12960.
> > >
> > > On Fri, Apr 19, 2024 at 12:02 PM David Handermann <
> > > exceptionfact...@apache.org> wrote:
> > >
> > > > Dan,
> > > >
> > > > Reviewing the previous thread, the last reply from Matt Gilman still
> > > > applies [1] meaning that CentOS 7 is not recent enough to support the
> > > > version of Node.js required.
> > > >
> > > > CentOS 7 is also scheduled for End of Life [2] on June 30, 2024.
> Based
> > > > on the compatibility issues with the core OS libraries, I would not
> > > > expect CentOS 7 to be supported for building NiFi 2.0.
> > > >
> > > > Regards,
> > > > David Handermann
> > > >
> > > > [1] https://lists.apache.org/thread/jdmw7dsjryyf8vbjgq84tl8kpv68pplr
> > > > [2] https://www.redhat.com/en/topics/linux/centos-linux-eol
> > > >
> > > > On Fri, Apr 19, 2024 at 10:51 AM Dan S  wrote:
> > > > >
> > > > > I am trying to build the 2.x branch for a PR I am trying to submit
> for
> > > > > NIFI-13069 and it is failing. Here are the messages I see from the
> build
> > > > >
> > > > > [INFO]
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > > > /lib64/libm.so.6: version `GLIBC_2.27' not found (required by
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > > > [INFO]
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > > > /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found
> (required by
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > > > [INFO]
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > > > /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required
> by
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > > > [INFO]
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > > > /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found
> (required by
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > > > [INFO]
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > > > /lib64/libc.so.6: version `GLIBC_2.27' not found (required by
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > > > [INFO]
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > > > /lib64/libc.so.6: version `GLIBC_2.28' not found (required by
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node)
> > > > > [INFO]
> > > > >
> > > >
> git/NIFI-FORK/nifi-2.x/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/target/frontend-working-directory/node/node:
> > > > > /lib64/libc.so.6: version `GLIBC_2.25' not found (required by
> > > > >
>

Re: ...not the most recent version of this FlowFile within this session...

2024-05-08 Thread Michael Moser 
Oh yeah, I do love this behavior of ProcessSession.  And thanks for the
tip, it's easy to forget that there are efficiencies to be gained by using
different parts of an API.

-- Mke


On Wed, May 8, 2024 at 11:04 AM Mark Payne  wrote:

> Yeah, that was something that kinda flew under the radar. Definitely
> improved the API.
>
> Not really related, but on the note of things you may not realize, with
> that code snippet :)
> If you have access to update the processor mentioned here, you should
> avoid using session.putAttribute many times.
> Under the hood, in order to maintain object immutability it has to create
> a new FlowFile object (and a new HashMap of all attributes!)
> for every call to putAttribute. So if there are 100 attributes that match
> that’s potentially a huge amount of garbage getting created. Instead,
> you could just use:
>
> ```
> final Map attributes = new HashMap<>();
> flowFile.getAttributes().forEach( (key, value) -> {
>   if (key.startsWith(“foo”)) {
> attributes.put(“original-“ + key, value);
>   }
> }
>
> flowFIle = session.putAllAttributes(flowFile, attributes);
> ```
>
> Thanks
> -Mark
>
>
>
> > On May 8, 2024, at 10:30 AM, Michael Moser  wrote:
> >
> > Wow, thanks for this information!  Just last week I saw code that
> modified
> > attributes in a stream:
> >
> > flowFile.getAttributes().entrySet().stream().filter(e ->
> > e.getKey().startsWith("foo"))
> >.forEach(e -> session.putAttribute(flowFile, "original-" + e.getKey,
> > e.getValue()));
> >
> > and I wondered how that could possibly work since the return value of
> > session.putAttribute is ignored!  Now I know.
> >
> > -- Mike
> >
> > On Tue, May 7, 2024 at 3:02 PM Russell Bateman 
> > wrote:
> >
> >> Yes, what you described is what was happening, Mark. I didn't display
> >> all of the code to the session methods, and I did re-read the in-coming
> >> flowfile for different purposes than I had already read and written it.
> >> So, I wasn't helpful enough. In the end, however, I had forgotten,
> >> immediately after the call to session.putAllAttributes(), to update the
> >> resulting flowfile for passing to session.transfer(). That solved it for
> >> 1.1.2 which wasn't necessary for 1.13.2 or later versions. Being
> >> helpful, the newer versions made me a spoiled, entitled child and I will
> >> repent immediately.
> >>
> >> Thanks, guys! DevOps are happy they don't have to upgrade the customers
> >> to NiFi 1.13.2. (In a way, I'm unhappy about that, but...).
> >>
> >> Best regards,
> >>
> >> Russ
> >>
> >> On 5/7/24 11:53, Mark Payne wrote:
> >>> The call to session.putAttribute would throw an Exception because you
> >>> provided an outdated version of the flowFile (did not capturing the
> >>> result of calling session.write)
> >>>
> >>> Now, as NiFi matured, we found that:
> >>> (a) for more complex processors that aren’t just a series of sequential
> >>> steps it becomes difficult to manage all of that bookkeeping.
> >>> (b) it was not intuitive to require this
> >>> (c) the ProcessSession already had more or less what it needed in order
> >>> to determine what the most up-to-date version of the FlowFile was.
> >>>
> >>> So we updated the ProcessSession to automatically grab the latest
> >>> version of the FlowFile for these methods. But since you’re trying to
> >>> run an old version, you’ll need to make sure that you capture all of
> >>> those outputs and always keep track of the most recent version of a
> >>> FlowFile.
> >>
>
>

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

2024-05-06 Thread Michael Moser 
+1 (binding)

verified signature, hashes, commit ID
had a glance at the README, LICENSE, NOTICE files

built on:
Apache Maven 3.9.6 Maven home:
/home/mwmoser/.m2/wrapper/dists/apache-maven-3.9.6/a53741d1
Java version: 1.8.0_412, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.412.b08-2.el8.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.18.0-513.24.1.el8_9.x86_64", arch: "amd64",
family: "unix"

Ran some simple flows and performed some operations against NiFi Registry.

Many thanks to Pierre for being RM.

-- Mike


On Mon, May 6, 2024 at 10:25 AM Peter Turcsanyi 
wrote:

> +1 (binding)
>
> Verified signatures and hashes.
> Built NiFi on Ubuntu 22.04 with Java 8 (Temurin 1.8.0_412+8) and Java 11
> (Temurin 11.0.23+9), Maven 3.9.6 with empty local repo.
>
> Ran flows for validating:
>  - NIFI-12837 Add DFS setting to smb processors
>  - NIFI-12732 ListS3 should reset its tracking state after configuration
> change
>  - NIFI-12936 ListGCSBucket should reset its tracking state after
> configuration change
>  - NIFI-12928 Add Simple Write strategy in PutAzureDataLakeStorage
>
> Thanks for RMing Pierre!
>
> Regards,
> Peter Turcsanyi
>
> On Mon, May 6, 2024 at 4:09 PM Chris Sampson
>  wrote:
>
> > +1 (binding)
> >
> > Ran through the release helper. Verified signatures and hashes.
> >
> > Full clean build of RC with Java openjdk 11.0.23 2024-04-16 on macOS
> > Sonoma 14.4.1 using the Maven Wrapper 3.9.6.
> >
> > Ran a selection of processors/flows, primarily focussed on Elasticsearch
> > integration and HTTP Request/Response.
> >
> >
> > Cheers,
> >
> > ---
> > Chris Sampson
> > IT Consultant
> > chris.samp...@naimuri.com
> >
> >
> > > On 6 May 2024, at 14:31, David Handermann  >
> > wrote:
> > >
> > > +1 binding
> > >
> > > - Verified signatures and hashes
> > > - Ran build using Maven Wrapper 3.9.6
> > > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-382 x86_64
> > >
> > > Thanks Pierre!
> > >
> > > Regards,
> > > David Handermann
> > >
> > > On Fri, May 3, 2024 at 7:47 AM Pierre Villard
> > >  wrote:
> > >>
> > >> Team,
> > >>
> > >> I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > >> 1.26.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-1.26.0
> > >>
> > >> The build artifacts are available on the Apache Nexus Repository:
> > >>
> > >> https://repository.apache.org/content/repositories/orgapachenifi-1265
> > >>
> > >> Git Tag: nifi-1.26.0-RC1
> > >> Git Commit ID: 338083f6850b61cd2651e41bbd73b3cb5330d98c
> > >> GitHub Commit Link:
> > >>
> >
> https://github.com/apache/nifi/commit/338083f6850b61cd2651e41bbd73b3cb5330d98c
> > >>
> > >> Checksums of nifi-1.26.0-source-release.zip
> > >>
> > >> SHA256:
> 75ea201c12bb99672b1f075c9520b5f7df8b24e033ec47121848b351a0d47790
> > >> SHA512:
> > >>
> >
> 5b754d899ce8cff900d5871d44c2fda9224e69fe8a0fe9a7121f3359ed8881300e4d4d0b2fe5befea276e0495c7ebbed04cc307c18527aa7a1cea25a923a
> > >>
> > >> 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: 128
> > >>
> > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354185
> > >>
> > >> Release note highlights can be found on the project wiki:
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.26.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.26.0
> > >> [] +0 no opinion
> > >> [] -1 Do not release this package because...
> >
> >
>

Re: [VOTE] Release Apache NiFi 2.0.0-M3 (RC1)

2024-05-16 Thread Michael Moser 
+1 (binding)

Stepped through the release helper to verify the things.
Apache Maven 3.9.6  Java version: 21.0.3  Red Hat Enterprise Linux 8.9
Upgraded NiFi from 2.0.0-M2 to 2.0.0-M3.
Upgraded NiFi Registry from 2.0.0-M2 to 2.0.0-M3
Tested a few flows with no problems.

-- Mike


On Thu, May 16, 2024 at 2:25 PM Pierre Villard 
wrote:

> +1 (binding)
>
> Went through the usual steps, deployed a secured cluster with a secured
> NiFi Registry instance on GCP and tested a bunch of flows that I have
> around.
>
> Thanks for RM'ing David!
>
>
> Le jeu. 16 mai 2024 à 15:26, Matt Burgess  a écrit :
>
> > +1 (binding)
> >
> > Ran through release helper, verified various flows. Thanks for RM'ing
> > David!
> >
> > On Mon, May 13, 2024 at 11:48 PM David Handermann <
> > exceptionfact...@apache.org> wrote:
> >
> > > Team,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi 2.0.0-M3.
> > >
> > > 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 and the convenience binaries are available
> > > on the Apache Distribution Repository:
> > >
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0-M3
> > >
> > > The build artifacts are available on the Apache Nexus Repository:
> > >
> > > https://repository.apache.org/content/repositories/orgapachenifi-1269
> > >
> > > Git Tag: nifi-2.0.0-M3-RC1
> > > Git Commit ID: f2215c6522a5571189290760c55f0317f8562cbd
> > > GitHub Commit Link:
> > >
> > >
> >
> https://github.com/apache/nifi/commit/f2215c6522a5571189290760c55f0317f8562cbd
> > >
> > > Checksums of nifi-2.0.0-M3-source-release.zip
> > >
> > > SHA256:
> d471a0a9e4e04faf13bbe13c7d83be6f8002fba598bf0968a3c1b339802a185a
> > > SHA512:
> > >
> >
> cd0b8bbd3fe4ea7ebe8cdac6ac8a7afa97fd7b6a521c2cbcb2c0cdc94899b652bf3726c8fe432e16f44a9dc81907414bbb42e03113f0cd9fb51aa1de9cd727a7
> > >
> > > Release artifacts are signed with the following key:
> > >
> > > https://people.apache.org/keys/committer/exceptionfactory.asc
> > >
> > > KEYS file is available on the Apache Distribution Repository:
> > >
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > Issues resolved for this version: 411
> > >
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12354155
> > >
> > > Release note highlights can be found on the project wiki:
> > >
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3
> > >
> > > 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.0.0-M3
> > > [] +0 no opinion
> > > [] -1 Do not release this package because...
> > >
> >
>

Re: ...not the most recent version of this FlowFile within this session...

2024-05-08 Thread Michael Moser 
Wow, thanks for this information!  Just last week I saw code that modified
attributes in a stream:

flowFile.getAttributes().entrySet().stream().filter(e ->
e.getKey().startsWith("foo"))
.forEach(e -> session.putAttribute(flowFile, "original-" + e.getKey,
e.getValue()));

and I wondered how that could possibly work since the return value of
session.putAttribute is ignored!  Now I know.

-- Mike

On Tue, May 7, 2024 at 3:02 PM Russell Bateman 
wrote:

> Yes, what you described is what was happening, Mark. I didn't display
> all of the code to the session methods, and I did re-read the in-coming
> flowfile for different purposes than I had already read and written it.
> So, I wasn't helpful enough. In the end, however, I had forgotten,
> immediately after the call to session.putAllAttributes(), to update the
> resulting flowfile for passing to session.transfer(). That solved it for
> 1.1.2 which wasn't necessary for 1.13.2 or later versions. Being
> helpful, the newer versions made me a spoiled, entitled child and I will
> repent immediately.
>
> Thanks, guys! DevOps are happy they don't have to upgrade the customers
> to NiFi 1.13.2. (In a way, I'm unhappy about that, but...).
>
> Best regards,
>
> Russ
>
> On 5/7/24 11:53, Mark Payne wrote:
> > The call to session.putAttribute would throw an Exception because you
> > provided an outdated version of the flowFile (did not capturing the
> > result of calling session.write)
> >
> > Now, as NiFi matured, we found that:
> > (a) for more complex processors that aren’t just a series of sequential
> > steps it becomes difficult to manage all of that bookkeeping.
> > (b) it was not intuitive to require this
> > (c) the ProcessSession already had more or less what it needed in order
> > to determine what the most up-to-date version of the FlowFile was.
> >
> > So we updated the ProcessSession to automatically grab the latest
> > version of the FlowFile for these methods. But since you’re trying to
> > run an old version, you’ll need to make sure that you capture all of
> > those outputs and always keep track of the most recent version of a
> > FlowFile.
>

Re: Jira contributor access

2024-03-01 Thread Michael Moser 
Hello,

The bbobcik user in Apache Jira has contributor access to the NiFi
project.  Is it not working for you?  What action in Jira are you trying
to do?

-- Mike


On Fri, Mar 1, 2024 at 9:48 AM Boleslav Bobcik  wrote:

> Hello, I just wanted to check whether my request for contributor access is
> perhaps missing some aspect?
> Or could you let me know whether I should try again?
>
>
> Yours sincerely / S přátelským pozdravem,
>
> --
>   Boleslav Bobčík
>   bbob...@gmail.com
>
>
> po 19. 2. 2024 v 0:05 odesílatel Boleslav Bobcik 
> napsal:
>
> > Hello,
> > as per Contributor Guide, I'd like to ask for contributor access to the
> > project.
> > Jira username: bbobcik
> >
> > Thank you in advance.
> >
> > Yours sincerely / S přátelským pozdravem,
> >
> > --
> >   Boleslav Bobčík
> >   bbob...@gmail.com
> >
> >
>

Re: [DISCUSS] Progress Update on new UI

2024-05-30 Thread Michael Moser 
Would we prefer Jira tickets or dev emails to discuss design of the new UI?

For example: On the Summary page the old UI could show 25 rows in the table
before scrolling but the new UI shows 14 rows.  Is there any way we can
make the height of each row a bit smaller to fit more on the screen?

I do appreciate all the hard work done on the new UI.  Well done!

-- Mike


On Thu, May 30, 2024 at 2:33 PM Matt Gilman  wrote:

> Joe,
>
> Thanks for mentioning the documentation. I filed something yesterday [1] to
> capture these efforts.
>
> [1] https://issues.apache.org/jira/browse/NIFI-13314
>
> On Thu, May 30, 2024 at 2:28 PM Joe Witt  wrote:
>
> > Thanks Matt - this path makes sense to me.  I've been using the new ui
> > exclusively for the past couple of months and now with the improvements
> and
> > gaps covered I think it is the perfect time to go to it exclusively.  We
> > give at least one milestone release.  We gather feedback/fix things.
> Then
> > we launch 2.0!
> >
> > Big thanks to all those who contributed to the new UI both in coding as
> > well as feedback.
> >
> > One other thing worth tackling over time is updating documentation
> imagery
> > to leverage the new UI but that is something a large group of people can
> > contribute to and much easier when the new UI is what is in use by
> default.
> >
> > Thanks
> >
> > On Thu, May 30, 2024 at 11:09 AM Scott Aslan 
> > wrote:
> >
> > > Outstanding! The new UI is fun, fast, and fantastic. Gathering feedback
> > > from the community will be invaluable, and the best way to do this is
> by
> > > having them actively use the new UI.
> > >
> > > On Thu, May 30, 2024 at 12:37 PM Matt Gilman 
> > > wrote:
> > >
> > > > Team,
> > > >
> > > > About a month ago a [DISCUSS] thread was sent regarding the UI
> updates
> > > and
> > > > requesting that any future contributions target both old and new UIs.
> > > Since
> > > > then there has been substantial progress as we continue to close the
> > gap
> > > on
> > > > feature parity with the old UI. Only a few features remain [1] [2]
> [3]
> > > [4].
> > > >
> > > > The updated UI was included in the most recent 2.0.0-M3 release [5]
> > > > alongside the old UI. Since then we've received lots of helpful
> > feedback
> > > > and all reported bugs and differences from the existing UI have been
> > > > addressed. A new JIRA has been filed [6] to remove the old UI and
> > install
> > > > the new UI as the default. This will be a great step forward to be
> able
> > > to
> > > > move away from some frameworks that are no longer officially
> supported
> > > [7].
> > > > When 2.0.0-M4 is released it will only contain the new UI. Until then
> > > > please continue to provide any feedback.
> > > >
> > > > Additional work has begun that will establish a good path forward on
> > > > modernizing the remaining UIs within NiFi (documentation, data
> viewers,
> > > > custom UIs, etc) that also have outdated/unsupported dependencies. As
> > we
> > > > continue to make progress on the remaining features, work will begin
> to
> > > > start modernizing these other UIs.
> > > >
> > > > Matt
> > > >
> > > > [1] https://issues.apache.org/jira/browse/NIFI-13316
> > > > [2] https://issues.apache.org/jira/browse/NIFI-13317
> > > > [3] https://issues.apache.org/jira/browse/NIFI-13318
> > > > [4] https://issues.apache.org/jira/browse/NIFI-13319
> > > > [5]
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3
> > > > [6] https://issues.apache.org/jira/browse/NIFI-13313
> > > > [7] https://issues.apache.org/jira/browse/NIFI-11481
> > > >
> > >
> >
>

<    1   2