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

NIFI-13288 On Thu, May 23, 2024 at 12:46 PM Dan S wrote: > I will make a ticket for this. Thanks! > > On Thu, May 23, 2024 at 12:45 PM Mark Payne wrote: > >> Hey Dan, >> >> Yessir, it absolutely would! Probably would be good to clean those up.

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

I will make a ticket for this. Thanks! On Thu, May 23, 2024 at 12:45 PM Mark Payne wrote: > Hey Dan, > > Yessir, it absolutely would! Probably would be good to clean those up. > > Thanks > -Mark > > > > On May 23, 2024, at 12:29 PM, Dan S wrote: > > > > Mark, > > In regards to your last

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

Hey Dan, Yessir, it absolutely would! Probably would be good to clean those up. Thanks -Mark > On May 23, 2024, at 12:29 PM, Dan S wrote: > > Mark, > In regards to your last comments > >> Not really related, but on the note of things you may not realize, with >> that code snippet :) >> If

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

Mark, In regards to your last comments > 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

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

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.

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

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.

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

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

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

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

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

uuid=cfb2a124-4b07-46bd-a70e-3848502b3df1,claim=StandardContentClaim > \ > [resourceClaim=StandardResourceClaim[id=1715094869203-1, container=default, > section=1], offset=0, > length=1077766],offset=0,name=30575811037248611,size=1077766] \ &g

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

ContentClaim > \ > [resourceClaim=StandardResourceClaim[id=1715094869203-1, > container=default, section=1], offset=0, > length=1077766],offset=0,name=30575811037248611,size=1077766] \ > is not the most recent version of this FlowFile within this session > (StandardProcessSession[id

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

=30575811037248611,size=1077766] \ is not the most recent version of this FlowFile within this session (StandardProcessSession[id=3923]): \ org.apache.nifi.processor.exception.FlowFileHandlingException: StandardFlowFileRecord[uuid=cfb2a124-4b07-46bd-a70e-3848502b3df1,claim=StandardContentClaim \ [resourceClaim