[
https://issues.apache.org/jira/browse/NIFI-8636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kartik Mishra updated NIFI-8636:
--------------------------------
Description:
There is a requirement where we need to read the messages from a Kafka Topic
and push to other systems. So far I was using *Timer Driven scheduling with Run
Schedule of 0 sec, and everything worked fine.* Now when *I tried setting Run
Schedule of 60 sec, it stopped working for some reason. Same issue with CRON
Driven scheduling also.*
was:
There is a requirement where we need to read the messages from a Kafka Topic
and push to other systems. So far I was using TIMER_DRIVEN scheduling and
everything worked fine. Recently we moved to CRON_DRIVEN scheduling and we came
to know that ConsumeKafka_2_0 doesn't adhere to CRON scheduling and starts
randomly.
Offset Reset -> Latest
Scheduling Strategy -> CRON Driven
Run Duration -> 0 0/1 * 1/1 * ? *
> ConsumeKafka doesn't adhere the CRON driven and Timer Driven scheduling and
> starts randomly
> -------------------------------------------------------------------------------------------
>
> Key: NIFI-8636
> URL: https://issues.apache.org/jira/browse/NIFI-8636
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.13.2
> Reporter: Kartik Mishra
> Priority: Major
> Labels: consumekafka, nifi
>
> There is a requirement where we need to read the messages from a Kafka Topic
> and push to other systems. So far I was using *Timer Driven scheduling with
> Run Schedule of 0 sec, and everything worked fine.* Now when *I tried setting
> Run Schedule of 60 sec, it stopped working for some reason. Same issue with
> CRON Driven scheduling also.*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
