XB10-2715: Avoid redundant tableSyncHandler calls during wildcard get resolution#449
Open
WellPeter wants to merge 1 commit into
Open
XB10-2715: Avoid redundant tableSyncHandler calls during wildcard get resolution#449WellPeter wants to merge 1 commit into
WellPeter wants to merge 1 commit into
Conversation
… resolution
Reason for change: During wildcard get resolution, the rbus implementation may call the tableSyncHandler multiple times for the same parameter,
which can lead to unnecessary overhead, potential performance issues or even memory corruption.
Test Procedure: Tested and verified
Priority: P1
Risks: Low
Signed-off-by: Petro Krynytskyi <33368124+WellPeter@users.noreply.github.com>
df88a2c to
e022c73
Compare
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
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.
Reason for change: During wildcard get resolution, the rbus implementation may call the tableSyncHandler multiple times for the same parameter,
which can lead to unnecessary overhead, potential performance issues, or even memory corruption.
Test Procedure: Tested and verified
Priority: P1
Risks: Low