Bowen,
Question is whether it is a blocker to the release and requires re-spin
? Bundle logs are only used for debugging in case of a problem and there is
no functionality impact for the user. It is still available on the server
machine. And it only affects the case of automatic state transition and
logs are not affected for user initiated kill/suspend/pause/resume. In my
opinion it can go into the next patch release.
Regards,
Rohini
On Wed, Jun 3, 2015 at 9:20 AM, bowen zhang <[email protected]
> wrote:
> log API for bundle relies on lastModifiedTime to set the ending time of
> the searching for oozie.log. With the current bug, lastModifiedTime is set
> prematurely and as a result, log API for bundle job will miss later parts
> of the logs. If you run a simple bundle job right now, and after the job is
> done, you make a api log call, you won't see something like "update bundle
> job status from running to succeeded" which is supposedly be included in
> the log api results. Purshatom created a bug already and I gave a plus one.
> So, he should be able to commit it today. Purshatom, can you comment on the
> status of the bug?Bowen
>
> From: Shwetha Shivalingamurthy <[email protected]>
> To: bowen zhang <[email protected]>; Purshotam Shah <
> [email protected]>
> Cc: "[email protected]" <[email protected]>
> Sent: Wednesday, June 3, 2015 3:50 AM
> Subject: Re: [VOTE] Release Oozie 4.2.0 (candidate 0)
>
> Bowen,
>
> Did you mean BundleEngine.streamJobLog()? I didn’t understand how bundle
> last modified time is related to log API. Doesn’t it just affect updating
> bundle status?
>
> Even if its related to log API, is this blocker for 4.2 release Bowen? The
> issue can be addressed on trunk. Lets take a call on either going ahead
> with the release or cancelling the already voted release.
>
> Thanks,
> Shwetha
>
>
>
>
> On 02/06/15 6:13 am, "bowen zhang" <[email protected]>
> wrote:
>
> >Purshotam,The issue with this one is that log api for bundle jobs no
> >longer runs correctly since it relies on the lastModifiedTime of the job
> >
> > From: Purshotam Shah <[email protected]>
> > To: "[email protected]" <[email protected]>; bowen zhang
> ><[email protected]>
> > Sent: Monday, June 1, 2015 5:24 PM
> > Subject: Re: [VOTE] Release Oozie 4.2.0 (candidate 0)
> >
> >>In BundleStatusTransitService.java method updateJobStatus, shouldn't we
> >>set the lastModifiedTime >for the job as well?Purshatom, can you comment
> >>on my second point since you created the file?
> >Yes, it should. Created https://issues.apache.org/jira/browse/OOZIE-2257
> >to track this.
> >I don't think it's a blocker for 4.2. We are running Oozie with modified
> >StatusTransitService in our prod for more than 6 months. No issue.
> >
> >
> >
> > From: bowen zhang <[email protected]>
> > To: "[email protected]" <[email protected]>
> > Sent: Sunday, May 31, 2015 1:02 PM
> > Subject: Re: [VOTE] Release Oozie 4.2.0 (candidate 0)
> >
> >I have two concerns.1. In our install doc, it looks like we are still
> >telling user to do "hadoop fs -put share share" which is not correct
> >anymore or at elast not the most updated method2. In
> >BundleStatusTransitService.java method updateJobStatus, shouldn't we set
> >the lastModifiedTime for the job as well?Purshatom, can you comment on my
> >second point since you created the file?Thanks,Bowen
> >
> > From: Rohini Palaniswamy <[email protected]>
> >
> >
> > To: "[email protected]" <[email protected]>
> > Sent: Thursday, May 28, 2015 12:16 PM
> > Subject: Re: [VOTE] Release Oozie 4.2.0 (candidate 0)
> >
> >+1. Checked signatures. Compiled and ran unit tests.
> >
> >Regards,
> >Rohini
> >
> >On Wed, May 27, 2015 at 2:16 AM, Harsh J <[email protected]> wrote:
> >
> >> +1. I checked the MD5 and the RAT report, and built it
> >> successfully with the -Phadoop-2 flag.
> >>
> >> On Wed, May 27, 2015 at 10:09 AM, Shwetha Shivalingamurthy
> >> <[email protected]> wrote:
> >> > Thanks Robert for verifying.
> >> >
> >> > I didn¹t realise it was a long weekend in the US. Extending the vote
> >>by 2
> >> > days. Vote now closes on Friday, May 29th, 2015 12:00 PM GMT. Please
> >> > verify and vote.
> >> >
> >> > +1 from me.
> >> >
> >> > Thanks,
> >> > Shwetha
> >> >
> >> > On 27/05/15 3:15 am, "Robert Kanter" <[email protected]> wrote:
> >> >
> >> >>+1
> >> >>
> >> >>
> >> >>+ Verified md5
> >> >>+ RAT report looks good
> >> >>+ Ran some of the examples against Hadoop 1.2.0 after compiling with
> >>the
> >> >>hadoop-1 and uber profiles (mvn clean package assembly:single
> >> -DskipTests
> >> >>-Phadoop-1 -Puber -DgenerateDocs)
> >> >>+ Ran some of the examples against the latest Hadoop 2.8-SNAPSHOT
> >>after
> >> >>compiling with the hadoop-2 and uber profiles (mvn clean package
> >> >>assembly:single -DskipTests -Phadoop-2 -Puber -DgenerateDocs)
> >> >>
> >> >>- Robert
> >> >>
> >> >>
> >> >>On Tue, May 26, 2015 at 8:04 AM, pavan kumar Kolamuri <
> >> >>[email protected]> wrote:
> >> >>
> >> >>> Hi shwetha there is issue regarding spark action
> >> >>> https://issues.apache.org/jira/browse/OOZIE-2253. Please mention in
> >> >>> release
> >> >>> notes.
> >> >>>
> >> >>> On Tue, May 26, 2015 at 12:37 PM, Shwetha Shivalingamurthy <
> >> >>> [email protected]> wrote:
> >> >>>
> >> >>> > Just one more day for the vote to close. Need atleast 3 votes from
> >> >>>PMCs.
> >> >>> > Please review and vote
> >> >>> >
> >> >>> > Thanks,
> >> >>> > Shwetha
> >> >>> >
> >> >>> > On 22/05/15 11:30 pm, "Shwetha Shivalingamurthy"
> >> >>> > <[email protected]> wrote:
> >> >>> >
> >> >>> > >Hi All,
> >> >>> > >
> >> >>> > >I have created a build for Oozie 4.2.0 (candidate 0).
> >> >>> > >
> >> >>> > >Please download, test, try it out and vote:
> >> >>> > >http://people.apache.org/~shwethags/oozie-4.2.0-rc0/
> >> >>> > >
> >> >>> > >The release, md5 signature, gpg signature, rat report, and gpg
> >>keys
> >> >>>can
> >> >>> > >all be found at the above address.
> >> >>> > >
> >> >>> > >Vote closes on Wednesday, May 27th, 2015 12:00 PM GMT
> >> >>> > >
> >> >>> > >Thank you all for your contribution
> >> >>> > >
> >> >>> > >Regards,
> >> >>> > >Shwetha
> >> >>> >
> >> >>> >
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Regards
> >> >>> Pavan Kumar Kolamuri
> >> >>>
> >> >
> >>
> >>
> >>
> >> --
> >> Harsh J
> >>
> >
> >
> >
> >
> >
> >
>
>
>
>
>
