[
https://issues.apache.org/jira/browse/FLINK-16811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bowen Li updated FLINK-16811:
-----------------------------
Description:
currently when JDBCInputFormat converts a JDBC result set row to Flink Row, it
doesn't check the type returned from jdbc result set. Problem is that object
from jdbc result set doesn't always match the corresponding type in relational
db. E.g. a short column in Postgres actually returns an Integer via jdbc. And
such mismatch can be db-dependent.
Thus, we introduce JDBCRowConverter interface to convert a db specific row from
jdbc to Flink row. Dbs should implement their own row converters.
was:
currently when JDBCInputFormat converts a JDBC result set row to Flink Row, it
doesn't check the type returned from jdbc result set. Problem is that object
from jdbc result set doesn't always match the corresponding type in relational
db. E.g. a short column in Postgres actually returns a Integer via jdbc. And
such mismatch can be db-dependent.
Thus, we introduce JDBCRowConverter interface to convert a db specific row from
jdbc to Flink row. Dbs should implement their own row converters.
> introduce JDBCRowConverter
> --------------------------
>
> Key: FLINK-16811
> URL: https://issues.apache.org/jira/browse/FLINK-16811
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / JDBC
> Reporter: Bowen Li
> Assignee: Bowen Li
> Priority: Major
> Fix For: 1.11.0
>
>
> currently when JDBCInputFormat converts a JDBC result set row to Flink Row,
> it doesn't check the type returned from jdbc result set. Problem is that
> object from jdbc result set doesn't always match the corresponding type in
> relational db. E.g. a short column in Postgres actually returns an Integer
> via jdbc. And such mismatch can be db-dependent.
> Thus, we introduce JDBCRowConverter interface to convert a db specific row
> from jdbc to Flink row. Dbs should implement their own row converters.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
