Hi, IMO, both the SQL Client and the Restful API can provide connections to the SQL Gateway service for submitting jobs. A slight difference is that the SQL Client also offers a command-line visual interface for users to view results. In your production scenes, placing the SQL to be submitted into a file and then using the '-f' command in SQL Client to submit the file sounds a bit roundabout. You can just use the Restful API to submit them directly?
-- Best! Xuyang At 2024-03-07 04:11:01, "Robin Moffatt via user" <user@flink.apache.org> wrote: I'm reading the deployment guide[1] and wanted to check my understanding. For deploying a SQL job into production, would the pattern be to write the SQL in a file that's under source control, and pass that file as an argument to SQL Client with -f argument (as in this docs example[2])? Or script a call to the SQL Gateway's REST API? Are there pros and cons to each approach? thanks, Robin [1]: https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/deployment/overview/ [2]: https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/dev/table/sqlclient/#execute-sql-files