[AMBARI-23110]. livy2-client version is not updated as part of Patch Up… #499
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
…grade. (dlysnichenko)
ghost
requested review from
ghost
changed the title
jonathan-hurley
approved these changes
Feb 28, 2018
|
Refer to this link for build results (access rights to CI server needed): |
rlevas
approved these changes
Feb 28, 2018
This pull request was closed.
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.
…grade. (dlysnichenko)
What changes were proposed in this pull request?
LIVY2_CLIENT isn't actually a component which Ambari manages. That's why it's never orchestrated. I suppose that we can fix this by having the SPARK2_CLIENT also update the pointers for LIVY2_CLIENT by changing the stack_packages.json.
How was this patch tested?
manual cluster deployment