AMBARI-22698: Custom zeppelin interpreter properties are getting removed after moving zeppelin to a different host#162
Merged
Conversation
…ved after moving zeppelin to a different host (prabhjyotsingh)
Contributor
Author
|
@venkatasairamlanka please help review/merge this in trunk/branch-2.6 |
|
Refer to this link for build results (access rights to CI server needed): |
Contributor
|
Will merge this based on reviews on https://reviews.apache.org/r/64861/ |
This file contains hidden or 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.
What changes were proposed in this pull request?
Custom zeppelin interpreter properties are getting removed after moving zeppelin to a different host
How was this patch tested?
Manually
Custom zeppelin interpreter properties are getting lost after moving zeppelin to a different host
Steps to reproduce :
a) Add new custom properties
b) Modify existing properties
Changes are getting saved in HDFS path /user/zeppelin/conf/interpreter.json and they are getting synced to local path /etc/zeppelin/conf/interpreter.json after zeppelin restart.