CurtHagenlocher opened a new issue, #4231:
URL: https://github.com/apache/arrow-adbc/issues/4231
### What feature or improvement would you like to see?
Credentials are increasingly of limited duration, which introduces the
possibility of them expiring in the middle of an operation. While one approach
is to give the driver enough information so that it can refresh the credential
on its own, there are systems where such delegation is difficult or impossible.
For these cases, it would be nice for the driver to call back into the host to
ask for an updated credential.
One possible approach:
```
/// \brief A credential handler function.
///
/// The handler must not call any ADBC functions other than the
/// ConnectionSetOption functions and releasing the warning.
///
/// There are no requirements on ordering or concurrency of calls to the
/// handler; the driver may call the handler at any time from any thread,
/// including calling the handler concurrently.
///
/// \param[in] details Additional details about the credential required.
/// The application is responsible for releasing the details, but the
/// pointer itself will not be valid after the handler returns.
/// \param[in] user_data The user_data pointer.
typedef void (*AdbcCredentialHandler)(const struct AdbcError* details, void*
user_data);
AdbcStatusCode (*ConnectionSetCredentialHandler)(struct AdbcConnection*,
AdbcCredentialHandler
handler,
void* user_data, struct
AdbcError*);```
--
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]
