diegomrsantos opened a new issue, #4238: URL: https://github.com/apache/iggy/issues/4238
Parent tracker: #4232. Make the supported delivery guarantee the default for new sink configurations in the agreed release, and provide an explicit migration path for existing deployments and plugins. Acceptance criteria: - New configurations select the reliable behavior. The runtime validates plugin compatibility and required settings it can check, producing actionable errors for unsupported configurations. - Existing deployments receive documented configuration changes, plugin rebuild requirements, duplicate handling guidance, and the agreed deprecation policy. - Upgrades preserve the consumer identity and valid checkpoints. Recovery of records skipped before migration is a deliberate replay procedure with documented consequences. - Expose pending work, retry or stopped state, delivery progress, checkpoint progress, and actionable failure details. Document retention monitoring and recovery procedures. - Tests cover supported upgrade paths, incompatible versions, configuration defaults, and any supported rollback procedure. - Release documentation states the supported destinations, required settings, failure assumptions, and remaining limitations. Depends on the decisions in A and the relevant work in B through E. Defaults and migration instructions should be reviewed during implementation and validated before the feature is released. -- 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]
