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

Stephan Ewen commented on FLINK-2410:
-------------------------------------

I think there is nothing that speaks against serializability.

We should encourage to not ship TypeInformation, but rather the serializers and 
comparators, but that does not mean TypeInformation cannot be serializable.

> PojoTypeInfo is not completely serializable
> -------------------------------------------
>
>                 Key: FLINK-2410
>                 URL: https://issues.apache.org/jira/browse/FLINK-2410
>             Project: Flink
>          Issue Type: Bug
>          Components: Java API
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>
> Table API requires PojoTypeInfo to be serializable. The following code fails:
> {code}
> Table finishedEtlTable = maxMeasurements
> .join(stationTable).where("s_station_id = m_station_id")
> .select("year, month, day, value, country, name");
> DataSet<MaxTemperature> maxTemp = tableEnv.toDataSet(finishedEtlTable, 
> MaxTemperature.class);
> maxTemp
> .groupBy("year")
> .sortGroup("value", Order.DESCENDING)
> .first(1)
> .print();
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to