test(cdc): reproduce malformed optional key data loss on current develop - #314
Conversation
|
Warning Review limit reached
Next review available in: 108 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Rebuilds the malformed optional Debezium-key integrity boundary from exact protected
develop@4408b6086fd725ff1629d8f048cf28f3a2b40b1bwithout rewriting stale-base #304.Exact fail-first head:
891ba83f52dbc291d3ad49807fca79d0a708ba6d. The sole change is a focused production-boundary test: valid update value data containsafter.id=42, while optionalkeyJsonis malformed. ProtectedDebeziumChangeRecordMappercurrently letsextractPk(...)throw into the outer required-valueIOExceptioncatch, discarding the otherwise valid event.Valid RED must be the focused assertion that the result is absent after normal compile/test startup. Only after exact-current-head RED is proven should the narrow optional-key parse isolation and public-contract Javadoc be replayed. No check/review from #304 or another head transfers.