[jira] [Closed] (FLINK-19485) Decouple runtime operator implementation from DataStream operations

["Kostas Kloudas (Jira)" <ji...@apache.org>]

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

Kostas Kloudas closed FLINK-19485.
----------------------------------
    Resolution: Implemented

Merged on master with 0c3dfc8d2d402492d46f5b5cb1d5495c49adfbe1

> Decouple runtime operator implementation from DataStream operations 
> --------------------------------------------------------------------
>
>                 Key: FLINK-19485
>                 URL: https://issues.apache.org/jira/browse/FLINK-19485
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / DataStream
>    Affects Versions: 1.12.0
>            Reporter: Kostas Kloudas
>            Assignee: Kostas Kloudas
>            Priority: Major
>              Labels: pull-request-available
>
> Although DataStream is going to be the unified API for Batch and Streaming applications, some operations, e.g. Sinks, may need to have different runtime implementations depending on if they are intended to run on bounded or unbounded data. This is not necessarily only for optimisations but also for the exposed semantics, i.e. correctness.
> So far, DataStream had a 1-to-1 mapping between an API call and an operator. In a sense, the DataStream API was an "explicit" API. With this addition, we will decouple the API calls from the actual runtime implementations and thus allow different operations to have more than one runtime implementations, depending (for now) on the {{execution.runtime-mode}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)