birschick-bq commented on PR #3315: URL: https://github.com/apache/arrow-adbc/pull/3315#issuecomment-3330435381
> @birschick-bq How do you see this evolving as time goes on? It sounds like the file exporter in the `Listeners` project isn't fully compatible with the one in the `Exporters` project -- so switching to `Exporters` would be a breaking change? Then any new C#-based driver would have to decide which of the two to use/support? @CurtHagenlocher My feeling is that the OTel Exporter mechanism is better suited to end-user applications because it is static/global and works better with an end application's lifetime. Consumers of Exporters/Listeners do not inherit from these classes, but just instantiate an instance. So from the driver's standpoint, it shouldn't matter how the telemetry is observed. They could actually mix-and-match an Exporter (OTLP) and a Listener (File) in a single driver. Ideally, I would like to have a Listener version of OTLP where I could re-use the OTel implementation without the overhead/restrictions of the Exporters interface. I will create an issue placeholder to deal with this further. Thanks for your help/input. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
