MySQL support for bulk inserts, deletes by reading multiple event rows #103
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Instead of assuming the ifrst index of event.rows contains the full pyload of the binlog event, we iterate through the full event, picking up additional inserts, deletes ..
KDMW-IO
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
MySQL support for bulk inserts, deletes by reading multiple event
Description
Refactor binlog event processing to support bulk operations.
Instead of assuming the ifrst index of event.rows contains the full pyload of the binlog event, we iterate through the full event, picking up additional inserts, deletes.
Testing
Tested against an a hosted MySQL instance. Flows from our backend that were leading to meilisearch being out of sync are now working as expected.
Related Issue
#93