Thank you Arun for your precious advice! Anyway, I reported the issue: https://issues.apache.org/jira/browse/STORM-1964 <https://issues.apache.org/jira/browse/STORM-1964>.
Lorenzo Affetti > On 12 Jul 2016, at 13:03, Arun Mahadevan <[email protected]> wrote: > > It may be a bug. You can raise an issue here - > https://issues.apache.org/jira/browse/STORM > <https://issues.apache.org/jira/browse/STORM> > > If you just want count based windows (without accounting for event > time/watermarks) you don’t need to set withTimestampField() and it should > work. > > Thanks, > Arun > > From: Lorenzo Affetti <[email protected]> > Reply-To: "[email protected]" <[email protected]> > Date: Tuesday, July 12, 2016 at 3:46 PM > To: "[email protected]" <[email protected]> > Subject: About count windows behavior > > Hi everybody, > > I launched a topology applying a tumbling count window of size 2 (watermark > interval 200ms, lag 1s) with the following input: > > 70 > 60 > 20 50 > 10 30 40 80 90 100 values > |———|———|———|———|———|—————> time > 10 11 12 13 14 15 > timestamps [s] > > And I got these windows as output (the format for a tuple is (timestamp, > value)): > > [(10,10), (10,20)] > [(12,60), (12,70)] > [(12,60), (12,70)] // why (60, 70) 2 times? > [(13,80), (14,90)] > > > I would expect something like: > > [(10,10), (10,20)] > [(11,30), (12,40)] > [(12,50), (12,60)] > [(12,70), (13,80)] > [(14,90), (15,100)] > > > Can anyone explain to me this behavior? > > Thank you in advance. > > > Lorenzo Affetti > > >
