Github user senorcarbone commented on the pull request: https://github.com/apache/flink/pull/1150#issuecomment-141907506 At first I found it a bit odd to include serialized checkpointers on every single statehandle but on a second look maybe that is the only way to generalize operator states. The main problem is that StreamOperatorState can be defined dynamically during runtime and thus, we need to allow dynamic checkpointers along with the operator states and include them in the state handles. An alternative take which is slightly more restrictive is to enforce the user to pre-define all mappings from custom operator state names to checkpointers so we can configure these in the tasks themselves (kept in the execution graph once) instead of including them on each state handle. Apart from this concern the PR is well tested and documented! Any other opinions?
--- 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 if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---