-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
-
0
-
0%
Which use case/requirement will be addressed by the proposed feature?
I am using Debezium to record every changes in every table in my database. I need to be able to set a unique ordering key so that my worker can consume messages in the order they were published.
The issue as of now is that each table has a different ordering key causing my worker to throw SQL errors because of foreign keys issues.
Implementation ideas (optional)
A property to be able to set a unique ordering key value in the application.properties