Hi Jiadong,
>From the context you described, I think ProcessingTimeWindow may not be a
good solution.
If I understand correctly, you'd like to use the same SQL for streaming and
batch jobs in your platform. How about creating partitioned Sink tables for
streaming jobs instead of Window? Then the s
Hi Shanmmon,
Thank you for your quick response.
To give you some context, I am working on a project that involves
joining two streams and performing some left/inner join operations based
on certain keys. As for using batch mode, my intention is to have a
unified approach that works for both s
Hi Jiadong
Using the process time window in Batch jobs may be a little strange for
me. I prefer to partition the data according to the day level, and then the
Batch job reads data from different partitions instead of using Window.
Best,
Shammon FY
On Wed, Apr 26, 2023 at 12:03 PM Jiadong Lu wro
Hi, Shammon,
Thank you for your reply.
Yes, the window configured with `Time.days(1)` has no special meaning,
it is just used to group all data into the same global window.
I tried using `GlobalWindow` for this scenario, but `GlobalWindow` also
need a `Trigger` like
`org.apache.flink.streaming.
Hi Jiadong,
I think it depends on the specific role of the window here for you. If this
window has no specific business meaning and is only used for performance
optimization, maybe you can consider to use join directly
Best,
Shammon FY
On Tue, Apr 25, 2023 at 5:42 PM Jiadong Lu wrote:
> Hello,
Hello,everyone,
I am confused about the window of join/coGroup operator in Batch mode.
Here is my demo code, and it works fine for me at present. I wonder if
this approach that using process time window in batch mode is
appropriate? and does this approach have any problems? I want to use
this
