Thank you for reviewing FLIP-255.
That indeed is a typo. I will correct it immediately.
Best,
Nathan
------------------ ???????? ------------------
??????:
"dev"
<[email protected]>;
????????: 2022??8??2??(??????) ????11:09
??????: "dev"<[email protected]>;
????: Re: [Phishing Risk] [External] [DISCUSS] FLIP-255 Introduce
pre-aggregated merge to Table Store
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?6?7ny bi?6?7g d?6?7ata system?6?7?6?7s (such as Apache
Doris,?6?7&nbsp; Apache Kylin?6?7 , Druid etc.)&nbsp;to save storage
and accelerate the aggregate query.?6?7 FLIP-255 proposes to introduce
pre-aggregated merge into Flink Table Store to acquire the same
benefit.&nbsp; ?6?7Supported aggregate functions include&nbsp;sum,
max/min, count, replace_if_not_null, replace,&nbsp; concatenate,
or/and?6?7. ?6?7 Looking forward to your feedback.
[1]&nbsp;https://cwiki.apache.org/confluence/display?6?7/FLINK/FLIP-2?6?755+Introduce+pre-aggregated+merge+to+table+store
Best, Nathan Kan (?6?7Hongnan Gan)?6?7?6?7?6?7
