[
https://issues.apache.org/jira/browse/FLINK-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Wosiński updated FLINK-9557:
------------------------------------
Description:
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.
was:
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.
> FlinkTypeFactory should support BigInteger type
> -----------------------------------------------
>
> Key: FLINK-9557
> URL: https://issues.apache.org/jira/browse/FLINK-9557
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: Dominik Wosiński
> 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)
