zhangdonghao

> Thanks @hawk9821 point this issue, this is a bug, good catch. > > > It would be more appropriate to move interface org.apache.seatunnel.transform.sql.zeta.ZetaUDF to the api module > >...

assign to me

[https://github.com/apache/seatunnel/blob/dev/docs/en/connector-v2/sink/Paimon.md#changelog](https://github.com/apache/seatunnel/blob/dev/docs/en/connector-v2/sink/Paimon.md#changelog) Only the changelog-producer of ST paimon is supported the none and input mode. `deletion-vectors.enabled=true` used the lookup mode. It didn't reappear this issues after I upgraded the Piamon version...

> Hi @hawk9821 Thanks for the contribution. > > Even if the verification here can pass, what about after that? How should users operate? Can you describe a complete story?...

Pseudocode example, there are errors here. I will fix it.

应该是告警时效性的问题， 在告警发触发的时候产生了告警， 告警记录的状态并没有更新导致的。 重启yarn 服务告警就没有了 告警的计算逻辑应该是没问题的 。 我发现从 alertmanager 发送的告警信息 status 都是 firing ， 没有 resolved ， 导致告警记录的状态不会更新  @datasophon