Hi Aleksandr Savonin, +1. That sounds reasonable to me.
Best, Yuepeng Pan Aleksandr Savonin <[email protected]> 于2026年6月2日周二 22:21写道： > Hi everyone, > gently pinging this thread to see if anyone has thoughts or concerns > regarding this proposal. > > On Wed, 27 May 2026 at 15:57, Aleksandr Savonin <[email protected]> > wrote: > > > > Hi everyone, > > > > I’d like to start a discussion about FLIP-583: Expose JobInfo on > > Source contexts [1]. > > Source connectors often need job metadata (job ID, job name) for > > authentication, distributed tracing, metrics labeling, and other > > usages. SinkV2 already exposes this via `InitContext.getJobInfo()`. > > > > The current workarounds on the source side (e.g. parsing the job ID > > from metric group variables) are brittle/fragile and undiscoverable. > > The FLIP adds a `@PublicEvolving` default method `getJobInfo()` to > > `SourceReaderContext` and `SplitEnumeratorContext`, following the same > > pattern as already established in these interfaces. The runtime > > implementations delegate to `StreamingRuntimeContext` (reader side) > > and `OperatorCoordinator.Context` (enumerator side). > > > > Looking forward to your feedback. > > > > [1] > https://cwiki.apache.org/confluence/display/FLINK/FLIP-583%3A+Expose+JobInfo+on+Source+contexts > > > > -- > > Kind regards, > > Aleksandr > > > > -- > Kind regards, > Aleksandr >
