Allow to incrementally adopt new ID format in distributed system #7343
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.
In order to adopt the new ID format in a distributed system, you need to
Currently this adoption strategy wouldn't be possible, because while the new Default Serializer supports parsing both formats, it only outputs the new format, making it impossible to only update one service. The Legacy serializer only handles the old format, so it also can't be used to start adopting the new format.
This PR introduces a new option
outputNewIdFormat
forAddDefaultNodeIdSerializer
. This allows you in the first step to update all your services toAddDefaultNodeIdSerializer(outputNewIdFormat: false)
and once all services are updated, switch to outputting the new ID format viaAddDefaultNodeIdSerializer()
.