[ https://issues.apache.org/jira/browse/FLINK-10265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610819#comment-16610819 ]
vinoyang commented on FLINK-10265: ---------------------------------- hi [~twalthr] Sorry to reply a bit late, because I am processing multiple issues in parallel. I think descriptor and validator are necessary. According to the existing pattern, these properties should belong to the "*execution*" configuration section. But considering properties like checkpoint, they can only be applied in one context. Do we need to provide a way to make the configuration more friendly to user. For example, we consider the configuration under the "*execution*" section as _ExecutionConfig_ in the API. Can we define a "*streaming*" section or a "*batch*" section to distinguish between specific types of configurations, or prefix the specific properties under the "*execution*" section with "*streaming.*" and "*batch.*", such as "streaming.enable-checkpointing"? > Configure checkpointing behavior for SQL Client > ----------------------------------------------- > > Key: FLINK-10265 > URL: https://issues.apache.org/jira/browse/FLINK-10265 > Project: Flink > Issue Type: New Feature > Components: SQL Client > Reporter: Timo Walther > Assignee: vinoyang > Priority: Major > > The SQL Client environment file should expose checkpointing related > properties: > - enable checkpointing > - checkpointing interval > - mode > - timeout > - etc. see {{org.apache.flink.streaming.api.environment.CheckpointConfig}} > Per-job selection of state backends and their configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)