You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the usage question you have. Please include as many useful details as possible.
This is a governance question.
OpenTelemetry has developed a project to transmit telemetry using a particular protocol based around the Arrow-Go library and Arrow IPC.
This is a CNCF-hosted project. We are proposing to name the protocol "OTel-Arrow". OpenTelemetry collector components would be named, for example otelarrowreceiver and otelarrowexporter, as described in open-telemetry/opentelemetry-collector-contrib#26491.
Does the Apache Arrow project have any reservations or guidelines about the use of this name? This concern was raised during internal review by OpenTelemetry contributors. Thank you!
Component(s)
Other
The text was updated successfully, but these errors were encountered:
Describe the usage question you have. Please include as many useful details as possible.
This is a governance question.
OpenTelemetry has developed a project to transmit telemetry using a particular protocol based around the Arrow-Go library and Arrow IPC.
This is a CNCF-hosted project. We are proposing to name the protocol "OTel-Arrow". OpenTelemetry collector components would be named, for example
otelarrowreceiver
andotelarrowexporter
, as described in open-telemetry/opentelemetry-collector-contrib#26491.The repository where this has been developed: https://github.com/open-telemetry/otel-arrow
Does the Apache Arrow project have any reservations or guidelines about the use of this name? This concern was raised during internal review by OpenTelemetry contributors. Thank you!
Component(s)
Other
The text was updated successfully, but these errors were encountered: