Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Won't Do
-
1.4.0
-
None
Description
As we all known , see https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-type-conversions.html
SQL data type BIGINT in mysql represents UNSIGNED BIGINT by default , it can receive value from some columns typed Long or BigInteger if we use java/scala driver to write data into db.
| MySQL Type Name | Return value of GetColumnTyneName | Return value of GetColumnClassName |
|---|---|---|
| BIGINT[(M)] [UNSIGNED] | BIGINT [UNSIGNED] | java.lang.Long, if UNSIGNED java.math.BigInteger |
But now , in Flink SQL BIGINT just represents SIGNED BIGINT, that to say it can only receive value from some columns typed Long .
all supported types of the Table API defined in this class org.apache.flink.table.api.Types
so if we should let BIGINT in Flink SQL match the BIGINT in some SQL Engine , like MySQL.
Or, as a new feature, support a new FLINK SQL type named BIGINTEGER for Java type Biginteger and also into MySQL BIGINT?