OK that makes sense, I can see how sharing the same Assigner instance
between partitions could be tricky, specially if you're handling state.
Good to hear this is not expected behaviour, I'm using Flink's
JDBCAppendTableSink so nothing particularly unconventional (and I get the
same result with JD
You can use the Timestamp Assigner / Watermark Generator in two different
ways: Per Kafka Partition or per parallel source.
I would usually recommend per Kafka Partition, because if the read position
in the partitions drifts apart (for example some partitions are read at the
tail, some are read a
Hi all,
It was a bit tricky to figure out what was going wrong here, hopefully
someone can add the missing piece to the puzzle.
I have a Kafka source with a custom AssignerWithPeriodicWatermarks
timestamp assigner. It's a copy of the AscendingTimestampExtractor with a
log statement printing each
