[RESULT][VOTE] Release Apache NiFi MiNiFi 0.3.0

Apache NiFi Community, I am pleased to announce that the 0.3.0 release of Apache NiFi MiNiFi passes with: 6 +1 (binding) votes 1 +1 (non-binding) votes 0 -1 votes Thanks to all who helped make this release possible. Here is the PMC vote thread:

Re: [VOTE] Release Apache NiFi MiNiFi 0.3.0 - RC3

+1, binding License and Notification looks good. Clear of binary files Builds for all components of the source look good Each of executables works as anticipated On Thu, Dec 21, 2017 at 12:39 PM, Joe Percivall wrote: > +1 (binding) > > Ran a clean build and contrib

NIFI-4715 : ListS3 list duplicate files when incoming file throughput to S3 is high

I have logged a defect in NIFI. ListS3 is generation duplicate flows  when S3 throughput is high. Root cause is: When the file gets uploaded to S3 simultaneously when List S3 is in progress. onTrigger--> maxTimestamp is initiated as 0L. This is clearing keys as per the code below When

Re: Penalized FlowFiles still cause Processor Invocations

Yep probably best. If your processor and its typical usage context could be susceptible to having a connection of only penalized flowfiles in front then if the session.get() call returns null then for that case a call to yield would be nice. We should also do something so you don't have to :)

Re: Penalized FlowFiles still cause Processor Invocations

Thanks. We'll keep an eye on that ticket. In the meantime, I think we'll probably manually yield the processors to save system resources. _ [1496944291439_image001.png] Oleksi Derkatch |

Re: Penalized FlowFiles still cause Processor Invocations

This behavior is known and there is an open JIRA ticket [1] for it. It's not great for the processor's onTrigger() to be continually called without a flowfile, but it's also not a great user experience to do nothing and show 0 tasks executed, which leaves the end user with no idea why the

Re: Penalized FlowFiles still cause Processor Invocations

Hello, Does your processor happen to have a @TriggerWhenEmpty annotation on it? That would cause it to always execute regardless of what is in the queue, so just wanted to rule that out. Thanks, Bryan On Fri, Dec 22, 2017 at 12:45 PM, Oleksi Derkatch wrote: >

Penalized FlowFiles still cause Processor Invocations

Hi, I've noticed that if the every FlowFile in a queue is penalized, I see constant invocations on the processor's onTrigger() method, despite the queue being "effectively" empty. This seems to cause millions of invocations of the processor that don't result in useful work. Am I