Joshua MacDonald

Thank you @jade-guiton-dd. Having received some feedback, I will return this to draft and work on improving it. I do want to address the central questions, and why I think...

> Do nothing and assume this is a qualified success. Sounds good and conservative. I'd say it gives room to improve in the future, though nothing's easy.

@pyohannes @zeitlinger As both of you have approached this topic from the perspective of how to report timeseries deletion, I'd like to involve you in thinking about how to update...

This looks good to me. I do not mind all the `Get()` calls given how much simpler/safer this appears (i.e., the pointer removals).

We've been careful to avoid describing a "Rust-based Collector" in favor of the term "pipeline" in https://github.com/open-telemetry/otel-arrow/blob/main/docs/phase2-design.md because our goal is to understand how an end-to-end implementation using OTAP performs....

> What constraints are leading to the Rust requirement for this pipeline? Processing performance/memory safety? Arrow library support in Rust vs. Go? Etc. "All of the above". The choice of...

@jpkrohling We hope that https://github.com/open-telemetry/otel-arrow/blob/main/docs/project-phases.md will address your concerns. I feel that I owe you an updated diagram, since the one you copied above is from the OTEP.

Completed.

I believe we can mark this done. HTTP and gRPC middleware support has been added. At this time there are no core middleware components, but one named limitermiddleware has been...

Note to incorporate feedback in https://github.com/open-telemetry/opentelemetry-collector/pull/12953#pullrequestreview-2856098381