You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem Statement
The current implementation of SDK returns a Wait object for long running operations like cluster or warehouse creation. The clients have option to either getId() which returns identifier of the resource or use get() method which waits for the operation to complete and internally uses Thread.sleep for polling. This causes the current thread to block.
Proposed Solution
Support async programming by returning Futures. This will allow clients to write async code and better utilize their resources.
The text was updated successfully, but these errors were encountered:
Problem Statement
The current implementation of SDK returns a Wait object for long running operations like cluster or warehouse creation. The clients have option to either getId() which returns identifier of the resource or use get() method which waits for the operation to complete and internally uses Thread.sleep for polling. This causes the current thread to block.
Proposed Solution
Support async programming by returning Futures. This will allow clients to write async code and better utilize their resources.
The text was updated successfully, but these errors were encountered: