You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "nsivabalan (via GitHub)" <gi...@apache.org> on 2026/06/25 03:08:58 UTC
Re: [I] Update to handle deletes in postgres debezium [hudi]
nsivabalan commented on issue #15718:
URL: https://github.com/apache/hudi/issues/15718#issuecomment-4795467505
Triage note: this looks **fixed** on current `master`.
The failure modes you described are addressed by:
- **Deletes** — [HUDI-6199 / PR #8690](https://github.com/apache/hudi/pull/8690) (commit `1d780e220e07`) added `isDeleteRecord(GenericRecord)` so that Debezium payloads detect deletes via the `op=d` field rather than only the `_hoodie_is_deleted` flag. See [`AbstractDebeziumAvroPayload.java` lines 107-114](https://github.com/apache/hudi/blob/master/hudi-common/src/main/java/org/apache/hudi/common/model/debezium/AbstractDebeziumAvroPayload.java#L107-L114).
- **Null debezium fields after JDBC bootstrap (the schema-update / `#7219` family of errors)** — [HUDI-5203 / PR #7193](https://github.com/apache/hudi/pull/7193) (commit `a8ed77a67d03`) handles null `event seq` (MySQL) / `LSN` (Postgres).
- **Empty payloads in merge handle** — [PR #7944](https://github.com/apache/hudi/pull/7944) (commit `905e0876fd3e`).
The linked PR #7687 was superseded by these fixes. If you're still hitting an issue on a recent Hudi release, please reopen with the stack trace and the Hudi version so we can re-investigate. Otherwise, this issue can likely be closed.
--
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: commits-unsubscribe@hudi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org