[
https://issues.apache.org/jira/browse/FLINK-28163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576580#comment-17576580
]
Wencong Liu commented on FLINK-28163:
-------------------------------------
Compared with the description of the statement api in [FLIP-91: Support SQL
Gateway - Apache Flink - Apache Software
Foundation|https://cwiki.apache.org/confluence/display/FLINK/FLIP-91%3A+Support+SQL+Gateway]],
I have made the following modifications in the specific implementation:
*1. Execute a statement*
*1.1* The request body of the API will contain an object of type Map<String,
String>, which will be converted to a Configuration and passed to the
corresponding Operation. The json string converted from the request body will
be like following:
{code:java}
{
"statement": "",
"executionTimeout": ""
"executionConfig":{
"k1" : "v1",
"k2" : "v2"
}
}
{code}
*1.2* The has_result attribute in the response body will be removed. The json
string converted from response body will be like following:
{code:java}
{
"operation_handle": "xxxxxxxxxx",
"operation_type": "EXECUTE_STATEMNT",
}
{code}
*2. Fetch results*
The field {{next_result_uri}} will be null if there is no more data. And there
will be no field {{exception}}.
> Introduce the statement related API for REST endpoint
> -----------------------------------------------------
>
> Key: FLINK-28163
> URL: https://issues.apache.org/jira/browse/FLINK-28163
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Gateway
> Affects Versions: 1.16.0
> Reporter: Shengkai Fang
> Assignee: Wencong Liu
> Priority: Major
>
> It includes executeStatement, fetchResults API in the FLIP-91.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
