That is correct, RETRACTING_FIRED_PANES is unimplemented[1].
1: https://issues.apache.org/jira/browse/BEAM-91
On Tue, Jan 21, 2020 at 8:11 AM tison wrote:
> IIUC RETRACTING_FIRED_PANES is not yet implemented but only a placeholder,
> is it?
>
> Best,
> tison.
>
>
> tison 于2020年1月21日周二
IIUC RETRACTING_FIRED_PANES is not yet implemented but only a placeholder,
is it?
Best,
tison.
tison 于2020年1月21日周二 下午11:59写道：
> Thanks for your explanation Max. I will take a look.
>
> Best,
> tison.
>
>
> Maximilian Michels 于2020年1月21日周二 下午11:45写道：
>
>> Hi Tison,
>>
>> Beam has its own set
Thanks for your explanation Max. I will take a look.
Best,
tison.
Maximilian Michels 于2020年1月21日周二 下午11:45写道：
> Hi Tison,
>
> Beam has its own set of libraries to implement windowing. Hence, the
> Flink Runner does not use Flink's windowing but deploys Beam's windowing
> logic within a Flink
Hi Tison,
Beam has its own set of libraries to implement windowing. Hence, the
Flink Runner does not use Flink's windowing but deploys Beam's windowing
logic within a Flink operator. If you want to look in the code, have a
look at WindowDoFnOperator.
Cheers,
Max
On 21.01.20 10:35, tison
Hi guys,
I'm curious that how does BEAM translate its AccumulationMode such
as DISCARDING_FIRED_PANES and ACCUMULATING_FIRED_PANES to Flink Runner
implementation. Since I don't find directly respective concept in Flink
world it puzzles me a lot.
Best,
tison.
