You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jing Zhang (JIRA)" <ji...@apache.org> on 2019/07/23 03:33:00 UTC
[jira] [Commented] (FLINK-13375) Move ExecutionConfigOptions and
OptimizerConfigOptions to table-api
[ https://issues.apache.org/jira/browse/FLINK-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890646#comment-16890646 ]
Jing Zhang commented on FLINK-13375:
------------------------------------
Good proposal. It's better to create `TableConfigOptions` in table-api, and move field in `TableConfig` to `TableConfigOptions`.
> Move ExecutionConfigOptions and OptimizerConfigOptions to table-api
> -------------------------------------------------------------------
>
> Key: FLINK-13375
> URL: https://issues.apache.org/jira/browse/FLINK-13375
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: Jark Wu
> Priority: Major
> Fix For: 1.9.0, 1.10.0
>
>
> Move ExecutionConfigOptions and OptimizerConfigOptions to table-api.
> We should also go through every config options in detail in this issue. Because we are now moving it to the API module. We should actually discuss how the properties are named and make sure that those options follow Flink naming conventions.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)