You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2023/01/18 14:35:00 UTC
[jira] [Comment Edited] (FLINK-29863) Properly handle NaN/Infinity in OpenAPI spec
[ https://issues.apache.org/jira/browse/FLINK-29863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678262#comment-17678262 ]
Chesnay Schepler edited comment on FLINK-29863 at 1/18/23 2:34 PM:
-------------------------------------------------------------------
We could add a custom serializer for all doubles that converts NaN/infinity to null. We can register this centrally so it applies to the entire REST API.
was (Author: zentol):
We could do is add a custom serializer for all doubles that converts NaN/infinity to null. We can register this centrally so it applies to the entire REST API.
> Properly handle NaN/Infinity in OpenAPI spec
> --------------------------------------------
>
> Key: FLINK-29863
> URL: https://issues.apache.org/jira/browse/FLINK-29863
> Project: Flink
> Issue Type: Bug
> Components: Documentation, Runtime / REST
> Affects Versions: 1.15.0
> Reporter: Chesnay Schepler
> Priority: Major
> Fix For: 1.17.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)