Thanks Congxian for your references. Mans
On Wednesday, November 27, 2019, 07:12:57 AM EST, Congxian Qiu
wrote:
Hi,
As the doc[1] said we should assign uid to all the stateful operators. If you
do not set uid for an operator, Flink will generate an operatorId for it,
AFAIK,
Hi,
As the doc[1] said we should assign uid to all the stateful operators. If
you do not set uid for an operator, Flink will generate an operatorId for
it, AFAIK, operatorId will not change as far as the job DAG does not change.
you can skip the operator's state which is not in the new job,
Hi Kostas/Congxian:
Thanks fo your response.
Based on your feedback, I found that I had missed adding uid to one of the
stateful operators and correcting that resolved the issue. I still have
stateless operators which I have no uid specified in the application.
So, I thought that adding uid
Hi
The problem is that the specified uid did not in the new job.
1. As far as I know, the answer is yes. There are some operators have their
own state(such as window state), could you please share the minimal code of
your job?
2.*truely* stateless operator do not need to have uid, but for the
As a side note, I am assuming that you are using the same Flink Job
before and after the savepoint and the same Flink version.
Am I correct?
Cheers,
Kostas
On Mon, Nov 25, 2019 at 2:40 PM Kostas Kloudas wrote:
>
> Hi Singh,
>
> This behaviour is strange.
> One thing I can recommend to see if
Hi Singh,
This behaviour is strange.
One thing I can recommend to see if the two jobs are identical is to
launch also the second job without a savepoint,
just start from scratch, and simply look at the web interface to see
if everything is there.
Also could you please provide some code from your
Hey Folks:
Please let me know how to resolve this issue since using
--allowNonRestoredState without knowing if any state will be lost seems risky.
ThanksOn Friday, November 22, 2019, 02:55:09 PM EST, M Singh
wrote:
Hi:
I have a flink application in which some of the operators have
Hi:
I have a flink application in which some of the operators have uid and name and
some stateless ones don't.
I've taken a save point and tried to start another instance of the application
from a savepoint - I get the following exception which indicates that the
operator is not available to
