at will happen if more
> elements arrive *at the last millisecond, but AFTER the window is fired*?
>
> Thanks,
> Youjun
> *发件人**:* Hequn Cheng
> *发送时间:* Friday, July 13, 2018 9:44 PM
> *收件人:* Yuan,Youjun
> *抄送:* Timo Walther ; user@flink.apache.org
> *主题:* Re: 答复: 答复: Tumblin
t the last millisecond, but AFTER the window is fired?
>>
>> Thanks,
>> Youjun
>> 发件人: Hequn Cheng mailto:chenghe...@gmail.com>>
>> 发送时间: Friday, July 13, 2018 9:44 PM
>> 收件人: Yuan,Youjun mailto:yuanyou...@baidu.com>>
>> 抄送: Timo Walther mailto:twal...@ap
ly 13, 2018 9:44 PM
> 收件人: Yuan,Youjun
> 抄送: Timo Walther ; user@flink.apache.org
> 主题: Re: 答复: 答复: TumblingProcessingTimeWindow emits extra results for a same
> window
>
> Hi Youjun,
>
> The rowtime value in udf:EXTRACT(EPOCH FROM rowtime) is different from the
> row
: Yuan,Youjun
抄送: Timo Walther ; user@flink.apache.org
主题: Re: 答复: 答复: TumblingProcessingTimeWindow emits extra results for a same
window
Hi Youjun,
The rowtime value in udf:EXTRACT(EPOCH FROM rowtime) is different from the
rowtime value of window. Sql will be parsed and translated into some nodes
r01"
> ,"min_ts":1531447919981,"max_ts":1531448159975}
>
> {"timestamp":153144816,"cnt":3278178,"userId":"user01"
> ,"min_ts":1531448159098,"max_ts":1531448399977}
>
> {"timestamp":15
;:"user01","min_ts":1531447919981,"max_ts":1531448159975}
{"timestamp":153144816,"cnt":3278178,"userId":"user01","min_ts":1531448159098,"max_ts":1531448399977}
{"timestamp":153144816,"cnt"
,"min_sec":1531395119}
>
> {"timestamp":153139500,"cnt":2,"userId":"user01","min_sec":1531395119}
>
> {"timestamp":153139500,"cnt":2,"userId":"user01","min_sec":15313951
;:"user01","min_sec":1531395119}
{"timestamp":153139500,"cnt":2,"userId":"user01","min_sec":1531395119}
{"timestamp":153139500,"cnt":2,"userId":"user01","min_sec":1531395119}
Th
Hi Yuan,
this sounds indeed weird. The SQL API uses regular DataStream API
windows underneath so this problem should have come up earlier if this
is problem in the implementation. Does this behavior reproducible on
your local machine?
One thing that comes to my mind is that the "userId"s mig
Hi community,
I have a job which counts event number every 2 minutes, with TumblingWindow in
ProcessingTime. However, it occasionally produces extra DUPLICATED records. For
instance, for timestamp 153136848 below, it emits a normal result
(cnt=1641161), and then followed by a few more recor
10 matches
Mail list logo
