[ 
https://issues.apache.org/jira/browse/STORM-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lorenzo Affetti updated STORM-1964:
-----------------------------------
    Description: 
I launched a topology applying a tumbling count window of size 2 (watermark 
interval 200ms, lag 1s) with the following input (timestamp,value):

{noformat}
(10,10)
(10,20)
(11,30)
(12,40)
(12,50)
(12,60)
(12,70)
(13,80)
(14,90)
(15,100)
{noformat}

And I got these windows as output:

{noformat}
[(10,10), (10,20)]
[(12,60), (12,70)]
[(12,60), (12,70)]    // why (60, 70) twice?
[(13,80), (14,90)]
{noformat}


I would expect something like:

{noformat}
[(10,10), (10,20)]
[(11,30), (12,40)]
[(12,50), (12,60)]
[(12,70), (13,80)]
[(14,90), (15,100)]
{noformat}


It seems like that timestamp extraction and count windows does not fit each 
other.

  was:
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)]


It seems like that timestamp extraction and count windows does not fit each 
other.


> Unexpected behavior when using count window together with timestamp extraction
> ------------------------------------------------------------------------------
>
>                 Key: STORM-1964
>                 URL: https://issues.apache.org/jira/browse/STORM-1964
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 1.0.1
>            Reporter: Lorenzo Affetti
>            Priority: Minor
>              Labels: timestamp, windowing
>
> I launched a topology applying a tumbling count window of size 2 (watermark 
> interval 200ms, lag 1s) with the following input (timestamp,value):
> {noformat}
> (10,10)
> (10,20)
> (11,30)
> (12,40)
> (12,50)
> (12,60)
> (12,70)
> (13,80)
> (14,90)
> (15,100)
> {noformat}
> And I got these windows as output:
> {noformat}
> [(10,10), (10,20)]
> [(12,60), (12,70)]
> [(12,60), (12,70)]    // why (60, 70) twice?
> [(13,80), (14,90)]
> {noformat}
> I would expect something like:
> {noformat}
> [(10,10), (10,20)]
> [(11,30), (12,40)]
> [(12,50), (12,60)]
> [(12,70), (13,80)]
> [(14,90), (15,100)]
> {noformat}
> It seems like that timestamp extraction and count windows does not fit each 
> other.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to