As part of this FLIP, does it make sense to also extend the documentation
for the sort shuffle [1] to include a tuning guide? I am thinking of a more
in depth description of what things you might observe and how to influence
them with the configuration options.
[1]
https://nightlies.apache.org/fli
Hi,
> I think setting taskmanager.network.sort-shuffle.min-parallelism to 1 and
> using sort-shuffle for all cases by default is a good suggestion. I am not
> choosing this value mainly because two reasons:
> 1. The first one is that it increases the usage of network memory which may
> cause
Hi！
可以用 SQL 的聚合函数 [1] 实现。内置聚合函数详见 [2]，也可以自定义聚合函数，详见 [3]。
[1]
https://nightlies.apache.org/flink/flink-docs-master/zh/docs/dev/table/sql/queries/group-agg/
[2]
https://nightlies.apache.org/flink/flink-docs-master/zh/docs/dev/table/functions/systemfunctions/#%E8%81%9A%E5%90%88%E5%87%BD%E6%95%B0
[3]
-- --
??:
"user-zh"
业务需要按每分钟统计不同交易状态的交易数，接了业务mysql库binlog到flink计算。这是一个retract回撤流。是不能够直接使用Tumble
window计算的。
1. 那么是不是只能用全量窗口的方式实现？即group by交易时间落到其时长为一分钟的窗口，再配合state TTL来过期不需要的状态？
2. 这样一来的话每来一笔交易都会更新状态，如果直接输出到下游mysql保存的话会对mysql造成很大写压力，那么是不是可以再接一个Tumble
window获取每个指标的最新统计值输出？
3. 另外我在想是不是可以将retract流转变成append流，再在上面使用Tumble
嗯，正解，谢谢！
在 2021-12-14 14:26:35，"yidan zhao" 写道：
>应该在open中做全量数据的初始化。然后broadcastState做增量的更新。
>
>Caizhi Weng 于2021年12月14日周二 09:50写道：
>
>> Hi！
>>
>> 可以看一下 event time temporal join [1] 是否满足需求。
>>
>> [1]
>>
>> https://nightlies.apache.org/flink/flink-docs-release-1.13/zh/docs/dev/table
Hi Till,
Thanks for the suggestion. I think it makes a lot of sense to also extend
the documentation for the sort shuffle to include a tuning guide.
Best,
Yingjie
Till Rohrmann 于2021年12月14日周二 18:57写道：
> As part of this FLIP, does it make sense to also extend the documentation
> for the sort sh
