clarax opened a new pull request, #406: URL: https://github.com/apache/flink-kubernetes-operator/pull/406
…oint ## What is the purpose of the change https://issues.apache.org/jira/browse/FLINK-29695 Users want to know the status of last savepoint, especially for manually triggered ones, to manage savepoints. Currently, users can infer the status of the last savepoint (PENDING, SUCCEEDED and ABANDONED) from jobStatus.triggerId, lastSavepoint.triggerNonce, spec.job.savepointTriggerNonce and savepointTriggerNonce from last reconciliation. If the last savepoint is not manually triggered, there is no ABANDONED status, only PENDING or SUCCEEDED. Creating a utility will encapsulate the internal logic of Flink operator guard against regression by any future version changes. ## Brief change log - Added SavepointStatus class and getLastSavepointStatus method to SavepointUtils ## Verifying this change Added verification of savepoint status in existing SavepointOserverTests and ApplicationReconcilerTests for manual and non-manual savepoints for all types of SavepointStatus ## 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 changes to the `CustomResourceDescriptors`: No - Core observer or reconciler logic that is regularly executed: No ## Documentation - Does this pull request introduce a new feature? No - If yes, how is the feature documented? No -- 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]
