[
https://issues.apache.org/jira/browse/FLINK-13521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu updated FLINK-13521:
----------------------------
Description:
Currently, we provide a set of configurations in blink planner to support
optimization or enable some advanced feature. However, all the configurations
can't be set in SQL CLI.
It would be great to allow set configurations in SQL CLI via {{SET}} command.
This maybe a new feature, but considering the implementation effort is rather
low (pass configurations to TableConfig), I would like to add it to 1.9 too,
but I won't set it as blocker.
For example:
{code:sql}
SET table.exec.mini-batch.enabled = true;
SET table.exec.mini-batch.allow-latency = 5s;
{code}
Meanwhile, we may also need to add an entry in yaml file:
{code}
config:
table.exec.mini-batch.enabled: true
table.exec.mini-batch.allow-latency: 5s
{code}
was:
Currently, we provide a set of configurations in blink planner to support
optimization or enable some advanced feature. However, all the configurations
can't be set in SQL CLI.
It would be great to allow set configurations in SQL CLI via {{SET}} command.
This maybe a new feature, but considering the implementation effort is rather
low (pass configurations to TableConfig), I would like to add it to 1.9 too,
but I won't set it as blocker.
> Allow set configuration in SQL CLI
> ----------------------------------
>
> Key: FLINK-13521
> URL: https://issues.apache.org/jira/browse/FLINK-13521
> Project: Flink
> Issue Type: Task
> Components: Table SQL / Client
> Reporter: Jark Wu
> Assignee: Caizhi Weng
> Priority: Major
> Fix For: 1.9.0, 1.10.0
>
>
> Currently, we provide a set of configurations in blink planner to support
> optimization or enable some advanced feature. However, all the configurations
> can't be set in SQL CLI.
> It would be great to allow set configurations in SQL CLI via {{SET}} command.
> This maybe a new feature, but considering the implementation effort is rather
> low (pass configurations to TableConfig), I would like to add it to 1.9 too,
> but I won't set it as blocker.
> For example:
> {code:sql}
> SET table.exec.mini-batch.enabled = true;
> SET table.exec.mini-batch.allow-latency = 5s;
> {code}
> Meanwhile, we may also need to add an entry in yaml file:
> {code}
> config:
> table.exec.mini-batch.enabled: true
> table.exec.mini-batch.allow-latency: 5s
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
