Regarding job status between current and the latest

[Jungtaek Lim <ka...@gmail.com>]

Hi devs,

Paragraph seems to show the latest job run info (date, status), and another
run overrides this information.
Confused thing is that another run doesn't override the finished date until
job finished, so while running start date is greater than finished date
which is not intuitive.

What do you think? Is it intention, or just a bug?
If we agree that we'd be better to set finished date to initial value
(null) when start of the run I'll address it to new issue / pull request.

Btw, would it be better to store job run history?
Maybe unit is paragraph, since we can run individual paragraph without
running whole notebook.
It is just a idea and I didn't think a way to realize.

Please share your opinion.

Thanks,
Jungtaek Lim (HeartSaVioR)

-- 
Name : Jungtaek Lim
Blog : http://medium.com/@heartsavior
Twitter : http://twitter.com/heartsavior
LinkedIn : http://www.linkedin.com/in/heartsavior

Re: Regarding job status between current and the latest

[Jungtaek Lim <ka...@gmail.com>]

Alexander,

Thanks for the quick comment!

As you may already know, null value is just a initial value of the date.
Changing date to initial value should not hurt if initial value doesn't
hurt now.
Again, I love to have Option but Zeppelin uses Java so we may want to just
adapt ourselves.

"null, or not null" is actually far from the issue. Job status messing up
with latest run and current run is the origin issue.
We're exposing start date and finish date to the REST API now, so although
it is not urgent but this is an existing issue.

Btw, just wondering, how about exposing job run history to the UI?
If we don't want to store histories, how about exposing current run status
(or latest status if not running) ?

Thanks,
Jungtaek Lim (HeartSaVioR)



On Wed, Dec 23, 2015 at 2:48 PM, Alexander Bezzubov <bz...@apache.org> wrote:

> Hi,
>
> Thank you for your question, I see what you meen.
>
> If I may, I would suggest that we do not try to store nulls anywhere becuse
> that will result in more pullrequests, checking for nulls in different
> places.
>
> If you could summerize the problem from the user perspective, that you are
> trying to solve - that usually helps to get more feedback from both users
> and developers.
>
> I.e right now date in UI beeing off for a running paragraph does not appear
> to me as a problem require immediate fix, allthough I might be wrong.
>
> --
> Alex
>
> On Wed, Dec 23, 2015, 14:28 Jungtaek Lim <ka...@gmail.com> wrote:
>
> > Hi devs,
> >
> > Paragraph seems to show the latest job run info (date, status), and
> another
> > run overrides this information.
> > Confused thing is that another run doesn't override the finished date
> until
> > job finished, so while running start date is greater than finished date
> > which is not intuitive.
> >
> > What do you think? Is it intention, or just a bug?
> > If we agree that we'd be better to set finished date to initial value
> > (null) when start of the run I'll address it to new issue / pull request.
> >
> > Btw, would it be better to store job run history?
> > Maybe unit is paragraph, since we can run individual paragraph without
> > running whole notebook.
> > It is just a idea and I didn't think a way to realize.
> >
> > Please share your opinion.
> >
> > Thanks,
> > Jungtaek Lim (HeartSaVioR)
> >
> > --
> > Name : Jungtaek Lim
> > Blog : http://medium.com/@heartsavior
> > Twitter : http://twitter.com/heartsavior
> > LinkedIn : http://www.linkedin.com/in/heartsavior
> >
>



-- 
Name : Jungtaek Lim
Blog : http://medium.com/@heartsavior
Twitter : http://twitter.com/heartsavior
LinkedIn : http://www.linkedin.com/in/heartsavior

Re: Regarding job status between current and the latest

[Alexander Bezzubov <bz...@apache.org>]

Hi,

Thank you for your question, I see what you meen.

If I may, I would suggest that we do not try to store nulls anywhere becuse
that will result in more pullrequests, checking for nulls in different
places.

If you could summerize the problem from the user perspective, that you are
trying to solve - that usually helps to get more feedback from both users
and developers.

I.e right now date in UI beeing off for a running paragraph does not appear
to me as a problem require immediate fix, allthough I might be wrong.

--
Alex

On Wed, Dec 23, 2015, 14:28 Jungtaek Lim <ka...@gmail.com> wrote:

> Hi devs,
>
> Paragraph seems to show the latest job run info (date, status), and another
> run overrides this information.
> Confused thing is that another run doesn't override the finished date until
> job finished, so while running start date is greater than finished date
> which is not intuitive.
>
> What do you think? Is it intention, or just a bug?
> If we agree that we'd be better to set finished date to initial value
> (null) when start of the run I'll address it to new issue / pull request.
>
> Btw, would it be better to store job run history?
> Maybe unit is paragraph, since we can run individual paragraph without
> running whole notebook.
> It is just a idea and I didn't think a way to realize.
>
> Please share your opinion.
>
> Thanks,
> Jungtaek Lim (HeartSaVioR)
>
> --
> Name : Jungtaek Lim
> Blog : http://medium.com/@heartsavior
> Twitter : http://twitter.com/heartsavior
> LinkedIn : http://www.linkedin.com/in/heartsavior
>