Remove underspecified and unused Span decorator from Trace SDK.

open-telemetry · Apr 4, 2023 · 77c8edd · 77c8edd
1 parent 6ba4a82
commit 77c8edd
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 3 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -11,9 +11,11 @@ release.
 
 ### Traces
 
-* Clarify required parent information in ReadableSpan. Technically a relaxation,
+- Clarify required parent information in ReadableSpan. Technically a relaxation,
   but previously it was easy to overlook certain properties were required.
   [#3257](https://github.com/open-telemetry/opentelemetry-specification/pull/3257)
+- Remove underspecified and unused Span decorator from Trace SDK.
+  ([#3363](https://github.com/open-telemetry/opentelemetry-specification/pull/3363))
 
 ### Metrics
 

diff --git a/specification/trace/sdk.md b/specification/trace/sdk.md
@@ -470,8 +470,7 @@ Each processor registered on `TracerProvider` is a start of pipeline that consis
 of span processor and optional exporter. SDK MUST allow to end each pipeline with
 individual exporter.
 
-SDK MUST allow users to implement and configure custom processors and decorate
-built-in processors for advanced scenarios such as tagging or filtering.
+SDK MUST allow users to implement and configure custom processors.
 
 The following diagram shows `SpanProcessor`'s relationship to other components
 in the SDK: