`ADBC_INFO_DRIVER_ARROW_VERSION` is useful?

[eitsupi]

What feature or improvement would you like to see?

The spec says the following about ADBC_INFO_DRIVER_ARROW_VERSION:

The driver Arrow library version (type: utf8).

Currently, the drivers in this repository seem to report the built-in arrow-go or nanoarrow version.

However, compared to before, there are now many different implementations of Apache Arrow format, and the ecosystem has expanded, with arrow-go, which was previously managed as the main monorepo, migrating to its own version, so it is very difficult to guess what the version is just by seeing it reported.

I'm wondering whether this field is useful in its current state and whether it would be worth updating it to encourage a stricter format (e.g., including the implementation language and arrow library name, like go github.com/apache/arrow-go/v18 v18.5.0).
Or maybe there's value in simply displaying the versions of the Arrow format that are supported?

[lidavidm]

Maybe we can use this for Arrow format, and add new keys for library name and library version?

[eitsupi]

Maybe we can use this for Arrow format, and add new keys for library name and library version?

It depends on the purpose of this key, but if we envision a use case where a tool needs to compare format versions, I suspect that an int64 would be more convenient than a string (like ADBC_INFO_DRIVER_ADBC_VERSION).
In that case, would it be better to define a separate key rather than reusing this one?

arrow-adbc/c/include/arrow-adbc/adbc.h

Lines 515 to 528 in d380961

	/// \brief The driver Arrow library version (type: utf8).
	///
	/// \see AdbcConnectionGetInfo
	#define ADBC_INFO_DRIVER_ARROW_VERSION 102
	/// \brief The driver ADBC API version (type: int64).
	///
	/// The value should be one of the ADBC_VERSION constants.
	///
	/// \since ADBC API revision 1.1.0
	/// \see AdbcConnectionGetInfo
	/// \see ADBC_VERSION_1_0_0
	/// \see ADBC_VERSION_1_1_0
	#define ADBC_INFO_DRIVER_ADBC_VERSION 103

[lidavidm]

True. So maybe this should be version string, and we can add a separate variable for library name, and we can consider if format version is actually useful