[
https://issues.apache.org/jira/browse/FLINK-40597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther closed FLINK-40597.
--------------------------------
Fix Version/s: 2.4.0
Assignee: dylanhz
Resolution: Fixed
Fixed in master: ac9d2aaaa39876481aebb5ceb20e6ef74398a4b0
> TypeExtractor rejects explicitly specified Types.UUID
> -----------------------------------------------------
>
> Key: FLINK-40597
> URL: https://issues.apache.org/jira/browse/FLINK-40597
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Reporter: dylanhz
> Assignee: dylanhz
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.4.0
>
>
> After FLINK-40490, explicitly specifying {{Types.UUID}} for a DataStream can
> cause type inference for a non-lambda {{MapFunction<UUID, String>}} or
> {{KeySelector}} to fail with {{Input mismatch: Basic type expected.}}
> {{TypeExtractor.validateInfo()}} validates basic types through
> {{{}BasicTypeInfo.getInfoFor(){}}}. However, {{UUID.class}} is intentionally
> excluded from that registry to preserve serializer compatibility, so a
> matching UUID input is incorrectly rejected.
> Explicit UUID input validation should work while keeping automatic UUID
> extraction unchanged. Automatic extraction is tracked separately in
> FLINK-40546.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
