[
https://issues.apache.org/jira/browse/NIFI-11157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696874#comment-17696874
]
ASF subversion and git services commented on NIFI-11157:
--------------------------------------------------------
Commit 169b53feaa50a1072ba793c215e0afb7330f0d6a in nifi's branch
refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=169b53feaa ]
NIFI-11157 - Doc update for scheduling strategy for MergeContent/Record
This closes #6999.
Signed-off-by: Peter Turcsanyi <[email protected]>
> Doc: Update docs usage for MergeContent and MergeRecord to use Timer Driven
> as default scheduling strategy
> -----------------------------------------------------------------------------------------------------------
>
> Key: NIFI-11157
> URL: https://issues.apache.org/jira/browse/NIFI-11157
> Project: Apache NiFi
> Issue Type: Improvement
> Components: NiFi Stateless
> Affects Versions: 1.16.0, 1.18.0
> Reporter: CHANDAN KUMAR
> Assignee: Pierre Villard
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With respect to the following Jira
> https://issues.apache.org/jira/browse/NIFI-9390 , now MergeContent or
> MergeRecord if scheduled to run as CRON Driven files are Not Merging, Issue
> reported at https://issues.apache.org/jira/browse/NIFI-10081.
> Since this is not a Bug but working as designed, Please add the following
> message in the processor description "The MergeContent/Record processor is
> not designed to be used in a CRON-Driven fashion. It should always be
> scheduled to run with a Timer-Driven Scheduling and a Run Schedule of "0
> sec". "
>
> Thank you
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
