[
https://issues.apache.org/jira/browse/FLINK-16729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-16729:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Offer an out-of-the-box Set serializer
> --------------------------------------
>
> Key: FLINK-16729
> URL: https://issues.apache.org/jira/browse/FLINK-16729
> Project: Flink
> Issue Type: New Feature
> Components: API / Type Serialization System
> Affects Versions: 1.11.0
> Reporter: Nico Kruber
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> Currently, Set types are serialized by Kryo by default, since Flink does not
> come with an own SetSerializer (only one for maps). While the MapSerializer
> can be easily adapted to cover sets instead, I think, this should be
> available by default to get the maximum performance out of Flink (kryo is
> slow!)
>
> When this is added, however, we need to provide a migration path for old
> state (or not use the new SetSerializer by default but offer to opt-in). This
> may need further investigation as to whether it is possible to migrate from
> kryo automatically and whether we can check potential changes to the
> encapsulated entry class.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
