I think configuration "pipeline.jars" [1] works for you, because SQL Client
supports --jars to load user jars and it also uses this option internally.
But I'm not expert on this, maybe Kostas and Aljoscha can give
a definitive answer.
Best,
Jark
[1]:
https://ci.apache.org/projects/flink/flink-docs-master/ops/config.html#pipeline-jarsOn Wed, 11 Dec 2019 at 15:41, Jingsong Li <
[hidden email]> wrote:
> Hi Leo,
>
> I think run job with external jars is important too.
> Have you took a look to PipelineOptions.JARS in configuration?
> I think this is a way to set external jars. And SQL-CLI need it too.
>
> Best,
> Jingsong Lee
>
> On Wed, Dec 11, 2019 at 9:18 AM 50man <
[hidden email]> wrote:
>
> > Hi everyone,
> >
> >
> > I propose an important API feature to register user jar files in
> > {Stream}ExecutionEnvironment.
> >
> > The proposal is here,
> >
> >
https://issues.apache.org/jira/browse/FLINK-14319> >
> > Let's discuss it and I hope we can acquire a consent ASAP cause this
> > feature is potentially helpful for some release issues about version
> > 1.10 on sub-task FLINK-14055
> > <
https://issues.apache.org/jira/browse/FLINK-14055> under task
> > FLINK-10232 <
https://issues.apache.org/jira/browse/FLINK-10232> ;-).
> >
> >
> > Best,
> >
> > Leo
> >
> >
>
> --
> Best, Jingsong Lee
>