Fix tag relationship processing errors #1156
Merged
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.
Description
This PR addresses three issues:
These changes are related to the bug reported in #1144
Changes
Optimized
HasNewTag
function ininternal/service/tag_common/tag_common.go
:map[string]bool
withmap[string]struct{}
for better memory efficiency.Fixed tag relationship status when enabling:
Added status filtering when updating tag relationships:
Testing
Please test the following scenarios:
Verify that:
Additional Notes
This PR aims to resolve the issues mentioned in #1144 and improve overall tag handling in the system. Please review and provide feedback if any further changes are needed.