flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3243) Fix Interplay of TimeCharacteristic and Time Windows
Date Mon, 08 Feb 2016 18:34:40 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137431#comment-15137431
] 

ASF GitHub Bot commented on FLINK-3243:
---------------------------------------

Github user StephanEwen commented on the pull request:

    https://github.com/apache/flink/pull/1513#issuecomment-181511999
  
    Is the switch from `ProcessingTime` to `PROCESSING_TIME` actually necessary?
    Breaks yet one more thing for users just because of a matter of taste.
    
    There are only so many breaking changes that we can do without upsetting people too much,
and I would like to make those where it makes a difference.


> Fix Interplay of TimeCharacteristic and Time Windows
> ----------------------------------------------------
>
>                 Key: FLINK-3243
>                 URL: https://issues.apache.org/jira/browse/FLINK-3243
>             Project: Flink
>          Issue Type: Bug
>          Components: Streaming
>    Affects Versions: 1.0.0
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Blocker
>
> As per the discussion on the Dev ML: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Time-Behavior-in-Streaming-Jobs-Event-time-processing-time-td9616.html.
> The discussion seems to have converged on option 2):
> - Add dedicated WindowAssigners for processing time and event time
> - {{timeWindow()}} and {{timeWindowAll()}} respect the set {{TimeCharacteristic}}. 
> This will make the easy stuff easy, i.e. using time windows and quickly switching the
time characteristic. Users will then have the flexibility to mix different kinds of window
assigners in their job.



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

Mime
View raw message