CurtHagenlocher commented on issue #4231: URL: https://github.com/apache/arrow-adbc/issues/4231#issuecomment-4255211929
> what the driver would have to do internally anyways In our increasingly HTTP-centric world, the driver could keep using the same HTTP connection and simply put the new credential in the header of the next request. This is presumably what it would do if it were refreshing credentials on its own. > The better solution (IMHO) is for this to be handled by the driver if necessary I agree that this would be ideal but have run into situations where it's not possible. For instance, minting the token might require access to a certificate behind a custom service and having the driver know about the service isn't practical. -- 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]
