...

We can introduce richer merge strategies, one of which is already introduced is PartialUpdateMergeFunction, which completes non-NULL fields when merging. We can introduce more powerful merge strategies, such as support for pre-aggregated merges. Currently the pre-aggregation is used by many big data systems, e.g. Apache Doris, Apache Kylin, Druid, to reduce storage cost and accelerate aggregation query. By introducing pre-aggregated merge to Flink table store, it can acquire the same benefit.  Aggregate functions which we plan to  implement includes sum, max/min, count, replace_if_not_null, replace, concatenate, or/and.

Public Interfaces

Usage of pre-aggregated merge

To use pre-aggregated merge in Flink Table Store, two kind of configurations should be added to WITH clause when creating table.

1. assign 'aggregation' to 'merge-engine' 
2. designate aggregate function for each column of table.

Briefly list any new interfaces that will be introduced as part of this proposal or any existing interfaces that will be removed or changed. The purpose of this section is to concisely call out the public contract that will come along with this feature.

...

• What impact (if any) will there be on existing users?
  • They can decide whether to use pre-aggregated merge. If no, no impact on them. Otherwise, they have to  add some configurations in WITH clause when creating table. Configurations are described in 'Public Interfaces' section.
• If we are changing behavior how will we phase out the older behavior?
  • No need to phase out older behavior.
• If we need special migration tools, describe them here.
  • None.
• When will we remove the existing behavior?
  • No need.

Test Plan

Each  pre-aggregated merge function will be covered with IT tests.

Rejected Alternatives

None.