[
https://issues.apache.org/jira/browse/FLINK-36812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17942093#comment-17942093
]
Ruan Hang commented on FLINK-36812:
-----------------------------------
This issue is not a blocker for jdbc-3.3.0. Move to a new version.
> The flink jdbc connector's 'scan.partition.column' supports the varchar field
> type.
> -----------------------------------------------------------------------------------
>
> Key: FLINK-36812
> URL: https://issues.apache.org/jira/browse/FLINK-36812
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / JDBC
> Affects Versions: jdbc-3.2.0
> Reporter: ouyangwulin
> Priority: Major
> Fix For: jdbc-3.3.0
>
>
> The scan.partition.column must be a numeric, date, or timestamp column from
> the table in question. But in many cases, tables don't have numeric, date,
> or timestamp columns, and we need to support a varchar field to make
> concurrent ingest useful in a wider range of scenarios.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
