ferran-gali-lifullconnect commented on issue #13067: URL: https://github.com/apache/iceberg/issues/13067#issuecomment-3131808030
I think we’re experiencing the same issue with Apache Iceberg Kafka Connect (v1.9.1). When everything is working correctly, the `org.apache.iceberg.connect.channel.Coordinator` logs look like this: ``` Commit 60560861-b4ed-4853-8bf7-d79148dd31bb initiated Commit complete to table MY_ICEBERG_TABLE, snapshot 6419974970605020043, commit ID 60560861-b4ed-4853-8bf7-d79148dd31bb, valid-through 2025-07-28T00:58:49.075Z Commit 60560861-b4ed-4853-8bf7-d79148dd31bb complete, committed to 1 table(s), valid-through 2025-07-28T00:58:49.075Z ``` However, when lag appears on the coordinator topic, the logs change to: ``` Commit f9bbf292-4149-4d12-a116-9aef0efd4f45 initiated Commit f9bbf292-4149-4d12-a116-9aef0efd4f45 complete, committed to 0 table(s), valid-through null ``` The result when there is lag, is that data gets written into the iceberg table (MY_ICEBERG_TABLE), but the metadata does not. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
