Hi Nathan,

Seems a great proposal for table store aggregation.
In the example, I think the 'max_field1' should be 1 instead of 2 after the
max aggregation in the output result.
And there may be a minor typo in the WITH clause, 'max_field2' ->
'max_field1'.

Best,
Guojun

From: "Hannan Kan"<[email protected]>
Date: Mon, Aug 1, 2022, 11:35 PM
Subject: [Phishing Risk] [External] [DISCUSS] FLIP-255 Introduce
pre-aggregated merge to Table Store
To: "dev"<[email protected]>
Cc: "lzljs3620320"<[email protected]>
Hi everyone, I would like to open a discussion on&nbsp;FLIP-255 Introduce
pre-aggregated merge to table store&nbsp;[1]. Pre-aggregation mechanism has
been adopted by ma​ny bi​g d​ata system​​s (such as Apache Doris,​&nbsp;
Apache Kylin​ , Druid etc.)&nbsp;to save storage and accelerate the
aggregate query.​ FLIP-255 proposes to introduce pre-aggregated merge into
Flink Table Store to acquire the same benefit.&nbsp; ​Supported aggregate
functions include&nbsp;sum, max/min, count, replace_if_not_null,
replace,&nbsp; concatenate, or/and​. ​ Looking forward to your feedback.
[1]&nbsp;https://cwiki.apache.org/confluence/display​/FLINK/FLIP-2​55+Introduce+pre-aggregated+merge+to+table+store
Best, Nathan Kan (​Hongnan Gan)​​​

Reply via email to