HIVE-18338 Exposing asynchronous execution through hive-jdbc client

[amrk7s]

Problem statement

Hive JDBC currently exposes 2 methods related to asynchronous execution
executeAsync() - to trigger a query execution and return immediately.
waitForOperationToComplete() - which waits till the current execution is complete blocking the user thread.

This has one problem

• If the client process goes down, there is no way to resume queries although hive server is completely asynchronous.

Proposal

If operation handle could be exposed, we can latch on to an active execution of a query.

Code changes

Operation handle is exposed. So client can keep a copy.
latchSync() and latchAsync() methods take an operation handle and try to latch on to the current execution in hive server if present

[amrk7s]

Travis CI seem to have failed? Is this a problem? Please let me know.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Feel free to reach out on the dev@hive.apache.org list if the patch is in need of reviews.