[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2018-04-03 Thread zentol
Github user zentol commented on the issue: https://github.com/apache/flink/pull/3117 @ShashwatRastogi-Reflektion I'm not entirely sure, but one thing you could try is to explicitly disable chaining (`StreamExecutionEnvironment#disableOperatorChaining`). This way the ID of each

[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2018-04-03 Thread ShashwatRastogi-Reflektion
Github user ShashwatRastogi-Reflektion commented on the issue: https://github.com/apache/flink/pull/3117 @zentol I am using flink 1.3.2. Normally, I don't use `--allowNonRestoredState` and I get an error while restarting the job. After using this `allowNonRestoredState` the job

[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2018-04-03 Thread zentol
Github user zentol commented on the issue: https://github.com/apache/flink/pull/3117 @ShashwatRastogi-Reflektion It's a bit odd that there are different ID's shown, I will have to look into that. It may be that one display accounts for the uid while the other one doesn't; in any case

[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2018-04-03 Thread ShashwatRastogi-Reflektion
Github user ShashwatRastogi-Reflektion commented on the issue: https://github.com/apache/flink/pull/3117 Hey @zentol Thank you for replying back. I was trying to do exactly the same thing, but I think I am messing something up that is why it isn't working in my case.

[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2018-04-03 Thread zentol
Github user zentol commented on the issue: https://github.com/apache/flink/pull/3117 @ShashwatRastogi-Reflektion 1. For each task to load from the savepoint S1: * Determine the existing hash by searching for the task ID in the logs/UI * Set the uidHash for that task

[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2018-04-03 Thread ShashwatRastogi-Reflektion
Github user ShashwatRastogi-Reflektion commented on the issue: https://github.com/apache/flink/pull/3117 Hey @uce, @StefanRRichter I too have a flink job running in production where operators doesn't have uids. Now, I have to add new operators and the job doesn't restart

[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2017-01-23 Thread StefanRRichter
Github user StefanRRichter commented on the issue: https://github.com/apache/flink/pull/3117 Thanks a lot for the review and such intensive testing @uce ! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2017-01-23 Thread uce
Github user uce commented on the issue: https://github.com/apache/flink/pull/3117 Thanks! Looks good. Just tested this with a job where I did not set any UIDs. After changing in an incompatible way (with respect to auto generated IDs) I was able to restore my state with `setUidHash`.

[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2017-01-23 Thread StefanRRichter
Github user StefanRRichter commented on the issue: https://github.com/apache/flink/pull/3117 Ok, I changed method names and commented as proposed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not

[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2017-01-20 Thread uce
Github user uce commented on the issue: https://github.com/apache/flink/pull/3117 Thanks for addressing the comments. I had a quick offline chat with Stephan regarding the naming of `setAdditionalNodeHash`. He also agrees that the name moves internal implementation details

[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2017-01-18 Thread StefanRRichter
Github user StefanRRichter commented on the issue: https://github.com/apache/flink/pull/3117 Thanks a lot for the reviews @zentol and @uce . I made another commit that addresses the review comments. --- If your project is set up for it, you can reply to this email and have your

[GitHub] flink issue #3117: [FLINK-5480] Introduce user-provided hash for JobVertexes

2017-01-13 Thread StefanRRichter
Github user StefanRRichter commented on the issue: https://github.com/apache/flink/pull/3117 cc @uce --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or