[
https://issues.apache.org/jira/browse/FLINK-14851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986874#comment-16986874
]
Kostas Kloudas commented on FLINK-14851:
----------------------------------------
Well you are right [~tison] that this is a change in the behaviour in some
cases, and we are actually contemplating on if we should add a "compatibility
mode" where in the per-job mode, a session cluster is going to be created and
then the job is going to be submitted as before.
Personally, I am a bit torn on if this "compatibility mode" is necessary. But I
have to think about it a bit more to figure out potential user-facing changes.
Do you have some in your mind?
Some changes that I can find are:
1) If job submission fails, before the user was getting back an exception, now
not.
2) Before you had a multi-\{{execute()}} job, they would all share the same
cluster, now each one will have a different cluster.
> Make the (Stream)ContextEnvironment use the Executors
> -----------------------------------------------------
>
> Key: FLINK-14851
> URL: https://issues.apache.org/jira/browse/FLINK-14851
> Project: Flink
> Issue Type: Sub-task
> Components: Client / Job Submission
> Affects Versions: 1.10.0
> Reporter: Kostas Kloudas
> Assignee: Kostas Kloudas
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
