Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Fri, 15 Jan 2016 15:30:40 +0000 (UTC)
From: "Aljoscha Krettek (JIRA)" <jira@apache.org>
To: dev@flink.apache.org
Message-ID: <JIRA.12931494.1452871797000.122390.1452871840018@Atlassian.JIRA>
In-Reply-To: <JIRA.12931494.1452871797000@Atlassian.JIRA>
References: <JIRA.12931494.1452871797000@Atlassian.JIRA>
 <JIRA.12931494.1452871797638@arcas>
Subject: [jira] [Created] (FLINK-3243) Fix Interplay of TimeCharacteristic
 and Time Windows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aljoscha Krettek created FLINK-3243:
---------------------------------------

             Summary: 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)