joellubi opened a new pull request, #1649: URL: https://github.com/apache/arrow-adbc/pull/1649
Draft for a few info_codes that would be useful to have defined in ADBC. These are all adaptations of info_codes already defined in Flight SQL, but they would also be helpful for ADBC clients to determine what capabilities are available when connecting to the backend. Although there are many more info_codes defined in Flight SQL, these are the ones that are mostly clearly relevant for ADBC clients. The others I considered adding from Flight SQL were: - `FLIGHT_SQL_SERVER_TRANSACTION` - `FLIGHT_SQL_SERVER_CANCEL` Transactions seem to be mediated via get/set options, so I didn't add a code for it. Although it may still be useful to report max isolation level or something similar. Looking for feedback on this. Reporting on support for cancelation seems like it could be useful. I don't know if this would be boolean or if it is necessary to distinguish between different kind of cancelation (like maybe connection vs statement?). Also could use some feedback here. Finally I wasn't sure if the keys should be prefixed `ADBC_INFO_VENDOR_`, `ADBC_INFO_DRIVER_`, or perhaps something else. I could see how either could make sense in different situations. If it makes sense to proceed with this then I can port these to the other ADBC interface definitions as well. -- 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]
