You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Seth Wiesman (JIRA)" <ji...@apache.org> on 2019/02/18 19:08:00 UTC

[jira] [Updated] (FLINK-11653) Add configuration to enforce custom UID's on datastream

     [ https://issues.apache.org/jira/browse/FLINK-11653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Seth Wiesman updated FLINK-11653:
---------------------------------
    Component/s:     (was: DataStream API)
                 Job-Submission

> Add configuration to enforce custom UID's on datastream
> -------------------------------------------------------
>
>                 Key: FLINK-11653
>                 URL: https://issues.apache.org/jira/browse/FLINK-11653
>             Project: Flink
>          Issue Type: Improvement
>          Components: Job-Submission
>            Reporter: Seth Wiesman
>            Assignee: Seth Wiesman
>            Priority: Minor
>
> 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.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)