One last question..
Can you conform that the "This will be available in 1.5 where we rework the
client-cluster communication to go entirely through the REST API." comment
, ches...@apache.org ?
On Mon, Dec 11, 2017 at 4:54 AM, Chesnay Schepler
wrote:
> This doesn't sound
This doesn't sound like proper behavior, could you provide instructions
on how to reproduce this?
On 07.12.2017 13:42, Lasse Nedergaard wrote:
I hope it can be put in 1.4.1.
I have one concern about the rest api. We running 1.3.1 on dc/os and
if we apply parameters as arguments and in our
We are currently voting on the third release candidate for 1.4.0.
Feel free to propose this feature on the dev mailing list [1], but I don't
think this will result in cancelling the vote.
If we identify a blocking issue for 1.4.0, it could be included as well.
But we're already a few weeks behind
Could that be put into 1.4 release ? This significantly eases tooling
around savepoints and though a minor change it is not intrusive or should
cause regression.. thank you though...
On Dec 7, 2017 3:51 AM, "Chesnay Schepler" wrote:
> I've finished the implementation. I
I hope it can be put in 1.4.1.
I have one concern about the rest api. We running 1.3.1 on dc/os and if we
apply parameters as arguments and in our code validate these parameters and
throw an exception during startup if something is wrong we see that all
uploaded jar disappear all running jobs
In retrospect I'm quite frustrated we didn't get around to implementing
this for 1.4.
The least-effort implementation would have required copying one class,
and modifying ~10 lines.
Doesn't get any more low-hanging than that.
On 07.12.2017 12:51, Chesnay Schepler wrote:
I've finished the
I've finished the implementation. I created 2 new branches in my
repository, for 1.3.2 and 1.4.
1.3.2: https://github.com/zentol/flink/tree/release-1.3.2-custom
1.4: https://github.com/zentol/flink/tree/release-1.4-custom
Triggering savepoints works exactly like cancel-with-savepoint, just
No, this is also not possible in 1.4.
This will be available in 1.5 where we rework the client-cluster
communication to go entirely through the REST API.
This will mean that everything you can do with the command-line client
can also be achieved directly through the REST API.
However, from
Hi.
It is not possible through REST in Flink 1.3.2 I’m looking for the feature. The
only option is to use ./Flink savepoint for now
Med venlig hilsen / Best regards
Lasse Nedergaard
> Den 6. dec. 2017 kl. 21.52 skrev Vishal Santoshi :
>
> I was more interested in
Hi Vishal,
Job cancellations can be done via a REST API:
https://ci.apache.org/projects/flink/flink-docs-release-1.3/monitoring/rest_api.html#cancel-job-with-savepoint
Thanks,
Vipul
On Wed, Dec 6, 2017 at 10:56 AM, Vishal Santoshi
wrote:
> One can submit jobs,
One can submit jobs, upload jars, kill jobs etc very strange that you can’t
do a save point ?
Or am I missing something obvious ?
Vishal
11 matches
Mail list logo