[
https://issues.apache.org/jira/browse/FLINK-21386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292765#comment-17292765
]
Kezhu Wang commented on FLINK-21386:
------------------------------------
[~chesnay] Combination of #1 and #3 could solve this. In construction of
{{FromElementsFunction}}, only {{elements}} will pass to constructor. In stream
graph generation, {{setOutputType}} will be called with correct serializer and
we can generate serialized data in that stage. In case that incorrect
serializer will success in serialization(eg. kryo case as I tested),
combination of #1 and #2 could also solve this. But there might be some waste
and indeterminate for other incorrect serializer, I plan to no serializer in
construction in first place.
> FromElements ignores returns()
> ------------------------------
>
> Key: FLINK-21386
> URL: https://issues.apache.org/jira/browse/FLINK-21386
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Affects Versions: 1.13.0
> Reporter: Chesnay Schepler
> Priority: Critical
> Labels: usability
> Fix For: 1.13.0
>
>
> StreamExEnv#fromElements eagerly serializes data with the automatically
> determined serializer. This can result in errors for example when generic
> avro records are used, because it will default to Kryo.
> Subsequent calls to returns() have no effect because the typeinformation is
> never forwarded to the function.
> Annoyingly the fact that it serializes data isn't logged anywhere. and there
> doesn't seem to be a way to change the serializer except by using
> fromCollection() instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
