[
https://issues.apache.org/jira/browse/NIFI-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798755#comment-17798755
]
Tan Luu commented on NIFI-12402:
--------------------------------
Yes, the expected behavior is to only trigger an inactive indicator after there
was activity after the processor had been started then no activity for
Threshold Duration. So the sequence of events is
Start the processor -> activity comes -> no activity for "Threshold Duration"
period
In the pull request, I add a configuration property to toogle the processor
behavior. It ensures backward compatibility
> MonitorActivity generates inactivity indicator after it is started and
> threshold duration exceeds without actual activities
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-12402
> URL: https://issues.apache.org/jira/browse/NIFI-12402
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.23.2
> Reporter: Tan Luu
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Even though there is no activity, a start or restart of MonitorActivity
> processor produces an inactive flowfile after "Threshold Duration". This
> behavior creates a false positive notification cause there was no actual
> activity. The expected behavior is to only send an inactive indicator if
> there is activity after the processor is started.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
