Hi All, While this has been brought up and discussed before, we haven't had a good consensus. For some background:
ODBC/JDBC utilize User and System-level configurations (that can be adjusted by some environment variables also!) to control where drivers can be found and how they are loaded. By contrast, ADBC has no defined configuration format or locations which means driver managers must always provide a full path to a dynamic lib for a driver. As a result, the developer experience for using drivers isn't particularly straightforward and the initial starting point is kinda difficult for many users. To this end, I've prototyped some ideas internally and have come up with a proposal for how we could leverage configuration manifests for drivers with ADBC. I've put together a google doc [1] with the proposal that I'm looking for feedback on from the community. After a few days, if there are no particular objects or specific problems brought up, I'll start implementing the ideas in the driver manager [2]. I don't think this really qualifies as a "format" change so I don't think we need to vote on this necessarily, but I have no problem with doing so if others think it qualifies and should be voted on. Looking forward to any feedback people might have, thanks all! --Matt [1]: https://docs.google.com/document/d/1ANeoDI7MCi9xFt_q8z726xKweWS2vgqO8Ut6BSTt5zM/edit?tab=t.0 [2]: https://github.com/apache/arrow-adbc/tree/main/c/driver_manager
