Sami Jaktholm created ZEPPELIN-751:
--------------------------------------
Summary: Notebook list quietly truncated if Zeppelin cannot access
one note.json object in Amazon S3
Key: ZEPPELIN-751
URL: https://issues.apache.org/jira/browse/ZEPPELIN-751
Project: Zeppelin
Issue Type: Bug
Affects Versions: 0.5.6
Reporter: Sami Jaktholm
*Steps to reproduce:*
# Have multiple notebooks stored in Amazon S3 bucket
# Remove READ permission from *one* of the note.json objects in the notebook
bucket
# Access Zeppelin and reload the notebook list
*What happens:*
Notebooks are read from Amazon S3 until the object without read permissions
comes up in the object listing. Any notebook that appears in the object list
after the notebook that Zeppelin was not able to access will be absent from the
Zeppelin notebook listing even though the note.json objects for these notebooks
were accessible.
Also, no error is logged making debugging this particularly hard. The relevant
exception is swallowed at [1].
*What should happen:*
Zeppelin should log an error and continue reading the remaining notebooks even
though one of them failed. Or at least log an error.
[1]
https://github.com/apache/incubator-zeppelin/blob/39417c073b6d5d6d206ea021f0d68aeb3c81f859/zeppelin-zengine/src/main/java/org/apache/zeppelin/notebook/repo/S3NotebookRepo.java#L113
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
