e developer's
> guide is
> >> > silent. I don't see how that slider is enforced in the processor
> code. It
> >> > seems that once the framework has ceded control to the processor it
> can
> >> run
> >> > for as long as it wants. So more information about thi
gt; >> higher throughput with micro-batching (but lesser control). In short,
> you
> >> can't expect to rollback a message and not affect the whole batch.
> >>
> >> However, if you 'commit' this batch as received by your processor, and
> >> t
cessor it can
>> run
>> > for as long as it wants. So more information about this would be great.
>> >
>> > Thanks again for the response. The information is always useful and
>> > enlighting.
>> > Devin
>> >
>> > On Tue, Mar 15,
But then, why?
>>
>> In general, one should leverage NiFi 'Scheduling' tab and have the
>> micro-batching aspect controlled via the framework. Unless you really
>> really have a very good reason to do it yourself.
>>
>> Hope this helps,
>> Andrew
>
k. Unless you really
> really have a very good reason to do it yourself.
>
> Hope this helps,
> Andrew
>
>
>
>
> On 3/7/16, 5:00 PM, "Devin Fisher"
> wrote:
>
> >Question about rollbacks. I have a processor that is grabbing a list of
> >FlowF
cro-batching aspect controlled via the framework. Unless you really really
have a very good reason to do it yourself.
Hope this helps,
Andrew
On 3/7/16, 5:00 PM, "Devin Fisher" wrote:
>Question about rollbacks. I have a processor that is grabbing a list of
>FlowFiles from se
Question about rollbacks. I have a processor that is grabbing a list of
FlowFiles from session.get(100). It will then process each flow file one at
a time. I want to then be able if there is an error with a single FlowFile
to roll it back (and only this failed FlowFile) and transfer it to the
