Open a49a opened 2 years ago
The FlinkSQLEngine process life is inconsistent with Session. One FlinkSQLEngine process corresponds to multiple sessions. So flink-sql-engine.sh
can not use configuration of Session or ExecuteStatement.
The FlinkSQLEngine process life is inconsistent with Session. One FlinkSQLEngine process corresponds to multiple sessions. So
flink-sql-engine.sh
can not use configuration of Session or ExecuteStatement.
From Flink document, Flink support ADD JAR
and REMOVE JAR
commands, what's the difference between use ADD JAR
and inject jars on launching Flink engine?
The
kyuuubi-default.conf
options like the following.flink.client.option.jar foo.jar flink.client.option.library /foo/bar
Give some comments based on my little understand of Flink, please correct me if I'm wrong.
There is no equality configuration in Flink of --jar
and --library
options defined by Flink CLI, if yes we'd better to introduce Kyuubi's style configurations instead of Flink's style to avoid potential conflict, e.g.
kyuubi.session.engine.flink.jar
kyuubi.session.engine.flink.library
BTW, I think we can modify this line to support overwriting Flink configuration by flink-sql-engine.sh
, then we can achieve same experience like Spark engine, which means we can define Flink confs in JDBC URL, kyuubi-defaults.conf
, flink-conf.yaml
, and the former has higher priority.
BTW, I think we can modify this line to support overwriting Flink configuration by
flink-sql-engine.sh
, then we can achieve same experience like Spark engine, which means we can define Flink confs in JDBC URL,kyuubi-defaults.conf
,flink-conf.yaml
, and the former has higher priority.
I spilled a new issue, I will achieve this first.
The
kyuuubi-default.conf
options like the following.flink.client.option.jar foo.jar flink.client.option.library /foo/bar
Give some comments based on my little understand of Flink, please correct me if I'm wrong.
There is no equality configuration in Flink of
--jar
and--library
options defined by Flink CLI, if yes we'd better to introduce Kyuubi's style configurations instead of Flink's style to avoid potential conflict, e.g.kyuubi.session.engine.flink.jar kyuubi.session.engine.flink.library
I second with introducing Kyuubi's style configurations, but this has nothing to do with session.
Could we design prefix is kyuubi.engine.flink.
?
kyuubi.engine.flink.jar
kyuubi.engine.flink.library
Code of Conduct
Search before asking
What would you like to be improved?
The following issue only achieves
FlinkSQLEngine
process, but users have no way to set--jar
and--library
options in Kyuubi. We should achieve this inKyuubiServer
process too.https://github.com/apache/incubator-kyuubi/issues/1685 https://github.com/SteNicholas/incubator-kyuubi/commit/dd5a704342334feb24eae981d184943f618dd228
We can put
--jar
and--library
options inkyuuubi-default.conf
, andKyuubiServer
process load these options.How should we improve?
KyuubiServer
process loads the FlinkSQL Client startup options
inkyuuubi-default.conf
. And thenKyuubiServer
transforms the options to standard FlinkSQL Client startup options
and passes them toflink-sql-engine.sh
when theflink-sql-engine.sh
process will be started.The
kyuuubi-default.conf
options like the following.Now
flink-sql-engine.sh
startup options are nothing, so users can't set any options.Are you willing to submit PR?