rpuch opened a new pull request, #7598: URL: https://github.com/apache/ignite-3/pull/7598
https://issues.apache.org/jira/browse/IGNITE-27460 * Introduce a mechanism to validate command+safeTime in Raft - this happens after we assign a safeTime to a command, but before it gets saved to log on the leader (and hence before it gets replicated) - this allows to request a retry of the same command by the Raft client (if the failure is temporary, like insufficient schemas information on the node) or instruct it to fail the command if it will never become valid * Introduce full commands validation wrt schema compatibility - do the validation in the Raft extension point introduced above (as safeTime becomes commitTs for full updates) - if the node lacks schema information, fail the validation requesting a retry from the Raft client - if the commitTs is invalid, return the result to Replica listener - in Replica listener, handle the failure by retrying the replica request (using updated schema) Thank you for submitting the pull request. To streamline the review process of the patch and ensure better code quality we ask both an author and a reviewer to verify the following: ### The Review Checklist - [ ] **Formal criteria:** TC status, codestyle, mandatory documentation. Also make sure to complete the following: \- There is a single JIRA ticket related to the pull request. \- The web-link to the pull request is attached to the JIRA ticket. \- The JIRA ticket has the Patch Available state. \- The description of the JIRA ticket explains WHAT was made, WHY and HOW. \- The pull request title is treated as the final commit message. The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue. - [ ] **Design:** new code conforms with the design principles of the components it is added to. - [ ] **Patch quality:** patch cannot be split into smaller pieces, its size must be reasonable. - [ ] **Code quality:** code is clean and readable, necessary developer documentation is added if needed. - [ ] **Tests code quality:** test set covers positive/negative scenarios, happy/edge cases. Tests are effective in terms of execution time and resources. ### Notes - [Apache Ignite Coding Guidelines](https://cwiki.apache.org/confluence/display/IGNITE/Java+Code+Style+Guide) -- 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]
