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

Flink Jira Bot updated FLINK-30459:
-----------------------------------
    Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it.


> SQL Client supports "SET 'property'"
> ------------------------------------
>
>                 Key: FLINK-30459
>                 URL: https://issues.apache.org/jira/browse/FLINK-30459
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Client
>    Affects Versions: 1.16.0
>            Reporter: Mingliang Liu
>            Assignee: Mingliang Liu
>            Priority: Major
>              Labels: pull-request-available, stale-assigned
>
> Currently the SET command in SQL client has two syntax:
> - {{SET;}} for listing all config properties
> - {{SET 'key'='value'}} for setting a property with (new) value
> As in Spark SQL and Flink SQL with Hive dialect, it would be convenient to 
> show one config property using the syntax {{SET 'key';}}. Without this, users 
> will need to find the very one config from all config properties.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to