You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/05/28 06:13:00 UTC
[jira] [Updated] (FLINK-17657) Fix reading BIGINT UNSIGNED type
field not work in JDBC
[ https://issues.apache.org/jira/browse/FLINK-17657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jark Wu updated FLINK-17657:
----------------------------
Summary: Fix reading BIGINT UNSIGNED type field not work in JDBC (was: jdbc not support read BIGINT UNSIGNED field)
> Fix reading BIGINT UNSIGNED type field not work in JDBC
> -------------------------------------------------------
>
> Key: FLINK-17657
> URL: https://issues.apache.org/jira/browse/FLINK-17657
> Project: Flink
> Issue Type: Bug
> Components: Connectors / JDBC
> Affects Versions: 1.10.0, 1.10.1
> Reporter: lun zhang
> Assignee: Leonard Xu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Attachments: env.yaml, excetion.txt
>
>
> I use sql client read mysql table, but I found I can't read a table contain `BIGINT UNSIGNED` field. It will
> Caused by: java.lang.ClassCastException: java.math.BigInteger cannot be cast to java.lang.Long
>
> MySQL table:
>
> create table tb
> (
> id BIGINT UNSIGNED auto_increment
> primary key,
> cooper BIGINT(19) null ,
> user_sex VARCHAR(2) null
> );
>
> my env yaml is env.yaml .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)