Hi Arvid,
Thanks a lot.
Will check Airflow and Cron-job options.
Regards,Sunitha.
On Monday, September 14, 2020, 05:23:43 PM GMT+5:30, Arvid Heise
wrote:
Hi Sunitha,
oozie is a valid approach, but I'd recommend to evaluate Airflow first [1].
It's much better maintained and easier to us
Hi Sunitha,
oozie is a valid approach, but I'd recommend to evaluate Airflow first [1].
It's much better maintained and easier to use.
Both tools are more used to compose complex workflows though. If you just
need a repeated execution, I'd go with cron jobs. For example, you can
completely rely o
Hi Sunitha,
(Note: You've emailed both the dev@ and user@ mailing list. Please only use
the user@ mailing list for questions on how to use Flink. I'm moving the
dev@ list to bcc)
Flink does not have facilities for scheduling batch jobs, and there are no
plans to add such a feature (this is not in
Hi Team,
We have Flink Batch Jobs which needs to be scheduled as listed below:Case 1 :
2.00 UTC time dailyCase 2 : Periodically 2 hours onceCase 3: Schedule
based on an event
Request you to help me on this, How to approach all the 3 use cases. Can we
use Oozie workflows or any better
