[
https://issues.apache.org/jira/browse/FLINK-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14713586#comment-14713586
]
Aljoscha Krettek commented on FLINK-2410:
-----------------------------------------
There is some streaming code that depends on TypeInformation being
serializable, for example {{org.apache.flink.streaming.util.FieldAccessor}}.
We should find consensus about whether we want TypeInformation to be
serializable or not and then enforce the solution. The current mix does not
seem very good.
> 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)
