[
https://issues.apache.org/jira/browse/FLINK-28777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574184#comment-17574184
]
Xintong Song edited comment on FLINK-28777 at 8/2/22 11:16 AM:
---------------------------------------------------------------
[~martijnvisser],
I think this is exactly an outcome of following the time-based release plan.
SQL Gateway supports various clients: sql client, rest, hiveserver2, etc. Given
the 1.16 feature freeze date, we won't be able to finish all the endpoints.
Thus, we'd exclude one of the rest apis (tracked by this ticket) from
FLINK-28161, which is only needed by the sql client, and still try to complete
the remaining of them.
In other words, we'd expect the sql gateway to support rest & hiveserver2 apis
in 1.16, and sql client in 1.17.
was (Author: xintongsong):
[~martijnvisser],
I think this is exactly an outcome of following the time-based release plan.
SQL Gateway supports various clients: sql client, rest, hiveserver2, etc. Given
the 1.16 feature freeze date, we won't be able to finish all the endpoints.
Thus, we'd exclude one of the rest apis (tracked by this ticket) from
FLINK-28161, which is only needed by the sql client, and still try to complete
the remaining of them.
> Add configure session API for sql gateway rest endpoint
> -------------------------------------------------------
>
> Key: FLINK-28777
> URL: https://issues.apache.org/jira/browse/FLINK-28777
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Gateway
> Reporter: Wencong Liu
> Priority: Major
> Fix For: 1.17.0
>
>
> In the development of version 1.16, we will temporarily skip the development
> of configure session api in sql gateway rest endpoint. Considering the
> workload and sql gateway temporarily does not need to be compatible with sql
> client, so the relevant development work will be carried out in the
> development work of version 1.17.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
