Fix Livy Batch model and tests, resolve Issue #56 #99
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi, this PR resolves the issue #56 by fixing the Livy Batch model and related tests.
The current Batch model is based on the official documentation from Livy at https://livy.incubator.apache.org/docs/latest/rest-api.html, which unfortunately is not inline with the current code of the Livy server.
The current code of the Livy server already returns "name", "owner" and "proxyUser" information for a batch, but the official documentation is not updated yet. So I patched our current code to reflect the latest changes.