Optimize encoding maps#4494
Merged
Merged
Conversation
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
dtunikov
reviewed
Jun 26, 2026
| columnCharset []uint64, | ||
| enumMap map[int][]string, | ||
| setMap map[int][]string, | ||
| colEncodings *[]encoding.Encoding, |
Collaborator
There was a problem hiding this comment.
nit: I think standart go way would be to return []encoding.Encoding instead of passing *[]encoding.Encoding (similar to how append function works)
dtunikov
approved these changes
Jun 26, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Follow-up to #4436
Optimize building two extra maps per event on go-mysql side when re-encoding won't be needed (common case)