Clarify SpanExporter#ForceFlush is required (#2654)

Co-authored-by: Armin Ruech <[email protected]>
open-telemetry · Jul 18, 2022 · 6d66ec5 · 6d66ec5
1 parent 6ce6220
commit 6d66ec5
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -14,6 +14,8 @@ release.
 - Clarify the return of `Export(batch)` in the Batch Span Processor and exporter
   concurrency ([#2452](https://github.com/open-telemetry/opentelemetry-specification/pull/2452))
 - Clarify that Context should not be mutable when setting a span ([#2637](https://github.com/open-telemetry/opentelemetry-specification/pull/2637))
+- Clarify that `ForceFlush` is a required method on `SpanExporter` interface.
+  ([#2654](https://github.com/open-telemetry/opentelemetry-specification/pull/2654)).
 
 ### Metrics
 

diff --git a/specification/trace/sdk.md b/specification/trace/sdk.md
@@ -602,8 +602,8 @@ primarily a simple telemetry data encoder and transmitter.
 
 ### Interface Definition
 
-The exporter must support two functions: **Export** and **Shutdown**. In
-strongly typed languages typically there will be 2 separate `Exporter`
+The exporter MUST support three functions: **Export**, **Shutdown**, and **ForceFlush**.
+In strongly typed languages typically there will be 2 separate `Exporter`
 interfaces, one that accepts spans (SpanExporter) and one that accepts metrics
 (MetricsExporter).