[FLINK-29863] Properly handle NaN/Infinity in OpenAPI spec

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.15.0
• Fix Version/s: 3.0.0
• Component/s: Documentation, Runtime / REST
• Assignee: Unassigned
• Reporter: Chesnay Schepler
• Created: 03/Nov/22 09:28
• Updated: 03/Sep/24 06:51

Description

Our OpenAPI spec maps all float/double fields to float64, but we at times also return NaN/infinity which can't be represented as such since the JSON spec doesn't support it.

One alternative could be to document it as an either type, returning either a float64 or a string.