You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
flink-jdbc-driver does not support connection properties currently. Thus, SessionClient connected to flink-sql-gateway cannot change Environment at session level.
For example, In my senario, I deployed a flink sql gateway , I use beeline to connect it and submit flink sql query. The query always submit to that one Flink Cluster based on flink-sql-gateway's configuration. The execution configuration like time-characteristic/max-parallelism cannot change as well. This is tremendous inconvenience.
I looked through flink-sql-gateway code. Actually it support overriding deployment/execution/tableconfig params at session level.
submitting to a yarn-session flink cluster: !connect jdbc:flink://localhost:8083?planner=blink&deployment.executor=yarn-session&deployment.yid=application_1574648431818_877975
submitting query for yarn-per-job mode: !connect jdbc:flink://localhost:8083?planner=blink&deployment.executor=yarn-per-job
The text was updated successfully, but these errors were encountered:
Hi,
flink-jdbc-driver does not support connection properties currently. Thus, SessionClient connected to flink-sql-gateway cannot change Environment at session level.
For example, In my senario, I deployed a flink sql gateway , I use beeline to connect it and submit flink sql query. The query always submit to that one Flink Cluster based on flink-sql-gateway's configuration. The execution configuration like time-characteristic/max-parallelism cannot change as well. This is tremendous inconvenience.
I looked through flink-sql-gateway code. Actually it support overriding deployment/execution/tableconfig params at session level.
POST http://localhost:8083/v1/sessions
{ "planner":"blink", "properties": { "deployment.jobmanager":"helloflinkonk8s.test.rest.shbt2.k8s.flink.ads.qihoo.net:80", "execution.parallelism": 1000, "execution.max-parallelism": 1000 } }
Then, I looked through flink-jdbc-drive code. It just ignore connection properties. I improved it, and now it works. I'm using beeline :
!connect jdbc:flink://localhost:8083?planner=blink&deployment.jobmanager=helloflinkonk8s.ultron:8081&execution.max-parallelism=1000
submitting to a yarn-session flink cluster:
!connect jdbc:flink://localhost:8083?planner=blink&deployment.executor=yarn-session&deployment.yid=application_1574648431818_877975
submitting query for yarn-per-job mode:
!connect jdbc:flink://localhost:8083?planner=blink&deployment.executor=yarn-per-job
The text was updated successfully, but these errors were encountered: