binarycat-dremio opened a new issue, #4501: URL: https://github.com/apache/arrow-adbc/issues/4501
## Summary The Go Flight SQL driver currently writes `adbcfile` trace output under a default path derived from `os.UserConfigDir()` plus `.adbc/traces`. Other ADBC config artifacts already use different platform-specific conventions, for example: - driver manifests under `ADBC/Drivers` - connection profiles under `ADBC/Profiles` ## Problem This means trace files are currently stored under a separate `.adbc` layout instead of following the existing ADBC config-directory conventions. That inconsistency came up during review of the Flight SQL telemetry documentation PR. ## Scope - Review the current default trace-file location used by the Go driver - Decide whether traces should move under the existing ADBC config layout - If so, refactor the path selection to use a shared or consistent convention across manifests, profiles, and driver-managed trace output - Update docs/tests as needed ## Context - Related docs PR: #4500 - Current implementation reference: `go/adbc/driver/internal/driverbase/rotating_file_writer.go` - Related config-path logic: `c/driver_manager/adbc_driver_manager.cc`, `c/driver_manager/adbc_driver_manager_profiles.cc`, `rust/driver_manager/src/search.rs` -- 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]
