Github user kavinkumarks commented on the issue:
https://github.com/apache/zeppelin/pull/1408
@khalidhuseynov thanks for sharing the inputs on this.Basically I like your
idea of propagating the specific error to the user instead of the generic error
message so the user would be more specific about the issue.If we need to handle
other errors we can think about them in the future if there is need.
Here is my thought to the approach.I will change
org.apache.zeppelin.notebook.repo.VFSNotebookRepo.save(Note,
AuthenticationInfo) to throw the specific exception with the error message and
handle the exception in
org.apache.zeppelin.socket.NotebookServer.runParagraph(NotebookSocket,
HashSet<String>, Notebook, Message) and then broadcast the error message to the
user.
Thanks,
Kavin
MailTo: kavin.ku...@imaginea.com
---
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.
---
