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.
Hi!
What exactly is changing? In jobber.go the writeResult change to consider interate the origin source and batch to the target database using new methods of the backend that use SQL with insert multlples rows. It hence that pass a slice to the backend method and there split acording the batch size.
why? Some bulks of thousands of lines could speedup if some bulk "backend" methods its used.
and how it helps? By configuration, could speedup the velocity of insert in target database.
The overall architecture.
TODO: