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

Clarify SpanExporter#ForceFlush is required #2654

Merged

Conversation

dyladan
Copy link
Member

@dyladan dyladan commented Jul 8, 2022

Fixes #2652

Changes

  • Clarify there are 3 methods, not 2, in the SpanExporter interface

@dyladan dyladan requested review from a team July 8, 2022 19:50
@arminru arminru added area:sdk Related to the SDK spec:trace Related to the specification/trace directory labels Jul 12, 2022
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`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not blocking, maybe we can just remove this sentence? It mentioned metrics in a tracing spec (also it might be inaccurate because LogExporter does exist https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/logging-library-sdk.md#logexporter).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:sdk Related to the SDK spec:trace Related to the specification/trace directory
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SpanExporter interface inconsistency
8 participants