[DISCUSS] Flink Kubernetes Operator cleanup procedure

Hi devs, I would like to enquire about the cleanup procedure upon FlinkSessionJob deletion. Currently, FlinkSessionJobController would trigger a cleanup in the SessionJobReconciler which in turn cancels the Flink Job. Link to code: https://github.com/apache/flink-kubernetes-operator/blob/371a2

Re: [VOTE] Externalize AWS formats to flink-connector-aws

+1 (non-binding) Thanks Hong for driving this. Regards, Daren On 30/01/2023, 09:32, "Samrat Deb" wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. +1 (non-b

[jira] (FLINK-24343) Revisit Scheduler and Coordinator Startup Procedure

Dear FLINK community, I am looking at JIRA FLINK-24343 and I am trying to understand what this sentence means: “The scheduler must be started to the point that it can handle "failGlobal()" calls, because the coordinators might trigger that during their startup when an exception in "start()" occ

Re: [DISCUSS] Add new JobStatus fields to Flink Kubernetes Operator CRD

good argument for getting something done in Flink. Best regards, Martijn Op di 12 jul. 2022 om 21:17 schreef WONG, DAREN : > Hi Yang, > > The requirement to add *plan* currently originates from an internal AWS > requirement as our service needs

Re: [DISCUSS] Add new JobStatus fields to Flink Kubernetes Operator CRD

ne to have a second API call once directly after application > submission (technically even this can be eliminated by setting a fix job id > always). > > +1 from me. > > Cheers, > Gyula > > > On Tue, Jul 12, 2022 a

Re: [DISCUSS] Add new JobStatus fields to Flink Kubernetes Operator CRD

the https://nightlies.apache.org/flink/flink-docs-master/docs/ops/rest_api/#jobs-jobid after the previous call for every job in every reconcile loop would be too expensive. Best, Matyas On Mon, Jul 11, 2022 at 3:17 PM WONG, DAREN wrote: > Hi everyone, I am

[DISCUSS] Add new JobStatus fields to Flink Kubernetes Operator CRD

Hi everyone, I am Daren from AWS Kinesis Data Analytics (KDA) team. I had a quick chat with Gyula as I propose to include a few additional fields in the jobStatus CRD for Flink Kubernetes Operator such as: - endTime - duration - jobPlan Further details of each states can be found here