[
https://issues.apache.org/jira/browse/FLINK-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509659#comment-16509659
]
ASF GitHub Bot commented on FLINK-9557:
---------------------------------------
Github user twalthr commented on the issue:
https://github.com/apache/flink/pull/6153
The change is also compliant to the JSON schema standard:
```
Note that JSON Schema vocabularies are free to define their own
extended type system. This should not be confused with the core data
model types defined here. As an example, "integer" is a reasonable
type for a vocabulary to define as a value for a keyword, but the
data model makes no distinction between integers and other numbers.
```
https://www.ietf.org/id/draft-handrews-json-schema-01.txt
> FlinkTypeFactory should support BigInteger type
> -----------------------------------------------
>
> Key: FLINK-9557
> URL: https://issues.apache.org/jira/browse/FLINK-9557
> Project: Flink
> Issue Type: New Feature
> Affects Versions: 1.5.0
> Reporter: Dominik Wosiński
> Assignee: Timo Walther
> Priority: Major
>
> Currently,
> {code:java}
> FlinkTypeFactory.typeInfoToSqlTypeName(typeInfo: TypeInformation[_]) {code}
> does not support _BigInteger_, and since this is default type returned by
> {code:java}
> JsonSchemaConverter.convert(String schema){code}
> for all fields with type: _integer_ this can be problematic for anyone who
> wants to force values to be of type Integer or Long.
> In 1.5.0 it is possible to register stream with _BigInteger_ as a type, but
> using this field in __SELECT query will cause it to fail due to problem above.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
