[ES-1614176] Fix: Databricks OSS JDBC Driver Fails to Authenticate After Token Update

[shivam2680]

Description

Problem: When using con.setClientInfo("Auth_AccessToken", <new_token>) to update the access token, subsequent queries continued using the old token instead of the new one. This caused authentication failures when the new token was invalid or when the old token expired.

fix: Made databricksConfig mutable in DatabricksThriftAccessor and update it with new config (token) on con.setClientInfo("Auth_AccessToken", <new_token>) calls.

Testing

Unit tests

Additional Notes to the Reviewer

[jayantsing-db]

u2m not working seems like a major bug. what versions we have u2m not working? curious how did this slip past testing?

[jayantsing-db]

u2m not working seems like a major bug

looks like a specific CUJ in U2M doesn't work and typical U2M works?

[nikhilsuri-db]

LGTM, Can we write end to end test to verify this fix?

[samikshya-db]

@nikhilsuri-db - that is not possible at the moment.

@jayantsing-db looks like a specific CUJ in U2M doesn't work and typical U2M works?
The U2M scenario itself is complex : there are 48 variations (3clouds * proxy/nonproxy * discoveryURLUsage * refreshTokenUsage* tokenFed). We are closely working with SDK to address some of these differences even today (after a couple of iterations earlier) : databricks/databricks-sdk-java#525. I don't know if that answers your q though.