[jira] [Commented] (FLINK-29863) Properly handle NaN/Infinity in OpenAPI spec

["Austin Cawley-Edwards (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-29863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17646692#comment-17646692 ] 

Austin Cawley-Edwards commented on FLINK-29863:
-----------------------------------------------

What might be the issue of fixing the API to not return NaN/infinity instead?

 

> Numeric values that cannot be represented as sequences of digits (such as Infinity and NaN) are not permitted.

 

https://www.ecma-international.org/publications-and-standards/standards/ecma-404/

> 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)