For Flink job(created using SQL), This is evident with metrics from processing operators that the operator names used in these metrics are auto-generated by Flink and do not appear to be configurable.
Please suggest whether there is an existing solution or recommended approach in Flink to configure operator name(specially for processing operator) For Flink job(created using SQL)
if there are any items in the Flink backlog to support to configure operator name etc. for SQL-based jobs?
j
Jaehyeon Kim
07/16/2025, 7:51 PM
Are you looking for something like this?
Copy code
-- set the job name
SET 'pipeline.name' = 'SqlJob';
a
Avinesh Sachan
07/21/2025, 10:07 AM
Thank you for responding!!!
we dont want to configure job name as you suggested, we want a way to configure metrics name, which currently FLINK is deciding by it self for job created using FLINK SQL, Ex : Calc[60]. attaching a snap for more clarity.
j
Jaehyeon Kim
07/22/2025, 10:12 AM
Ah, I see. From memory, it is not possible. Even the name can change when we upgrade a Flink version.
π 1
a
Avinesh Sachan
07/22/2025, 11:51 AM
Thank you for confirming, I understood that Processing operator metric name like Calc are not configurable for FLINK SQL JOB. If my understanding correct then is there any future backlog to support it ?