From 6ae8ee7f586fcc97c1ca7b5b05aee3aee81a54db Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20Neum=C3=BCller?= Date: Tue, 10 Nov 2020 17:05:58 +0100 Subject: [PATCH] Remove ordering reqirement for attributes. (#1212) * Remove ordering for attributes. * Fill in CHANGELOG link --- CHANGELOG.md | 2 ++ specification/common/common.md | 2 -- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 8f878de5975..66ee5322d27 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -70,6 +70,8 @@ New: Updates: +- Remove ordering SHOULD-requirement for attributes + ([#1212](https://github.com/open-telemetry/opentelemetry-specification/pull/1212)) - Make `process.pid` optional, split `process.command_args` from `command_line` ([#1137](https://github.com/open-telemetry/opentelemetry-specification/pull/1137)) - Renamed `CorrelationContext` to `Baggage`: diff --git a/specification/common/common.md b/specification/common/common.md index 0352f819abf..fca4b007a16 100644 --- a/specification/common/common.md +++ b/specification/common/common.md @@ -21,8 +21,6 @@ Attributes are a list of zero or more key-value pairs. An `Attribute` MUST have i.e. it MUST NOT contain values of different types. For protocols that do not natively support array values such values SHOULD be represented as JSON strings. -Attributes SHOULD preserve the order in which they're set. - Attribute values expressing a numerical value of zero, an empty string, or an empty array are considered meaningful and MUST be stored and passed on to processors / exporters.