flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "PJ Van Aeken (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2023) TypeExtractor does not work for (some) Scala Classes
Date Mon, 18 May 2015 07:50:00 GMT

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

PJ Van Aeken commented on FLINK-2023:

The thing is that the Scala DataSet API reimplements the logic of the Java DataSet API rather
than wrapping around it. For instance, scala.DataSet.map(MapFunction) builds a new MapOperator
rather than passing the MapFunction to the Java API so a MapOperator is built there. The reason
for this is probably similar to this issue. 

For the Scala Gelly API, we are trying to avoid reimplementing the whole thing in Scala. If
we weren't, we could've just talked to the Scala DataSet API rather than dealing with the
Java API. Since the Gelly API is more high level, I'm not sure how we could go about creating
a thin layer to provide implicit TypeInformations without drilling all the way down to the
layer of MapOperators, which would require reimplementing a lot of the Gelly logic (in which
case it would be better to reimplement it on top of the scala DataSet API).

> TypeExtractor does not work for (some) Scala Classes
> ----------------------------------------------------
>                 Key: FLINK-2023
>                 URL: https://issues.apache.org/jira/browse/FLINK-2023
>             Project: Flink
>          Issue Type: Bug
>          Components: Type Serialization System
>            Reporter: Aljoscha Krettek
> [~vanaepi] discovered some problems while working on the Scala Gelly API where, for example,
a Scala MapFunction can not be correctly analyzed by the type extractor. For example, generic
types will not be correctly detected.

This message was sent by Atlassian JIRA

View raw message