Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
Description
Current best practice when deploying Flink applications to production is to set a custom UID, using DataStream#uid, so jobs can resume from savepoints even if they job graph has been modified. Flink should contain a configuration that can allow users to fail submission if their program contains an operator without a custom UID; enforcing best practices similarly to #disableGenericTypes.
Attachments
Issue Links
- relates to
-
FLINK-14910 DisableAutoGeneratedUIDs fails on keyBy
- Closed
- links to