Skip to content

Commit b71106a

Browse files
pellaredtrask
andauthored
[IMPORTANT] Extending attribute value types is no longer a breaking change (#4614)
Towards #4602 Per OTEP: https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/4485-extending-attributes-to-support-complex-values.md#why-doesnt-this-require-a-major-version-bump This basically reverts: - #3858 Before we did not have a consensus to extend the attribute value types. However, this has changed with: - #4485 Related proto PR: - open-telemetry/opentelemetry-proto#683 **As a follow-up I plan to create issues in all language repositories so that they can prepare their APIs and SDKs to extend the attribute value types.** --------- Co-authored-by: Trask Stalnaker <[email protected]>
1 parent ee70c3d commit b71106a

File tree

2 files changed

+3
-15
lines changed

2 files changed

+3
-15
lines changed

CHANGELOG.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,9 @@ release.
3131

3232
### Common
3333

34+
- ⚠️ **IMPORTANT**: Extending the set of standard attribute value types is no longer a breaking change.
35+
([#4614](https://github.com/open-telemetry/opentelemetry-specification/pull/4614))
36+
3437
### Supplementary Guidelines
3538

3639
### OTEPs

specification/common/README.md

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -83,21 +83,6 @@ reflects that LogRecord attributes are expected to model data produced from
8383
external log APIs, which do not necessarily have the same value type
8484
restrictions as the standard attribute definition.
8585

86-
Note: Extending the set of standard attribute value types is a breaking change.
87-
This was decided after extensive debate, with arguments as follows:
88-
89-
* Limiting the types of attribute values to a set which has proved sufficient
90-
during several years of OpenTelemetry's development is a useful guardrail for
91-
design. In taking additional value types off the table, we narrow the solution
92-
space and have more productive design conversations.
93-
* Upon proposing to extend support for complex value types, we received significant
94-
pushback. Limiting attribute value types to primitives and arrays of primitives
95-
simplifies data consumers' efforts to create search indexes and perform statistical
96-
analysis.
97-
* To address concerns over restricting standard attributes to primitive types, it was
98-
called out that complex types can be encoded as existing primitive types, such as
99-
representing datetime as a string or 64 bit integer.
100-
10186
### Attribute Limits
10287

10388
Execution of erroneous code can result in unintended attributes. If there are no

0 commit comments

Comments
 (0)