PatrickRen closed issue #3108: Error on Postgres-CDC using incremental snapshot
with UUID column as PK
URL: https://github.com/apache/flink-cdc/issues/3108
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
PatrickRen commented on issue #3108:
URL: https://github.com/apache/flink-cdc/issues/3108#issuecomment-2044202366
Closing this issue as it has been migrated to [Apache
Jira](https://issues.apache.org/jira).
--
This is an automated message from the Apache Git Service.
To respond to the mes
loserwang1024 commented on issue #3108:
URL: https://github.com/apache/flink-cdc/issues/3108#issuecomment-2033865296
@olivier-derom It seems a bug, could you please create a [jira
](https://issues.apache.org/jira/browse/FLINK-34952)and fix it? If you don't
have time, I'd like to help you t
olivier-derom commented on issue #3108:
URL: https://github.com/apache/flink-cdc/issues/3108#issuecomment-2003696012
@drorventura
As per my last reply, I indeed created my own functions that are able to
calculate the min/max of UUID's, similar to how you defined them.
While this allow
drorventura commented on issue #3108:
URL: https://github.com/apache/flink-cdc/issues/3108#issuecomment-2003458861
@olivier-derom were you able to make that work?
if not then this should solve your missing functions:
```
create or replace function min(uuid, uuid)
returns u
olivier-derom commented on issue #3108:
URL: https://github.com/apache/flink-cdc/issues/3108#issuecomment-1980957733
I figured this is a limitation of Postgres and not Flink-CDC, so tried to
create my own min(uuid, uuid) and max(uuid, uuid) as well as aggregate
min(uuid) and max(uuid).
T
olivier-derom opened a new issue, #3108:
URL: https://github.com/apache/flink-cdc/issues/3108
A majority of our Postgres databases use UUIDs as primary keys.
When we enable 'scan.incremental.snapshot.enabled = true', Flink-CDC will
try to split into chunks.
The splitTableIntoChunks fun
