ction applications
3. Deploy the upgraded application to pre-production environment with copy of
production inputs/outputs.
It should be running for more than one cycle, usually one day or one week.
4. Deploy it the production environment
Best,
Yang
Konstantinos Kallas
mailto:konstantino
their results to make sure that they are
consistent? Do you run a set of unit and integration tests and then
deploy if they all succeed? Do you have some other method?
Best regards,
Konstantinos Kallas
1 Oct 2019, at 04:18, Konstantinos Kallas
mailto:konstantinos.kal...@hotmail.com>> wrote:
Hi everyone.
I wanted to ask Flink users what are the most subtle Flink bugs that
people have witnessed. The cause of the bugs could be anything (e.g.
wrong assumptions on data, parallelism of non-paral
1 Oct 2019, at 04:18, Konstantinos Kallas
<mailto:konstantinos.kal...@hotmail.com> wrote:
Hi everyone.
I wanted to ask Flink users what are the most subtle Flink bugs that
people have witnessed. The cause of the bugs could be anything (e.g.
wrong assumptions on data, parallelism of non-parallel oper
would be
interesting to have examples of difficult to spot bugs to evaluate our
testing framework on.
Thanks,
Konstantinos Kallas
