MLSQLRest returns more informative response for different types of errors #1739
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
RestUtils.executeWithRetrying executes one more time than expected.
In the old implementation, function executes at least two times. It's fixed now, and is covered by test case in RestUtilsTest
MLSQLRest load function refactoring
The logic to call http endpoints with retrying is repated 3 times with small differences. Now , we encapsulate it in
_httpWithRetrying
. For pagnation, use do while loop to avoid reapted code.Since it's a big change, 4 new caes are added. And unit test covers
More informative response
Now, MLSQLRest returns
Exception
such as UnknownHost.How was this patch tested?
MLSQLRest test result
RestUtils test result
Are there and DOC need to update?
Spark Core Compatibility