Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1439
@agoodm Thanks for the contribution.
While documentation says "Interpreter Execution Callbacks" is experimental
(which i agree), i think `@Experimental` annotation should be used for API
instead of `@ZeppelinApi`.
The implementation keeps callback registry in ZeppelinServer side. But i'm
curios while it's volatile and per interpreter, I wonder if callback registry
can be placed inside of Interpreter process, that might reduce complexity (no
thrift communication) and increases flexibility (able to register actual
function, not only the strings). What do you think? Could you elaborate these
two choices?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
