[
https://issues.apache.org/jira/browse/FLINK-28697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625038#comment-17625038
]
Josh Mahonin commented on FLINK-28697:
--------------------------------------
Agreed, the use of mismatched JVM versions is not ideal. In this case the major
versions were the same (16), but due to some ideosyncrasies in container
packaging, they were not the exact same JVM version.
The other classes in that package all have a serialVersionUID set (last I
checked).
I’ll also note the Flink style guide says all serializable classes must declare
a serialVersionUID
[https://flink.apache.org/contributing/code-style-and-quality-java.html#java-serialization]
> MapDataSerializer doesn't declare a serialVersionUID
> ----------------------------------------------------
>
> Key: FLINK-28697
> URL: https://issues.apache.org/jira/browse/FLINK-28697
> Project: Flink
> Issue Type: Bug
> Components: API / Type Serialization System
> Affects Versions: 1.15.1
> Reporter: Josh Mahonin
> Priority: Major
> Labels: pull-request-available
>
> MapDataSerializer doesn't declare a serialVersionUID, which can manifest as a
> InvalidClassException when attempting to serialize with different JREs for
> compilation / runtime.
> {code:java}
> Caused by: java.io.InvalidClassException:
> org.apache.flink.table.runtime.typeutils.MapDataSerializer; local class
> incompatible: stream classdesc serialVersionUID = 2533002123505507000, local
> class serialVersionUID = 1622156938509929811 {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)