keremulutas commented on a change in pull request #17:
URL:
https://github.com/apache/flink-statefun-docker/pull/17#discussion_r770015790
##########
File path: template/flink-distribution/conf/flink-conf.yaml
##########
@@ -53,3 +53,11 @@ taskmanager.state.local.root-dirs:
file:///local/state/recovery
jobmanager.memory.process.size: 1g
taskmanager.memory.process.size: 4g
+
+#==============================================================================
+# Support easy upgrades as the module.yaml file updates
+#==============================================================================
+
+pipeline.auto-generate-uids: false
+execution.savepoint.eignore-unclaimed-state: true
Review comment:
I have a question about enforcing
`execution.savepoint.ignore-unclaimed-state` config - is there a possibility
that an operator created in a StateFun application may not be checkpointed? If
that is not the case, then I have a use case which enforcing this config might
hurt a little. I am using the state bootstrapping functionality. In case I miss
to bootstrap a state, it is going to be an empty state without me noticing I
actually forgot to fill that state. What do you think?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]