[
https://issues.apache.org/jira/browse/NIFI-10081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572072#comment-17572072
]
Joe Witt commented on NIFI-10081:
---------------------------------
For a case where a specific time/time interval is the desire in terms of
batching I dont know that we make that easy. This is biased toward a
continuous stream of input whereby some various features dictate when it is
time to kick off a merged result.
We should arguably block the usage of cron scheduling for this processor at
least as it is written OR we need to update its behavior to be more appropriate
in the case of cron scheduling.
I'd be curious to hear what others think who are familiar with this thing. We
might need to create a time biased MergeContent and MergeRecord....to make
handling such cases easier to reason over.
> MergeContent processor is not executed when Scheduling Strategy is set to
> Cron Driven.
> --------------------------------------------------------------------------------------
>
> Key: NIFI-10081
> URL: https://issues.apache.org/jira/browse/NIFI-10081
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.16.1, 1.16.2
> Environment: RHEL 7.9, Linux 3.10.0-1160.21.1.el7.x86_64
> java version "1.8.0_331"
> Java(TM) SE Runtime Environment (build 1.8.0_331-b09)
> Java HotSpot(TM) 64-Bit Server VM (build 25.331-b09, mixed mode)
> Intel(R) Xeon(R) Silver 4110 CPU @ 2.10GHz
> 6 cores
> Reporter: Angel Oropeza
> Priority: Minor
> Labels: crondriven, merge-content, scheduling
> Attachments: image-2022-06-01-22-22-32-958.png,
> image-2022-06-01-22-33-10-811.png, image-2022-06-01-22-33-47-519.png
>
>
> I was able to replicate my problem using the following configuration:
> !image-2022-06-01-22-22-32-958.png!
> The MergeContent configuration is as follows
> !image-2022-06-01-22-33-10-811.png!
> !image-2022-06-01-22-33-47-519.png!
> Although the conditions of the MergeContent processor are met, it does not
> concatenate the incoming flowfiles.
> The last version in which the above flow worked was version 1.15.3.
> Any suggestions on how to solve this? Is this a bug?
> P.S.: The flow is so designed due to a dependency on only writing one file
> per day.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
