zeroshade commented on issue #2210: URL: https://github.com/apache/arrow-adbc/issues/2210#issuecomment-2839251179
Nah, it's definitely not required for an initial solution. It's good to keep the scope smaller where possible. Essentially, while the initial work will enable exporting proper OTel traces/spans/metrics for what happens inside the driver and wire things up. It won't necessarily allow for easily connecting the spans from the application *using* the driver to the spans *inside* the driver. That's what the options will be needed for. That said, because of the way OTel works for Golang, anyone using the Go interface directly (instead of going through the C ADBC API) would be able to easily connect the traces through the context parameters. So that will be more than sufficient to test after we get the initial solution working. We can then work on defining and implementing some standard options that we would be able to propagate through the drivers as a secondary piece of work. -- 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
