binarycat-dremio opened a new issue, #4487: URL: https://github.com/apache/arrow-adbc/issues/4487
## What happened? The Go Flight SQL driver accepts tracing configuration, but the core query path does not emit trace spans. In the affected implementation: - the main `Open` / `Prepare` / `ExecuteQuery` / `ExecuteUpdate` path did not start spans - the Flight SQL database close path did not delegate to `DatabaseImplBase.Close()`, so tracer shutdown and exporter flush did not run As a result, tracing could be configured successfully but no trace output was produced for normal Flight SQL query execution. ## What did you expect to happen? When tracing is enabled for the Go Flight SQL driver, the normal connection and query path should emit spans and configured exporters should flush their output when the database is closed. ## How can we reproduce it? 1. Create a Flight SQL database with tracing enabled using the `adbcfile` exporter. 2. Open a connection. 3. Prepare and execute a query. 4. Close the statement, connection, and database. 5. Observe that no trace output is produced. ## Additional context A fix should: - add spans for the core Flight SQL operations used by normal query execution - ensure Flight SQL database close handling flushes configured trace exporters -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
