-
Notifications
You must be signed in to change notification settings - Fork 2.8k
ZEPPELIN-1423 - Allow users to specify pre/post-execute hooks for interpreters #1470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
8fad936
Added Interpreter Hooks to Interpreter Process
agoodm 07cac65
Implemented user-defined hook registry system for spark/pyspark inter…
agoodm 1331fe1
Update interpreters.md
agoodm 044a99d
Ensure that registered hooks are applied after call to open()
agoodm 56ede60
Automatically detect default interpreter for registerHook()
agoodm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
InterpreterHookRegistryis directly passed toZeppelinContexton it's constructor. And ZeppelinContext is exposed to user directly. So currentlyInterpreter.registerHook(),Interpreter.unregiserHook(),Interpreter.getHook()are accessed from onlyRemoteInterpreterServer. ButRemoteInterpreterServeralso can get directly accessInterpreterHookRegistryfromInterpreterGroup. In this way, i think the feature can be implemented without modification of Interpreter.java. What do you think?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kind of see your point, moving the convenience methods from
Interpreter.javatoInterpreterGroup.javawould save the need for defining wrappers inLazyOpenInterpreter.java. However this would also mean that the interpreterclassNamemust always be specified. This means for example that this line:Would be changed to
Additionally while these methods are only currently called through
RemoteInterpreterServer, I will have use cases for directly calling them in the PythonInterpretersubclasses (eg,PySparkInterpreterandPythonInterpreter) for my upcoming matplotlib integration work. Given this, I felt that the current syntax would be clearer.