[BUG] Retract message for Aggregate table will lead to NPE for record ttl compaction

[xiangyuf]

Search before asking

• I searched in the issues and found nothing similar.

Motivation

For an aggregation Paimon PK table, if it receives a retract message at first, it will inevitably generate a +I message with a negative value for SumAggField or null value for other agg fields. If this table has enabled record level ttl, this will throw an IllegalArgumentException during compaction if the ttl time field is null.

The first react message may generated from the out-of-order issue during now-primary key hashing in streaming computation.

Solution

Ignore first retract message for aggregate table if its record level TTL is enabled. In most cases, the first retract message is meaningless for an aggregation table.

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!