[
https://issues.apache.org/jira/browse/FLINK-19869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser reopened FLINK-19869:
------------------------------------
Assignee: (was: Bobby Richard)
After discussion with [~twalthr] this has been reverted:
master: fa199c1b51455ecb44c1869154f9452facd43403
release-1.16: a342e7f048c3cf06eba600626866d69fe7ef015a
> Flink SQL JDBC connector for Postgres can't handle UUID datatype
> ----------------------------------------------------------------
>
> Key: FLINK-19869
> URL: https://issues.apache.org/jira/browse/FLINK-19869
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / JDBC
> Affects Versions: 1.15.0
> Reporter: Jingwei Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> Problem:
> UUID is not a SQL standard type. But it is supported by Postgres as an
> internal type which postgres client will help to convert to java.util.UUID
> when queried. However, it seems flink doesn't support it as a sql extension
> in PostgresCatalog. There is no uuid serializer provided for it, either. So
> if I want to filter a result set and put the filter result back to a table
> with same schema with uuid column type in it. I will have problem.
> Proposal:
> Handle UUID in postgres as a SQL extension. Use the DataTypes.RAW to wrap its
> original class info and its serializer so as to expose it as a RAW
> JDBCType(only in postgres) in PostgresCatalog.
> And meanwhile, for PostgresRowConverter, we could use BinaryRawValueData to
> handle those SQL extension for byte serialization/deserialization.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
