You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2023/03/01 19:10:00 UTC

[jira] [Updated] (NIFI-11157) Doc: Update docs usage for MergeContent and MergeRecord to use Timer Driven as default scheduling strategy

     [ https://issues.apache.org/jira/browse/NIFI-11157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard updated NIFI-11157:
----------------------------------
    Status: Patch Available  (was: Open)

> 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.18.0, 1.16.0
>            Reporter: CHANDAN KUMAR
>            Assignee: Pierre Villard
>            Priority: Major
>
> 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)