[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
