Do you mean a new interface just like *ApplicationDeployer* for
flink-jar-application submission?
The *ApplicationDeployer*[1] interface has already been used in the
flink-kubernetes-operator project.
[1].
https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-operator/src
Hi Yang,
It would be better to have an interface to submitting application mode
jobs. It's a little tricky for SQL CLI/Gateway process to invoke a shell
script to submit jobs.
Best,
Jark
On Thu, 17 Feb 2022 at 15:20, Yang Wang wrote:
> I am not sure whether the sql script could also be submitt
I am not sure whether the sql script could also be submitted like python.
We will need a sql-runner jar, which plays as the user jar and has the sql
script as the argument.
./bin/flink run-application \ --target kubernetes-application \
-Dkubernetes.cluster-id= \
-Dkubernetes.container.ima
I think this mode is still limited and maybe not easy to extend.
Could the application mode provide an interface to execute?
So that clients can implement the interface and pass arbitrary parameters
(e.g. SQL scripts) ?
Best,
Jark
On Wed, 16 Feb 2022 at 18:54, Konstantin Knauf wrote:
> Hi Jark,
Hi Jark,
I think you are raising a very good point. I think we need an application
mode for SQL that would work along the lines of executing a SQL script
(incl. init scripts) located in a particular directory in the Docker Image.
Details to be discussed.
Do you think Zeppelin/SQL CLI could work w
Hi David,
Zeppelin and SQL CLI also support submitting long-running streaming SQL
jobs. So the session cluster is not a fit mode.
Best,
Jark
On Fri, 11 Feb 2022 at 22:42, David Morávek wrote:
> Hi Jark, can you please elaborate about the current need of the per-job
> mode for interactive clien
Hi Jark, can you please elaborate about the current need of the per-job
mode for interactive clients (eg. Zeppelin that you've mentioned)? Aren't
these a natural fit for the session cluster?
D.
On Fri, Feb 11, 2022 at 3:25 PM Jark Wu wrote:
> Hi Konstantin,
>
> I'm not very familiar with the im
Hi Konstantin,
I'm not very familiar with the implementation of per-job mode and
application mode.
But is there any instruction for users abou how to migrate platforms/jobs
to application mode?
IIUC, the biggest difference between the two modes is where the main()
method is executed.
However, SQL
Hi everyone,
Thank you for sharing your perspectives. I was not aware of
these limitations of per-job mode on YARN. It seems that there is a general
agreement to deprecate per-job mode and to drop it once the limitations
around YARN are resolved. I've started a corresponding vote in [1].
Thanks a
Hi Yang,
Thank you for the clarification. In general I think we will have time to
experiment with this until it will be removed totally and migrate our solution
to use application mode.
Regards,
F
On 2022/01/26 02:42:24 Yang Wang wrote:
> Hi all,
>
> I remember the application mode was initial
10 matches
Mail list logo
