[
https://issues.apache.org/jira/browse/FLINK-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747171#comment-14747171
]
Till Rohrmann commented on FLINK-2684:
--------------------------------------
The benefits would be to re-establish the old contract that
{{TypeInformations}} shouldn't be passed along other job information. Marking
it {{Serializable}} has led in the past to problems where {{TypeInformations}},
which weren't serializable, were sent over the wire and, thus, made the program
fail. As far as I know, there is no real need to make the {{TypeInformation}}
serializable and, thus, re-establishing a harder contract will prevent possible
errors in the future.
> Make TypeInformation non-serializable again by removing Table API's need for
> it
> -------------------------------------------------------------------------------
>
> Key: FLINK-2684
> URL: https://issues.apache.org/jira/browse/FLINK-2684
> Project: Flink
> Issue Type: Improvement
> Components: Table API
> Reporter: Till Rohrmann
> Priority: Minor
>
> Currently, the {{TypeInformations}} must be serializable because they are
> shipped with UDFs of the Table API to the TMs. There the Table API code is
> generated and compiled. By generating the code on the client and shipping the
> code as strings, we could get rid of this dependency. As a consequence, the
> {{TypeInformations}} can be non-serializable again, as they were intended to
> be.
> Maybe [~aljoscha] can provide some more implementation details here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
