Stephan, not sure what you mean by this exactly... But I guess, this a
an "add-on" that can be done later. Seems to be related to
https://issues.apache.org/jira/browse/FLINK-1929
I will open a JIRA for the new "terminate" message and assign it to myself.
-Matthias
On 05/27/2015 12:36 PM, Stepha
+1 for the second option.
How about we allow to pass a flag that indicates whether a checkpoint
should be taken together with the canceling?
On Wed, May 27, 2015 at 12:27 PM, Aljoscha Krettek
wrote:
> I would also prefer the second option. The first is rather a hack but not
> an option. :D
> O
I would also prefer the second option. The first is rather a hack but not
an option. :D
On May 27, 2015 9:14 AM, "Márton Balassi" wrote:
> +1 for the second option:
>
> It would also provide possibility to properly commit a state checkpoint
> after the terminate message was triggered. In some cas
+1 for the second option:
It would also provide possibility to properly commit a state checkpoint
after the terminate message was triggered. In some cases this can be a
desirable behaviour.
On Wed, May 27, 2015 at 8:46 AM, Gyula Fóra wrote:
> Hey,
>
> I would also strongly prefer the second opt
Hey,
I would also strongly prefer the second option, users need to have the
option to force cancel a program in case of something unwanted behaviour.
Cheers,
Gyula
Matthias J. Sax ezt írta (időpont: 2015.
máj. 27., Sze, 1:20):
> Hi,
>
> currently, the only way to stop a streaming job is to "ca
Hi,
currently, the only way to stop a streaming job is to "cancel" the job,
This has multiple disadvantage:
1) a "clean" stopping is not possible (see
https://issues.apache.org/jira/browse/FLINK-1929 -- I think a clean stop
is a pre-requirement for FLINK-1929) and
2) as a minor issue, all cancel
