Hi 

I have few questions about the notebook job behaviors:

1. It uses cron job to schedule a notebook to run.  The cron job is OS 
dependent.  It is available only in Unix/Linux system.  Do you see if the 
Zeppelin will be ported to run in Windows?  Since cron job is not available in 
Windows, you will need to use Windows specific scheduling mechanism.  I wonder 
how extensible is the current job implementation, is it feasible to replace it 
with some open source scheduler that can support different OS?

2. Once a notebook is scheduled, it seems user can still work on the notebook. 
Does the scheduler create a copy of notebook to run?  Or it only runs the same 
instance of the notebook?  What happens if user is working on the notebook that 
it is about to be run by the job?  Will the notebook become unavailable to user 
until the job run is complete?

3. The UI to schedule a job run seems lacking. User expects a more elaborate UI 
to set the job start time, frequency (daily, weekly, monthly, etc), end time, 
email notification, etc.  Is there a plan to improve the scheduling UI in 
future release?  I see a proposal for a job monitoring UI, which is quite nice.

4. Current Zeppelin notebook supports only single user environment. I wonder if 
it will be extended to support multitent environment in future release. The job 
will then need to support multiple users running different jobs at vary 
intervals. Do you see any issues to support multiple users?

Thanks
Denny


Reply via email to