Josh Suereth

yeah, so I'd like to see a legit test case before we open this, otherwise it should be closed.

Another user request for this: https://cloud-native.slack.com/archives/C014L2KCTE3/p1669739859064699?thread_ts=1669652480.479969&cid=C014L2KCTE3

Wanted to add another comment about things we should likely be exposing to users with this change (once specification is written and publicized): - `ExemplarReservoirFactory` would be exposed in some...

I think if this API is complementary to the existing API, it'd be a great addition. This even goes into some discussions we've had, specification level, around how to adapt...

The specification itself is much cleared up and easier to follow. Thanks for all the fixes and explicit stability markers. The current prototype only include the propagator itself but not...

This would be a huge breaking change for OTLP proto handling. Right now, we explicitly disallow duplicates and allow implementations to treat the list as a `map`. The explicit reason...

I understand, but someone has to pay that cost at some point. Right now this would be a large breaking change for OTLP, in my opinion unacceptably large.

> Given the amount of concerns raised (very valid ones!), it maybe better to find a balance - the OTel API (bridge)/SDK can avoid de-duplication logic, and that'd meet the...

The issue is actually in `Defaults.itSettings`. These are added _after_ the autoplugin settings, and the notion of "itSettings" should probably be translated into Autoplugins, so you can depend on their...

I was assuming this was prohibitively expensive. If not, I think we have a way forward here for stabilzation.