Aesop Patch to send old values from mysql producer #65
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes are to enable old value propagation from mysql relay (producer). This is a flag based change, whereby in sample-mysql-relay this flag can be set. When enabled, in DBChangeEntry generic record which use to carry mysql-row field information (updated) will now have extra key: '_oldValue' (which will be a hash containing old values of changed field). The '_oldValue' column name depends on avro-schema defined.
In schema-generator utility, a command line parameter is added which can be used if someone wants to generate schema with '_oldValue' column (column name is user defined in parameter). This will update meta properties in avro-schema, mentioning '_oldValue' is special column (not mysql column).
At clients side, in AbstractEvent a new field stores the information of '_oldValue' from DataBus event and can be used if required.
@jagadeesh-huliyar
please have a look