flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-3303) Move all non-batch specific classes in flink-java to flink-core
Date Tue, 02 Feb 2016 17:25:39 GMT

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

Stephan Ewen resolved FLINK-3303.
    Resolution: Done

Done in 21a715867d655bb61df9a9f7eef37e42b99e206a

> Move all non-batch specific classes in flink-java to flink-core
> ---------------------------------------------------------------
>                 Key: FLINK-3303
>                 URL: https://issues.apache.org/jira/browse/FLINK-3303
>             Project: Flink
>          Issue Type: Improvement
>          Components: Core, Java API
>    Affects Versions: 0.10.0
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>             Fix For: 1.0.0
> Currently, {{flink-java}} has a lot of classes that are also needed by the streaming
api and that are useful to the classes in {{flink-core}}.
> In particular, certain improvements to the state API are blocked by the fact that certain
classes are not in {{flink-core}}.
> I suggest to move classes from {{flink-java}} to {{flink-core}} after the following pattern:
>   - {{flink-core}} will contain all classes that are common across the batch and streaming
>   - {{flink-java}} will contain all batch API specific classes (we may eventually even
think about renaming it to {{flink-batch-java}}.
> Because {{flink-java}} references {{flink-core}}, this will not be a breaking change.

This message was sent by Atlassian JIRA

View raw message