You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2017/11/03 17:26:00 UTC

[jira] [Resolved] (FLINK-7972) Move SerializationSchema to flink-core

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

Stephan Ewen resolved FLINK-7972.
---------------------------------
    Resolution: Fixed

Fixed in fe931d075f031e9494fd26dbeed4bb1024bd52cf

> Move SerializationSchema to flink-core
> --------------------------------------
>
>                 Key: FLINK-7972
>                 URL: https://issues.apache.org/jira/browse/FLINK-7972
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>             Fix For: 1.4.0
>
>
> The {{SerializationSchema}} and its related classes are currently in {{flink-streaming-java}}.
> API level projects that depend on those classes hence pull in a dependency on runtime classes.
> For example, this would be required in order to make {{flink-avro}} independent of runtime dependencies and Scala versions, same for the future for thrift format support, for Hbase connectors, etc.
> This should not be API breaking since we can keep the classes in the same namespace and only move them "updstream" in the dependency structure, or we can keep classes in the original namespace that extend the moved classes in {{flink-core}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)