oscerd opened a new pull request, #27507: URL: https://github.com/apache/camel/pull/27507
Debezium consumer health checks currently report UP while their connector tasks are still starting. Honor the configured health-check initial state (DOWN by default) until the engine invokes its pollingStarted callback, then report UP even when no change events have arrived. Reset readiness on each consumer start and preserve engine-failure reporting. CAMEL-24889 deliberately scoped its original health check to engine failures; this adds the startup signal deferred to CAMEL-24919. Debezium's polling callback signals that tasks have started and polling is enabled, before actual polling. It does not guarantee that an initial snapshot has completed. The component documentation and 4.23 upgrade guide describe this distinction and the `camel.health.initial-state=up` compatibility setting. Validation: - A real embedded file connector waits on a startup latch, covering DOWN/UP/UNKNOWN initial states, disabled checks, readiness without records, and repeated starts of the same consumer. The original implementation failed the DOWN and UNKNOWN startup assertions. - Complete Debezium common-module `verify`: 21 tests passed, zero failures/errors/skips. - Full 699-module reactor `mvn -Dquickly install` passed. Regenerated catalog documentation matches all six component pages. - Formatter, import sorting, and `git diff --check` passed. [CAMEL-24919](https://issues.apache.org/jira/browse/CAMEL-24919) ยท [Debezium 3.6.3 callback contract](https://github.com/debezium/debezium/blob/v3.6.3.Final/debezium-api/src/main/java/io/debezium/engine/DebeziumEngine.java#L100) _AI-generated by Codex on behalf of oscerd._ Generated by Codex via OSS Helper -- 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]
