[MINOR] Reuse empty InternalSchema instance #7287
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
codope
added
schema-and-data-types
priority:minor
|
@codope thanks, it's rebased |
vamshigv
pushed a commit
to vamshigv/hudi
that referenced
this pull request
Dec 1, 2022
satishkotha
pushed a commit
that referenced
this pull request
Dec 13, 2022
fengjian428
pushed a commit
to fengjian428/hudi
that referenced
this pull request
Apr 5, 2023
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.
Change Logs
When schema evolution is disabled each instance of HoodieAvroDataBlock calls
getEmptyInternalSchema()which triggers creation of ArrayList and InternalSchema. We can easily avoid unnecessary object creation by reusing empty schema.Impact
Avoid unnecessary creation of empty InternalSchema
Risk level (write none, low medium or high below)
Low
Documentation Update
None
Contributor's checklist