[jira] [Created] (FLINK-36029) Add @Nullable Annotation to ValueState's Value Method Return Type

LEE SOMANG created FLINK-36029: -- Summary: Add @Nullable Annotation to ValueState's Value Method Return Type Key: FLINK-36029 URL: https://issues.apache.org/jira/browse/FLINK-36029 Project: Flink

[jira] [Created] (FLINK-36028) Doc: kafka source additional properties

Rich created FLINK-36028: Summary: Doc: kafka source additional properties Key: FLINK-36028 URL: https://issues.apache.org/jira/browse/FLINK-36028 Project: Flink Issue Type: Improvement Com

[DISCUSS] re-open FLINK-28842 Add client.id.prefix for the KafkaSink

Hi all, I'm reaching out to you about FLINK-28842 . We've encountered the `javax.management.InstanceAlreadyExistsException` in production, and I believe resolving this issue could mitigate the problem. I've prepared a fix in a private fork that h

[jira] [Created] (FLINK-36027) [cdc-connector][MySQL] added metrics numRecordsOut for each OperationType(update, delete, insert)

Lee SeungMin created FLINK-36027: Summary: [cdc-connector][MySQL] added metrics numRecordsOut for each OperationType(update, delete, insert) Key: FLINK-36027 URL: https://issues.apache.org/jira/browse/FLINK-36027

Re: [DISCUSS] FLIP-474: Store operator name and UID in state metadata

Hi Gabor, I apologize for any confusion. Let me clarify my position. The concept of state observability is important for users, and the current FLIP seems to be a step in the right direction. However, before we proceed, I suggest we discuss the final presentation of the state observability to the

Re: Rebuilding flink

The cluster will only be refreshed if you rebuild the module with changes and "flink-dist". So in this particular case: $ mvn clean install -DskipTests -Dfast -pl flink-runtime,flink-dist -am If you have a fairly fresh SNAPSHOT build already in your local maven repo, then "-am" can be omitted and