fix(dataset): prevent duplicate metadata keys when renaming#2547
Merged
fix(dataset): prevent duplicate metadata keys when renaming#2547
Conversation
abdimo101
changed the title
abdimo101
changed the title
abdimo101
changed the title
nitrosx
approved these changes
Feb 17, 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.
Description
This PR fixes an issue where renaming scientific metadata keys in the V4 dataset would create duplicate metadata key records instead of updating the existing one.
The problem occurred because the default content-type was set to "application/merge-patch+json", which merges new keys with existing ones rather than replacing them. By changing the default content-type to "application/json", users must now provide all the metadata keys for the specific dataset when updating, as the new metadata will replace the old ones completely.
Users can still use "application/merge-patch+json" by explicitly setting the content-type header if they need merge behavior.
Motivation
Fixes
Changes:
Tests included
Documentation
official documentation info