Hi Jun,
First of all how do you actually get the ranges? TimeWindow#getStart
returns a long, which you must've interpreted somehow. I will try to
describe my suspicions. I think the core problem is that you pass the
input in one timezone, but interpret in a different one. (the processing
time uses
Hi,Caizhi :
1.if I add offset ,
window(TumblingProcessingTimeWindows.of(Time.hours(6),Time.hours(-8)))
it wil get a error: TumblingProcessingTimeWindows parameters must
satisfy abs(offset) < size
2.If it is caused by do not adding an offset, then why the same code, I set the
window size to b
Hi Jun,
You have to specify an offset when defining the windows. According to the
Java docs of TumblingProcessingTimeWindows: "*if you are living in
somewhere which is not using UTC±00:00 time*,* such as China which is using
UTC+08:00*,*and you want a time window with size of one day*,* and window
Hi??Caizhi ??
the code like this :
dataStream
.keyBy(??device")
.window(TumblingProcessingTimeWindows.of(Time.hours(6)))
.trigger(ContinuousProcessingTimeTrigger.of(Time.seconds(5)))
.aggregate(new MyAggre(), new WindowResultFunction())
Hi Jun,
How do you define your window? Could you please show us the code?
Thanks.
Jun Zhang <825875...@qq.com> 于2019年11月27日周三 下午5:22写道：
> ,
> Hi:
> I defined a Tumbling window, I set the time size to one hour, and the
> resulting windows are [00: 00: 00-01: 00: 00], [01: 00: 00-02: 00: 00]. ...
,
Hi:
I defined a Tumbling window, I set the time size to one hour, and the resulting
windows are [00: 00: 00-01: 00: 00], [01: 00: 00-02: 00: 00].
This meets my expectations, but when I set the time size to 6 hours, the
resulting window size is [02: 00: 00-08: 00: 00], [08: 00
