Hi,
I have a flink app that has a long development roadmap and will be worked
on by multiple people. We store state for a long period of time (~weeks)
and during that time there is a possibility that the long list of classes
registered with Kryo might change.
For example:
*env.registerTypeWithKr
Hi, maybe you can see here[1].
When a record is written into the jdbc sink, it will first be collected with
previous records as a batch. If the size of the input records exceeds the
limit, the code you mentioned will work. It first emits the upsert
records(insert or update_after), and then emit
Hello,
I have postgres as source and mysql as sink. The user authenticating with
mysql does _not_ have DELETE privileges.
In some cases, flink throws error because it is trying to _delete_ records
and the user does not have privilege. In most cases (of the same job),
upsert is working as expected
