GitHub user StefanRRichter opened a pull request:
https://github.com/apache/flink/pull/4491
[FLINK-7362] [checkpoints] Savepoint property is lost after de/serialâ¦
â¦ization of CheckpointProperties
## What is the purpose of the change
This PR fixes lost information about the savepoint property when
de/serializing `CheckpointProperty`. The problem was caused by serialization in
connection with a singleton that was checked for referencial equality to derive
the savepoint property.
## Brief change log
This makes the savepoint property explicit as a boolean field in
`CheckpointProperty`.
## Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Nevertheless I added a small test.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (no)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (no)
- The serializers: (no)
- The runtime per-record code paths (performance sensitive): (no)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
## Documentation
- Does this pull request introduce a new feature? (no)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/StefanRRichter/flink
serializable-savepoint-property
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/4491.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4491
----
commit 64eb3abb55f515252069371f7dd8f874b9c73c7e
Author: Stefan Richter <s.rich...@data-artisans.com>
Date: 2017-08-07T14:22:32Z
[FLINK-7362] [checkpoints] Savepoint property is lost after
de/serialization of CheckpointProperties
----
---
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.
---
