ammu20-dev commented on code in PR #26378: URL: https://github.com/apache/flink/pull/26378#discussion_r2044462396
########## docs/content/docs/dev/table/sql-gateway/overview.md: ########## @@ -84,6 +84,14 @@ $ curl --request POST http://localhost:8083/v1/sessions/${sessionHandle}/stateme The `operationHandle` in the return results is used by the SQL Gateway to uniquely identify the submitted SQL. +The Flink SQL Gateway allows clients to specify which Flink cluster to submit jobs to, enabling remote execution of SQL statements and facilitating easier interaction with Flink clusters through a REST API. Enrich the POST request body with `executionConfig` variable to set the Flink cluster address. For example: Review Comment: The request body part of Gateway REST [/sessions/:session_handle/statements](https://nightlies.apache.org/flink/flink-docs-release-2.0/docs/dev/table/sql-gateway/rest/#sessions-session_handle-statements-1) api contains an executionConfig variable which can be used to override the default configuration. I have mentioned the same here in the doc. > Also we should mention in the text why/when you would want to specify a non-default jm endpoint for the gateway. The statement `The Flink SQL Gateway allows clients to specify which Flink cluster to submit jobs to, enabling remote execution of SQL statements and facilitating easier interaction with Flink clusters through a REST API.` mentions about the possibility of using the gateway to submit jobs to a remote cluster. I hope this would be sufficient to convey the why/when part. > I think the parameters in the example should be parameterized i.e. {port} and then explain what port is. As is I support port will fail as it is not a number. Done through https://github.com/apache/flink/pull/26378/commits/70b67d6d456ca3ba8e212545242c9337901f5a69 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
