Hi Dong and Xuannan,
Thanks for your proposal! Processing time temporal join is a very important
feature, the proper implementation of which users have been waiting for a
long time.
However, I am wondering whether it is worth enhancing Watermarks and
related classes in order to support this feat
Alexander Smirnov created FLINK-31729:
-
Summary: Unexpected UPDATE_BEFORE output record in LEFT OUTER JOIN
Key: FLINK-31729
URL: https://issues.apache.org/jira/browse/FLINK-31729
Project: Flink
Alexander Smirnov created FLINK-30778:
-
Summary: Add Configuration into FunctionContext
Key: FLINK-30778
URL: https://issues.apache.org/jira/browse/FLINK-30778
Project: Flink
Issue Type
+1 (non-binding)
Best,
Alexander
чт, 23 июн. 2022 г., 11:49 Qingsheng Ren :
> Hi devs,
>
> I’d like to start a vote thread for FLIP-221: Abstraction for lookup
> source and metric. You can find the discussion thread in [2]*.
>
> The vote will be open for at least 72 hours unless there is an obje
Hi Qingsheng,
I like the current design, thanks for your efforts! I have no
objections at the moment.
+1 to start the vote.
Best regards,
Alexander
ср, 22 июн. 2022 г. в 15:59, Qingsheng Ren :
>
> Hi Jingsong,
>
> 1. Updated and thanks for the reminder!
>
> 2. We could do so for implementation b
Hi Jingsong and devs!
I agree that custom reloading would be very useful, so I changed
recently proposed ReloadTime to customizable ReloadStrategy and its
default realization FixedDelayReloadStrategy. I updated the FLIP, you
can look at the new design [1]. From my point of view, the
disadvantage o
Hi Qingsheng and devs,
I like the new concept of partial / full caching. Thanks for your
efforts, Qingsheng!
> The schedule-with-delay idea looks reasonable to me, but I think we need to
> redesign the builder API of full caching to make it more descriptive > for
> developers.
I've got the acc
