Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix id when common tags are after metric data #1439

Merged
merged 2 commits into from
Apr 28, 2022

Conversation

brharrington
Copy link
Contributor

If the common tags were after the metric data in the batch
json payload, then the tags in the tuple would get updated,
but not the id. This change fixes it so that the id is
updated based on the final tags for a metric. Also updates
the behavior so the conflicts resolution is consistent for
both paths.

If the common tags were after the metric data in the batch
json payload, then the tags in the tuple would get updated,
but not the id. This change fixes it so that the id is
updated based on the final tags for a metric. Also updates
the behavior so the conflicts resolution is consistent for
both paths.
@brharrington brharrington added this to the 1.7.0 milestone Apr 28, 2022
@brharrington brharrington requested a review from manolama April 28, 2022 21:23
@brharrington brharrington merged commit 99afe17 into Netflix:main Apr 28, 2022
@brharrington brharrington deleted the pub-id branch April 28, 2022 21:41
manolama pushed a commit to manolama/atlas that referenced this pull request May 22, 2024
If the common tags were after the metric data in the batch
json payload, then the tags in the tuple would get updated,
but not the id. This change fixes it so that the id is
updated based on the final tags for a metric. Also updates
the behavior so the conflicts resolution is consistent for
both paths.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants