GH-33874: [Java] Ensure custom headers are included during JDBC auth handshake#33946
Conversation
Looks like `getAuthenticate` makes a request to the server before it adds the `CredentialCallOption` to the client options. In order to send the existing `CallOptions` we need to pass them in to `getAuthenticate`
|
|
lidavidm
changed the title
|
Benchmark runs are scheduled for baseline = a0e2d65 and contender = 61f3cdf. 61f3cdf is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
… auth handshake (apache#33946) ### Rationale for this change The expectation is that any custom properties set on the JDBC connection are sent across on every request. This PR ensures the handshake request gets those headers as well. ### What changes are included in this PR? Ensure custom headers are sent during auth handshake ### Are these changes tested? No, not sure where the best place to test this. ### Are there any user-facing changes? No, other than seeing expected behavior. * Closes: apache#33874 Authored-by: Diego Fernandez <[email protected]> Signed-off-by: David Li <[email protected]>
3 participants
Rationale for this change
The expectation is that any custom properties set on the JDBC connection are sent across on every request. This PR ensures the handshake request gets those headers as well.
What changes are included in this PR?
Ensure custom headers are sent during auth handshake
Are these changes tested?
No, not sure where the best place to test this.
Are there any user-facing changes?
No, other than seeing expected behavior.