Re: Branching for Oozie 4.0

[Rohini Palaniswamy <ro...@gmail.com>]

Hi,
   I think we should be good to release 4.0 early next week. Mona will be
rolling out the release.

Pending:
  - https://issues.apache.org/jira/browse/OOZIE-1482 - backward
compatibility with older servers for frequency in json response. Patch is
already up.
  - A minor issue with db upgrade if error msg string is >4K characters. We
need to truncate and insert to the varchar errormsg column. Ryota is
working on this and should be committed by tomorrow.

 Is there anything else that needs to be pulled in?

Robert/Bowen,
   Would you guys be able to take the time and try out branch-4.0 since
this is a major one with DB upgrade? If you find any issues, we can pull
them in before the release. Since the RC candidate will not contain any
binaries, you don't have to wait till RC to try it out.

Regards,
Rohini

On Wed, Jul 24, 2013 at 11:43 AM, Mona Chitnis <ch...@yahoo-inc.com>wrote:

> We discovered a couple of critical bugs around Bundle Kill command. We
> will be patching branch 3.3, branch-4.0 and trunk in the next few days and
> then would be comfortable preparing for the release.
>
> --
> Mona
>
> On 7/24/13 11:36 AM, "Robert Kanter" <rk...@cloudera.com> wrote:
>
> >Hi Rohini,
> >
> >What's the status of branch 4?  Do you think you'll be sending out a vote
> >for the release soon?
> >
> >thanks
> >- Robert
> >
> >
> >On Wed, Jul 24, 2013 at 2:27 AM, Shwetha GS <sh...@inmobi.com>
> wrote:
> >
> >> https://issues.apache.org/jira/browse/OOZIE-1465 has a small patch to
> >>make
> >> some constants public. These are very useful for EL extensions. Can you
> >> please merge to 4.0 branch
> >>
> >> -Shwetha
> >>
> >>
> >> On Sat, Jul 20, 2013 at 5:36 AM, Rohini Palaniswamy <
> >> rohini.aditya@gmail.com
> >> > wrote:
> >>
> >> > This is done now. Changed version to 4.0.0 for the following
> >> >
> >> > project = OOZIE AND fixVersion = trunk AND resolution = Fixed AND Key
> >>not
> >> > in (OOZIE-1453, OOZIE-1447, OOZIE-1440) AND fixVersion not in
> >>("3.3.0",
> >> > "3.3.1", "3.3.2")
> >> >
> >> >   Also removed trunk from FixVersion/s when there were other versions.
> >> >
> >> > Regards,
> >> > Rohini
> >> >
> >> > On Sat, Jul 13, 2013 at 6:40 PM, Rohini Palaniswamy <
> >> > rohini.aditya@gmail.com
> >> > > wrote:
> >> >
> >> > > > Do you mean the "Fix Version" field?
> >> > >    Yes.
> >> > >
> >> > > >  I know that many JIRAs are using that
> >> > > to also mean the "target version", which is a field we don't have
> >> > >  "Fix Version" is the equivalent of bugzilla "Target Version".
> >> > >
> >> > > >  I'm sure there are some JIRAs marked with
> >> > > "Fix Version" as trunk that we don't want in 4.0, right?
> >> > >   Yes. A couple of jiras went into trunk after the branching. They
> >>will
> >> > > not be marked 4.0
> >> > >
> >> > > Regards,
> >> > > Rohini
> >> > >
> >> > >
> >> > > On Fri, Jul 12, 2013 at 2:10 PM, Robert Kanter <
> rkanter@cloudera.com
> >> > >wrote:
> >> > >
> >> > >> Do you mean the "Fix Version" field?  I know that many JIRAs are
> >>using
> >> > >> that
> >> > >> to also mean the "target version", which is a field we don't have
> >> > (perhaps
> >> > >> we should have that field?).  I'm sure there are some JIRAs marked
> >> with
> >> > >> "Fix Version" as trunk that we don't want in 4.0, right?
> >> > >>
> >> > >> - Robert
> >> > >>
> >> > >>
> >> > >> On Fri, Jul 12, 2013 at 11:45 AM, Rohini Palaniswamy <
> >> > >> rohini.aditya@gmail.com> wrote:
> >> > >>
> >> > >> > Planning to do a bulk update of the Fixed version of jiras to
> >> > branch-4.0
> >> > >> > tomorrow. Currently they are marked as trunk. Please let know if
> >> there
> >> > >> are
> >> > >> > any objections.
> >> > >> >
> >> > >> > Regards,
> >> > >> > Rohini
> >> > >> >
> >> > >> > On Fri, Jun 28, 2013 at 10:27 PM, Rohini Palaniswamy <
> >> > >> > rohini.aditya@gmail.com> wrote:
> >> > >> >
> >> > >> > > Created
> >>http://svn.apache.org/viewvc/oozie/branches/branch-4.0/.
> >> > >> > >
> >> > >> > > Patches yet to be done for branch-4.0.
> >> > >> > >
> >> > >> > >  OOZIE-1379 Generate SLA end_miss event only after confirming
> >> > against
> >> > >> > > persistent store
> >> > >> > > OOZIE-1249 and OOZIE-1430 Documentation for JMS notifications
> >>and
> >> > SLA
> >> > >> > > monitoring
> >> > >> > > OOZIE-1405 Fix flakey unit tests
> >> > >> > >
> >> > >> > > Regards,
> >> > >> > > Rohini
> >> > >> > >
> >> > >> > > On Fri, Jun 28, 2013 at 11:41 AM, Robert Kanter <
> >> > rkanter@cloudera.com
> >> > >> > >wrote:
> >> > >> > >
> >> > >> > >> Ah, you're right; thanks.
> >> > >> > >>
> >> > >> > >> I reviewed the patch, but I'd like someone else to also take a
> >> look
> >> > >> > >> because
> >> > >> > >> I'm not a DB expert.
> >> > >> > >>
> >> > >> > >> - Robert
> >> > >> > >>
> >> > >> > >>
> >> > >> > >> On Fri, Jun 28, 2013 at 11:30 AM, Virag Kothari <
> >> > virag@yahoo-inc.com
> >> > >> >
> >> > >> > >> wrote:
> >> > >> > >>
> >> > >> > >> > That change is reverted by OOZIE-1436. Can you review
> >> > >> > >> > https://reviews.apache.org/r/12164/ and confirm?
> >> > >> > >> > We can keep OOZIE-1437 open to deal the problems we will
> >>face
> >> > when
> >> > >> > >> having
> >> > >> > >> > a 'proper' fix for the clob/varchar issues.
> >> > >> > >> >
> >> > >> > >> > Thanks,
> >> > >> > >> > Virag
> >> > >> > >> >
> >> > >> > >> > On 6/28/13 11:12 AM, "Robert Kanter" <rk...@cloudera.com>
> >> > wrote:
> >> > >> > >> >
> >> > >> > >> > >I think we need both; OOZIE-1436 reverts the columns back
> >> > because
> >> > >> of
> >> > >> > an
> >> > >> > >> > >OpenJPA/Oracle issue and OOZIE-1437 is to fix an if
> >>statement
> >> > >> added
> >> > >> > >> into
> >> > >> > >> > >our code (see
> >> > >> > >> > >
> >> > >> > >> >
> >> > >> > >>
> >> > >> >
> >> > >>
> >> >
> >>
> >>
> https://issues.apache.org/jira/browse/OOZIE-1398?focusedCommentId=1369422
> >>4
> >> > >> > >> >
> >> > >> > >>
> >> > >> >
> >> > >>
> >> >
> >>
> >>>&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#c
> >>>om
> >> > >> > >> > >ment-13694224
> >> > >> > >> > >)
> >> > >> > >> > >
> >> > >> > >> > >thanks
> >> > >> > >> > >- Robert
> >> > >> > >> > >
> >> > >> > >> > >
> >> > >> > >> > >On Fri, Jun 28, 2013 at 11:00 AM, Virag Kothari <
> >> > >> virag@yahoo-inc.com
> >> > >> > >
> >> > >> > >> > >wrote:
> >> > >> > >> > >
> >> > >> > >> > >> OOZIE-1436 will convert data varchar column back to lob
> >>due
> >> to
> >> > >> some
> >> > >> > >> > >>issues
> >> > >> > >> > >> seen (In JIRA description) with OpenJPA.
> >> > >> > >> > >>
> >> > >> > >> > >>
> >> > >> > >> > >> Thanks,
> >> > >> > >> > >> Virag
> >> > >> > >> > >>
> >> > >> > >> > >> On 6/28/13 10:55 AM, "Robert Kanter"
> >><rk...@cloudera.com>
> >> > >> wrote:
> >> > >> > >> > >>
> >> > >> > >> > >> >Can we also get OOZIE-1437 (paramerize size limit of
> >> setData
> >> > in
> >> > >> > >> > >> >JsonWorkflowAction based on user's configuration) in
> >> > >> branch-4.0?
> >> > >> > >> > >>Without
> >> > >> > >> > >> >this, the size of </capture-output> is always hardcoded
> >>at
> >> > max
> >> > >> of
> >> > >> > >> 2k,
> >> > >> > >> > >>even
> >> > >> > >> > >> >if the user changes it in oozie-site (because of
> >> OOZIE-1398).
> >> > >> > >> > >> >
> >> > >> > >> > >> >thanks
> >> > >> > >> > >> >- Robert
> >> > >> > >> > >> >
> >> > >> > >> > >> >
> >> > >> > >> > >> >On Fri, Jun 28, 2013 at 9:21 AM, Rohini Palaniswamy
> >> > >> > >> > >> ><rohini.aditya@gmail.com
> >> > >> > >> > >> >> wrote:
> >> > >> > >> > >> >
> >> > >> > >> > >> >> Hi,
> >> > >> > >> > >> >>     I am planning to branch trunk as branch-4.0 and
> >>trash
> >> > the
> >> > >> > >> current
> >> > >> > >> > >> >> branch-4.0 today evening. Discussed this with some of
> >>the
> >> > >> folks
> >> > >> > >> > >>during
> >> > >> > >> > >> >>the
> >> > >> > >> > >> >> summit. This will facilitate releasing HCat
> >>integration,
> >> > JMS
> >> > >> > >> > >> >>notifications
> >> > >> > >> > >> >> for job and SLA and SLA monitoring as Oozie 4.0 which
> >>we
> >> > are
> >> > >> > done
> >> > >> > >> > >>with
> >> > >> > >> > >> >> functional testing and in the process of stress
> >>testing.
> >> > This
> >> > >> > will
> >> > >> > >> > >>free
> >> > >> > >> > >> >>up
> >> > >> > >> > >> >> the trunk for the next release features of HA, cron
> >>based
> >> > >> > >> > >>scheduling, DB
> >> > >> > >> > >> >> clob column removal to move forward.
> >> > >> > >> > >> >>
> >> > >> > >> > >> >>
> >> > >> > >> > >> >> Patches that need to get into branch-4.0 are
> >> > >> > >> > >> >>
> >> > >> > >> > >> >> OOZIE-1433 ActionCheckX should override
> >>XCommand.getKey()
> >> > to
> >> > >> > >> prevent
> >> > >> > >> > >> >> duplicates
> >> > >> > >> > >> >> OOZIE-1436 Revert SLA_XML and few other varchar
> >>columns
> >> > back
> >> > >> to
> >> > >> > >> clob
> >> > >> > >> > >> >> OOZIE-1427 Update CredentialsModule docs to mention
> >>Hive
> >> > >> > >> > >> >> OOZIE-1379 Generate SLA end_miss event only after
> >> > confirming
> >> > >> > >> against
> >> > >> > >> > >> >> persistent store
> >> > >> > >> > >> >> OOZIE-1435 StatusTransitService unnecessarily updates
> >>the
> >> > >> > >> > >> >>lastModifiedTime
> >> > >> > >> > >> >> of jobs which causes MaterializationService to bring
> >>same
> >> > >> jobs
> >> > >> > in
> >> > >> > >> > >>memory
> >> > >> > >> > >> >> OOZIE-1249 and OOZIE-1430 Documentation for JMS
> >> > notifications
> >> > >> > and
> >> > >> > >> SLA
> >> > >> > >> > >> >> monitoring
> >> > >> > >> > >> >> Subworkflow notifications don't have workflow as
> >>parent
> >> id
> >> > >> > >> > >> >> And any other issues that crop up during the stress
> >> > testing.
> >> > >> > >> > >> >>
> >> > >> > >> > >> >>    Hoping most of this will get committed today
> >>before we
> >> > >> > branch.
> >> > >> > >> > >>Please
> >> > >> > >> > >> >> bring up any other jiras that we need to get into
> >> branch-4
> >> > >> > before
> >> > >> > >> > >>moving
> >> > >> > >> > >> >> towards a release. Looking at a timeline of releasing
> >>4.0
> >> > in
> >> > >> 3
> >> > >> > >> weeks.
> >> > >> > >> > >> >>
> >> > >> > >> > >> >> Regards,
> >> > >> > >> > >> >> Rohini
> >> > >> > >> > >> >>
> >> > >> > >> > >>
> >> > >> > >> > >>
> >> > >> > >> >
> >> > >> > >> >
> >> > >> > >>
> >> > >> > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >> --
> >> _____________________________________________________________
> >> The information contained in this communication is intended solely for
> >>the
> >> use of the individual or entity to whom it is addressed and others
> >> authorized to receive it. It may contain confidential or legally
> >>privileged
> >> information. If you are not the intended recipient you are hereby
> >>notified
> >> that any disclosure, copying, distribution or taking any action in
> >>reliance
> >> on the contents of this information is strictly prohibited and may be
> >> unlawful. If you have received this communication in error, please
> >>notify
> >> us immediately by responding to this email and then delete it from your
> >> system. The firm is neither liable for the proper and complete
> >>transmission
> >> of the information contained in this communication nor for any delay in
> >>its
> >> receipt.
> >>
>
>