sydneyhoran commented on issue #8519:
URL: https://github.com/apache/hudi/issues/8519#issuecomment-1533514539
The reason I was getting an error on deleting records without tombstone was
because we were testing by starting from a midpoint of a Kafka topic, so I
suspect Deltastreamer didn't
sydneyhoran commented on issue #8519:
URL: https://github.com/apache/hudi/issues/8519#issuecomment-1533511853
Thanks to help from Aditya, @rmahindra123 and @nsivabalan , this was the
fix that worked for us to filter out tombstones:
sydneyhoran commented on issue #8519:
URL: https://github.com/apache/hudi/issues/8519#issuecomment-152991
Thank you @the-other-tim-brown for the explanation/confirmation. That is
what we have assumed as well, but it seems with our configuration we are unable
to parse the event with
sydneyhoran commented on issue #8519:
URL: https://github.com/apache/hudi/issues/8519#issuecomment-1529939285
When we either turn off tombstones in Debezium, or filter them out in
DebeziumSource.java, no null/tombstones are coming in (which is good). But we
still get a "commit failed" and
sydneyhoran commented on issue #8519:
URL: https://github.com/apache/hudi/issues/8519#issuecomment-1524068006
My team is trying to develop a Custom Transformer class that can skip over
null (tombstone) records from PostgresDebezium Kafka Source to address this. We
are attempting along the
sydneyhoran commented on issue #8519:
URL: https://github.com/apache/hudi/issues/8519#issuecomment-1524065639
Just as an update, we were able to set tombstones.on.delete to `false` in a
lower environment and still got the following error after a delete op:
--
This is an automated message
