Fix/Ecto high number of batches #126
Merged
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
As stated by the Elixir doc, Maps’ keys do not follow any ordering. In practice is is especially true starting at 32 elements. Therefore the batches' results were not in the same order as the batches' keys which resulted in an error when fetching a batch result.
|
Great catch! |
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.
Fix Dataloader.Ecto.run_batches/1 function for high number of batches
As stated by the Elixir doc, Maps’ keys do not follow any ordering. In practice it is especially true starting at 32 elements.
Therefore the batches' results were not in the same order as the batches' keys which resulted in an error when fetching a batch result.