You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.
To fully embrace Zeppelin as a first class citizen in our data analysis tools, we need to provide ATMO users with the ability to schedule Zeppelin notebooks. Here is a draft list of use cases:
As a user, I want to be able to create a new scheduled job provided a Zeppelin notebook.
As a user, when I schedule a Zeppelin notebook, I expect the notebook to be rendered in the job detail view.
As a user, I expect to see the list of results, logs and runs of a scheduled Zeppelin notebook in the job detail view.
Here is a draft list of tasks required to make it work:
Modify batch.sh to make it use zeppelin executor when dealing with a Zeppelin notebook.
Modify the job detail view to render a Zeppelin notebook either using the zeppelin markdown converter or via a new html/js converter.
Modify the job creation form to also accept Zeppelin notebooks.
Feel free to change this list as needed. Once this list is stable we can open one issue per task.
The text was updated successfully, but these errors were encountered:
To fully embrace Zeppelin as a first class citizen in our data analysis tools, we need to provide ATMO users with the ability to schedule Zeppelin notebooks. Here is a draft list of use cases:
Here is a draft list of tasks required to make it work:
batch.sh
to make it use zeppelin executor when dealing with a Zeppelin notebook.Feel free to change this list as needed. Once this list is stable we can open one issue per task.
The text was updated successfully, but these errors were encountered: