[ES-1436915] Modify an e2e test to iterate over the rs in a separate thread

[jayantsing-db]

Description

NO_CHANGELOG=true

This will help identify potential thread-safety issues, such as problems with state propagation and context management. In this scenario, customers can interact with first-class JDBC objects like Statement and ResultSet from a separate thread, while the JDBC connection object itself is managed in a different thread. The test is designed to simulate this type of multithreaded environment, ensuring that the system can handle concurrent access to these objects without issues. By doing so, it helps uncover any synchronization problems or unintended side effects that may arise when JDBC components are accessed from multiple threads.

Testing

The test is expected to fail now due to a bug in the implementation of DatabricksContextHolder.

Additional Notes to the Reviewer

[github-actions]

Please ensure that the `NEXT_CHANGELOG.md` file is updated with any relevant changes.  
If this is not necessary for your PR, include this in the PR body:

```
NO_CHANGELOG=true
```

and rerun the workflow.

[Copilot]

Pull Request Overview

This PR updates an end-to-end test to iterate over a ResultSet in a separate thread, aiming to surface potential thread-safety issues in the use of first-class objects such as Statement and ResultSet. Key changes include updating the test method signature to throw InterruptedException, creating a separate thread to iterate the result set, and capturing any exceptions occurring in that thread using an AtomicReference.

Comments suppressed due to low confidence (1)

src/test/java/com/databricks/jdbc/integration/fakeservice/tests/MultiChunkExecutionIntegrationTests.java:43

• [nitpick] Consider renaming 'thread' to a more descriptive name, such as 'resultProcessingThread', to clarify its role in this test.

Thread thread = new Thread(

[samikshya-db]

Thanks for adding this, J !