You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by Ryota Egashira <eg...@yahoo-inc.com.INVALID> on 2015/04/09 21:08:07 UTC
Re: [DISCUSSION] Oozie 4.2.0 release
OOZIE-1993 need to be fixed before release.workflow rerun failed with oozie.wf.rerun.failnodes=true in some cases. actually because of this, we reverted OOZIE-1879 for our internal branch.
ThanksRyota
On Thursday, March 26, 2015 4:57 PM, Robert Kanter <rk...@cloudera.com> wrote:
Another JIRA that would be good to get is OOZIE-2186 which updates the
Tomcat version.
On Thu, Mar 26, 2015 at 2:46 PM, Shwetha Shivalingamurthy <
sshivalingamurthy@hortonworks.com> wrote:
> Ok, I will wait for them. Thanks
>
>
> On 26/03/15 2:21 pm, "Rohini Palaniswamy" <ro...@gmail.com> wrote:
>
> >We don't have a list of issues that need to be included. But Michelle ran
> >the regression with trunk yesterday and there were couple of failures. We
> >haven't investigated them yet. Those will have to be fixed though. Ryota
> >will file jiras and upload fixes next week after investigating them.
> >
> >Regards,
> >Rohini
> >
> >On Thu, Mar 26, 2015 at 1:58 PM, Harsh J <ha...@cloudera.com> wrote:
> >
> >> I can take over OOZIE-1963. I need to test the modified hive(1) example
> >>and
> >> will then attach the change to the JIRA.
> >>
> >> On Thu, Mar 26, 2015 at 6:20 AM, Robert Kanter <rk...@cloudera.com>
> >> wrote:
> >>
> >> > I was hoping one of our QA engineers would take care of that, but it
> >> looks
> >> > like he won't have time. I don't think I'm proficient enough in Hive
> >> > Server 2 to make the example, so I've unassigned OOZIE-1963 from me.
> >> > Though I think it would still be good to include.
> >> >
> >> > If we include the Spark action, I think we should also include
> >> OOZIE-2170.
> >> > OOZIE-2174 would also be good; it addresses some long-standing
> >> shortcomings
> >> > of OozieClient/OozieCLI.
> >> > Finally, we should also include OOZIE-2181, which fixes some problems
> >> > retrieving job info.
> >> > I have patches available for all 3 of these.
> >> >
> >> >
> >> > - Robert
> >> >
> >> > On Wed, Mar 25, 2015 at 10:58 AM, Shwetha Shivalingamurthy <
> >> > sshivalingamurthy@hortonworks.com> wrote:
> >> >
> >> > > Robert, will you be able to take up OOZIE-1963?
> >> > >
> >> > > Dev team, Are there any other un-resolved jiras that needs to be
> >>part
> >> of
> >> > > 4.2 release?
> >> > >
> >> > > Thanks,
> >> > > Shwetha
> >> > >
> >> > >
> >> > > On 11/02/15 1:44 pm, "Robert Kanter" <rk...@cloudera.com> wrote:
> >> > >
> >> > > >I 4.2.0 release sounds good; I don't have cycles to drive it
> >>though.
> >> > > >
> >> > > >The Spark action currently has a number of problems with it. I'd
> >>hold
> >> > off
> >> > > >on putting that into a release until we get those fixed (OOZIE-2071
> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2071> (it's to add an
> >> > > >example,
> >> > > >but the comments discuss the problems), OOZIE-2087
> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2087>).
> >> > > >
> >> > > >I'm all for including the Hive2 action; though it would be good if
> >>we
> >> > > >could
> >> > > >create an example workflow for it for completeness (OOZIE-1963
> >> > > ><https://issues.apache.org/jira/browse/OOZIE-1963>). I can
> >>probably
> >> > take
> >> > > >care of this relatively easily.
> >> > > >
> >> > > >
> >> > > >- Robert
> >> > > >
> >> > > >On Tue, Feb 10, 2015 at 9:56 PM, Shwetha Shivalingamurthy <
> >> > > >sshivalingamurthy@hortonworks.com> wrote:
> >> > > >
> >> > > >> Hi All,
> >> > > >>
> >> > > >> Oozie trunk has a couple of changes since the last oozie release
> >>-
> >> > > >>re-run
> >> > > >> fixes, config cleanup, spark action, hive2 action, external
> >> > > >>configuration
> >> > > >> for mapred action, better error reporting and many other bug
> >>fixes.
> >> > > >>
> >> > > >> Can we have a oozie release from trunk? If someone wants to
> >> volunteer
> >> > to
> >> > > >> drive the release, please take this forward. Else, I can drive
> >>it as
> >> > > >>well.
> >> > > >>
> >> > > >> If we want to do a release, let's identify the pending jiras
> >>which
> >> are
> >> > > >> required for this release.
> >> > > >>
> >> > > >> Thanks,
> >> > > >> Shwetha
> >> > > >>
> >> > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Harsh J
> >>
>
>
Re: [DISCUSSION] Oozie 4.2.0 release
Posted by Shwetha Shivalingamurthy <ss...@hortonworks.com>.
I am going to commit OOZIE-1963 and OOZIE-2240 and create rc0
-Shwetha
On 18/05/15 12:33 pm, "Shwetha Shivalingamurthy"
<ss...@hortonworks.com> wrote:
>Branch-4.2 is creates. You can resume commits
>
>Thanks,
>Shwetha
>
>On 18/05/15 12:04 pm, "Shwetha Shivalingamurthy"
><ss...@hortonworks.com> wrote:
>
>>Creating a branch for 4.2.0 release. Please hold off any commits to
>>master
>>until further email
>>
>>
>>OOZIE-2232 and OOZIE-2210 are committed already. We can merge OOZIE-1993,
>>OOZIE-2229 into the release branch once they are closed. Are there any
>>other pending issues for the release?
>>
>>
>>Thanks,
>>Shwetha
>>
>>
>>On 12/05/15 5:17 am, "bowen zhang" <bo...@yahoo.com.INVALID>
>>wrote:
>>
>>>I am adding [OOZIE-2232] Oozie should invalidate bulk write command when
>>>"-filter" is missing - ASF JIRA
>>>| |
>>>| | | | | |
>>>| [OOZIE-2232] Oozie should invalidate bulk write command when "-filter"
>>>is missing - ASF JIRAThere are no comments yet on this issue. |
>>>| |
>>>| View on issues.apache.org | Preview by Yahoo |
>>>| |
>>>| |
>>>
>>> to 4.2 release
>>> This fixed a command line usability hole after the creation of bulk
>>>write API
>>> From: Robert Kanter <rk...@cloudera.com>
>>> To: "dev@oozie.apache.org" <de...@oozie.apache.org>
>>> Sent: Thursday, May 7, 2015 10:56 AM
>>> Subject: Re: [DISCUSSION] Oozie 4.2.0 release
>>>
>>>Can we add OOZIE-2210 to 4.2.0? It updates the extjs link because it's
>>>currently not working again. People have been filing JIRAs for it.
>>>
>>>- Robert
>>>
>>>
>>>
>>>On Tue, Apr 28, 2015 at 12:18 PM, Robert Kanter <rk...@cloudera.com>
>>>wrote:
>>>
>>>> I just filed a new JIRA, which we should probably fix: some
>>>>directories
>>>>in
>>>> the war file have 777 permissions.
>>>> It's a pretty simple fix that I'll upload shortly.
>>>>
>>>> https://issues.apache.org/jira/browse/OOZIE-2218
>>>>
>>>> On Tue, Apr 28, 2015 at 4:27 AM, Shwetha Shivalingamurthy <
>>>> sshivalingamurthy@hortonworks.com> wrote:
>>>>
>>>>> Hello everyone,
>>>>>
>>>>> The pending(not resolved) jiras for this release so far are:
>>>>> OOZIE-1993 - its on me, patch available
>>>>> OOZIE-1963 - Harsh/Robert, can you close this please?
>>>>>
>>>>> Looks like all other jiras mentioned in this thread are resolved
>>>>>already.
>>>>> Thank you:)
>>>>>
>>>>> Are there any other issues required for this release?
>>>>>
>>>>> Thanks,
>>>>> Shwetha
>>>>>
>>>>> On 13/04/15 4:23 pm, "Shwetha Shivalingamurthy"
>>>>> <ss...@hortonworks.com> wrote:
>>>>>
>>>>> >Ryota, is this the only issue from regression?
>>>>> >
>>>>> >Dev team, does anyone want to take up OOZIE-1993?
>>>>> >
>>>>> >Regards,
>>>>> >Shwetha
>>>>> >
>>>>> >
>>>>> >On 10/04/15 12:38 am, "Ryota Egashira"
>>>>><eg...@yahoo-inc.com.INVALID>
>>>>> >wrote:
>>>>> >
>>>>> >>OOZIE-1993 need to be fixed before release.workflow rerun failed
>>>>>with
>>>>> >>oozie.wf.rerun.failnodes=true in some cases. actually because of
>>>>>this,
>>>>> we
>>>>> >>reverted OOZIE-1879 for our internal branch.
>>>>> >>
>>>>> >>ThanksRyota
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> On Thursday, March 26, 2015 4:57 PM, Robert Kanter
>>>>> >><rk...@cloudera.com> wrote:
>>>>> >>
>>>>> >>
>>>>> >> Another JIRA that would be good to get is OOZIE-2186 which updates
>>>>>the
>>>>> >>Tomcat version.
>>>>> >>
>>>>> >>On Thu, Mar 26, 2015 at 2:46 PM, Shwetha Shivalingamurthy <
>>>>> >>sshivalingamurthy@hortonworks.com> wrote:
>>>>> >>
>>>>> >>> Ok, I will wait for them. Thanks
>>>>> >>>
>>>>> >>>
>>>>> >>> On 26/03/15 2:21 pm, "Rohini Palaniswamy"
>>>>><ro...@gmail.com>
>>>>> >>>wrote:
>>>>> >>>
>>>>> >>> >We don't have a list of issues that need to be included. But
>>>>>Michelle
>>>>> >>>ran
>>>>> >>> >the regression with trunk yesterday and there were couple of
>>>>> failures.
>>>>> >>>We
>>>>> >>> >haven't investigated them yet. Those will have to be fixed
>>>>>though.
>>>>> >>>Ryota
>>>>> >>> >will file jiras and upload fixes next week after investigating
>>>>>them.
>>>>> >>> >
>>>>> >>> >Regards,
>>>>> >>> >Rohini
>>>>> >>> >
>>>>> >>> >On Thu, Mar 26, 2015 at 1:58 PM, Harsh J <ha...@cloudera.com>
>>>>>wrote:
>>>>> >>> >
>>>>> >>> >> I can take over OOZIE-1963. I need to test the modified
>>>>>hive(1)
>>>>> >>>example
>>>>> >>> >>and
>>>>> >>> >> will then attach the change to the JIRA.
>>>>> >>> >>
>>>>> >>> >> On Thu, Mar 26, 2015 at 6:20 AM, Robert Kanter
>>>>> >>><rk...@cloudera.com>
>>>>> >>> >> wrote:
>>>>> >>> >>
>>>>> >>> >> > I was hoping one of our QA engineers would take care of
>>>>>that,
>>>>>but
>>>>> >>>it
>>>>> >>> >> looks
>>>>> >>> >> > like he won't have time. I don't think I'm proficient
>>>>>enough
>>>>>in
>>>>> >>>Hive
>>>>> >>> >> > Server 2 to make the example, so I've unassigned OOZIE-1963
>>>>>from
>>>>> >>>me.
>>>>> >>> >> > Though I think it would still be good to include.
>>>>> >>> >> >
>>>>> >>> >> > If we include the Spark action, I think we should also
>>>>>include
>>>>> >>> >> OOZIE-2170.
>>>>> >>> >> > OOZIE-2174 would also be good; it addresses some
>>>>>long-standing
>>>>> >>> >> shortcomings
>>>>> >>> >> > of OozieClient/OozieCLI.
>>>>> >>> >> > Finally, we should also include OOZIE-2181, which fixes some
>>>>> >>>problems
>>>>> >>> >> > retrieving job info.
>>>>> >>> >> > I have patches available for all 3 of these.
>>>>> >>> >> >
>>>>> >>> >> >
>>>>> >>> >> > - Robert
>>>>> >>> >> >
>>>>> >>> >> > On Wed, Mar 25, 2015 at 10:58 AM, Shwetha Shivalingamurthy <
>>>>> >>> >> > sshivalingamurthy@hortonworks.com> wrote:
>>>>> >>> >> >
>>>>> >>> >> > > Robert, will you be able to take up OOZIE-1963?
>>>>> >>> >> > >
>>>>> >>> >> > > Dev team, Are there any other un-resolved jiras that needs
>>>>>to
>>>>> be
>>>>> >>> >>part
>>>>> >>> >> of
>>>>> >>> >> > > 4.2 release?
>>>>> >>> >> > >
>>>>> >>> >> > > Thanks,
>>>>> >>> >> > > Shwetha
>>>>> >>> >> > >
>>>>> >>> >> > >
>>>>> >>> >> > > On 11/02/15 1:44 pm, "Robert Kanter"
>>>>><rk...@cloudera.com>
>>>>> >>>wrote:
>>>>> >>> >> > >
>>>>> >>> >> > > >I 4.2.0 release sounds good; I don't have cycles to drive
>>>>>it
>>>>> >>> >>though.
>>>>> >>> >> > > >
>>>>> >>> >> > > >The Spark action currently has a number of problems with
>>>>>it.
>>>>> >>>I'd
>>>>> >>> >>hold
>>>>> >>> >> > off
>>>>> >>> >> > > >on putting that into a release until we get those fixed
>>>>> >>>(OOZIE-2071
>>>>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2071> (it's
>>>>>to
>>>>> add
>>>>> >>>an
>>>>> >>> >> > > >example,
>>>>> >>> >> > > >but the comments discuss the problems), OOZIE-2087
>>>>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2087>).
>>>>> >>> >> > > >
>>>>> >>> >> > > >I'm all for including the Hive2 action; though it would
>>>>>be
>>>>> good
>>>>> >>>if
>>>>> >>> >>we
>>>>> >>> >> > > >could
>>>>> >>> >> > > >create an example workflow for it for completeness
>>>>>(OOZIE-1963
>>>>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-1963>). I
>>>>>can
>>>>> >>> >>probably
>>>>> >>> >> > take
>>>>> >>> >> > > >care of this relatively easily.
>>>>> >>> >> > > >
>>>>> >>> >> > > >
>>>>> >>> >> > > >- Robert
>>>>> >>> >> > > >
>>>>> >>> >> > > >On Tue, Feb 10, 2015 at 9:56 PM, Shwetha Shivalingamurthy
>>>>><
>>>>> >>> >> > > >sshivalingamurthy@hortonworks.com> wrote:
>>>>> >>> >> > > >
>>>>> >>> >> > > >> Hi All,
>>>>> >>> >> > > >>
>>>>> >>> >> > > >> Oozie trunk has a couple of changes since the last
>>>>>oozie
>>>>> >>>release
>>>>> >>> >>-
>>>>> >>> >> > > >>re-run
>>>>> >>> >> > > >> fixes, config cleanup, spark action, hive2 action,
>>>>>external
>>>>> >>> >> > > >>configuration
>>>>> >>> >> > > >> for mapred action, better error reporting and many
>>>>>other
>>>>>bug
>>>>> >>> >>fixes.
>>>>> >>> >> > > >>
>>>>> >>> >> > > >> Can we have a oozie release from trunk? If someone
>>>>>wants
>>>>>to
>>>>> >>> >> volunteer
>>>>> >>> >> > to
>>>>> >>> >> > > >> drive the release, please take this forward. Else, I
>>>>>can
>>>>> >>>drive
>>>>> >>> >>it as
>>>>> >>> >> > > >>well.
>>>>> >>> >> > > >>
>>>>> >>> >> > > >> If we want to do a release, let's identify the pending
>>>>>jiras
>>>>> >>> >>which
>>>>> >>> >> are
>>>>> >>> >> > > >> required for this release.
>>>>> >>> >> > > >>
>>>>> >>> >> > > >> Thanks,
>>>>> >>> >> > > >> Shwetha
>>>>> >>> >> > > >>
>>>>> >>> >> > >
>>>>> >>> >> > >
>>>>> >>> >> >
>>>>> >>> >>
>>>>> >>> >>
>>>>> >>> >>
>>>>> >>> >> --
>>>>> >>> >> Harsh J
>>>>> >>> >>
>>>>> >>>
>>>>> >>>
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>
Re: [DISCUSSION] Oozie 4.2.0 release
Posted by Shwetha Shivalingamurthy <ss...@hortonworks.com>.
Branch-4.2 is creates. You can resume commits
Thanks,
Shwetha
On 18/05/15 12:04 pm, "Shwetha Shivalingamurthy"
<ss...@hortonworks.com> wrote:
>Creating a branch for 4.2.0 release. Please hold off any commits to master
>until further email
>
>
>OOZIE-2232 and OOZIE-2210 are committed already. We can merge OOZIE-1993,
>OOZIE-2229 into the release branch once they are closed. Are there any
>other pending issues for the release?
>
>
>Thanks,
>Shwetha
>
>
>On 12/05/15 5:17 am, "bowen zhang" <bo...@yahoo.com.INVALID>
>wrote:
>
>>I am adding [OOZIE-2232] Oozie should invalidate bulk write command when
>>"-filter" is missing - ASF JIRA
>>| |
>>| | | | | |
>>| [OOZIE-2232] Oozie should invalidate bulk write command when "-filter"
>>is missing - ASF JIRAThere are no comments yet on this issue. |
>>| |
>>| View on issues.apache.org | Preview by Yahoo |
>>| |
>>| |
>>
>> to 4.2 release
>> This fixed a command line usability hole after the creation of bulk
>>write API
>> From: Robert Kanter <rk...@cloudera.com>
>> To: "dev@oozie.apache.org" <de...@oozie.apache.org>
>> Sent: Thursday, May 7, 2015 10:56 AM
>> Subject: Re: [DISCUSSION] Oozie 4.2.0 release
>>
>>Can we add OOZIE-2210 to 4.2.0? It updates the extjs link because it's
>>currently not working again. People have been filing JIRAs for it.
>>
>>- Robert
>>
>>
>>
>>On Tue, Apr 28, 2015 at 12:18 PM, Robert Kanter <rk...@cloudera.com>
>>wrote:
>>
>>> I just filed a new JIRA, which we should probably fix: some directories
>>>in
>>> the war file have 777 permissions.
>>> It's a pretty simple fix that I'll upload shortly.
>>>
>>> https://issues.apache.org/jira/browse/OOZIE-2218
>>>
>>> On Tue, Apr 28, 2015 at 4:27 AM, Shwetha Shivalingamurthy <
>>> sshivalingamurthy@hortonworks.com> wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> The pending(not resolved) jiras for this release so far are:
>>>> OOZIE-1993 - its on me, patch available
>>>> OOZIE-1963 - Harsh/Robert, can you close this please?
>>>>
>>>> Looks like all other jiras mentioned in this thread are resolved
>>>>already.
>>>> Thank you:)
>>>>
>>>> Are there any other issues required for this release?
>>>>
>>>> Thanks,
>>>> Shwetha
>>>>
>>>> On 13/04/15 4:23 pm, "Shwetha Shivalingamurthy"
>>>> <ss...@hortonworks.com> wrote:
>>>>
>>>> >Ryota, is this the only issue from regression?
>>>> >
>>>> >Dev team, does anyone want to take up OOZIE-1993?
>>>> >
>>>> >Regards,
>>>> >Shwetha
>>>> >
>>>> >
>>>> >On 10/04/15 12:38 am, "Ryota Egashira"
>>>><eg...@yahoo-inc.com.INVALID>
>>>> >wrote:
>>>> >
>>>> >>OOZIE-1993 need to be fixed before release.workflow rerun failed
>>>>with
>>>> >>oozie.wf.rerun.failnodes=true in some cases. actually because of
>>>>this,
>>>> we
>>>> >>reverted OOZIE-1879 for our internal branch.
>>>> >>
>>>> >>ThanksRyota
>>>> >>
>>>> >>
>>>> >>
>>>> >> On Thursday, March 26, 2015 4:57 PM, Robert Kanter
>>>> >><rk...@cloudera.com> wrote:
>>>> >>
>>>> >>
>>>> >> Another JIRA that would be good to get is OOZIE-2186 which updates
>>>>the
>>>> >>Tomcat version.
>>>> >>
>>>> >>On Thu, Mar 26, 2015 at 2:46 PM, Shwetha Shivalingamurthy <
>>>> >>sshivalingamurthy@hortonworks.com> wrote:
>>>> >>
>>>> >>> Ok, I will wait for them. Thanks
>>>> >>>
>>>> >>>
>>>> >>> On 26/03/15 2:21 pm, "Rohini Palaniswamy"
>>>><ro...@gmail.com>
>>>> >>>wrote:
>>>> >>>
>>>> >>> >We don't have a list of issues that need to be included. But
>>>>Michelle
>>>> >>>ran
>>>> >>> >the regression with trunk yesterday and there were couple of
>>>> failures.
>>>> >>>We
>>>> >>> >haven't investigated them yet. Those will have to be fixed
>>>>though.
>>>> >>>Ryota
>>>> >>> >will file jiras and upload fixes next week after investigating
>>>>them.
>>>> >>> >
>>>> >>> >Regards,
>>>> >>> >Rohini
>>>> >>> >
>>>> >>> >On Thu, Mar 26, 2015 at 1:58 PM, Harsh J <ha...@cloudera.com>
>>>>wrote:
>>>> >>> >
>>>> >>> >> I can take over OOZIE-1963. I need to test the modified hive(1)
>>>> >>>example
>>>> >>> >>and
>>>> >>> >> will then attach the change to the JIRA.
>>>> >>> >>
>>>> >>> >> On Thu, Mar 26, 2015 at 6:20 AM, Robert Kanter
>>>> >>><rk...@cloudera.com>
>>>> >>> >> wrote:
>>>> >>> >>
>>>> >>> >> > I was hoping one of our QA engineers would take care of that,
>>>>but
>>>> >>>it
>>>> >>> >> looks
>>>> >>> >> > like he won't have time. I don't think I'm proficient enough
>>>>in
>>>> >>>Hive
>>>> >>> >> > Server 2 to make the example, so I've unassigned OOZIE-1963
>>>>from
>>>> >>>me.
>>>> >>> >> > Though I think it would still be good to include.
>>>> >>> >> >
>>>> >>> >> > If we include the Spark action, I think we should also
>>>>include
>>>> >>> >> OOZIE-2170.
>>>> >>> >> > OOZIE-2174 would also be good; it addresses some
>>>>long-standing
>>>> >>> >> shortcomings
>>>> >>> >> > of OozieClient/OozieCLI.
>>>> >>> >> > Finally, we should also include OOZIE-2181, which fixes some
>>>> >>>problems
>>>> >>> >> > retrieving job info.
>>>> >>> >> > I have patches available for all 3 of these.
>>>> >>> >> >
>>>> >>> >> >
>>>> >>> >> > - Robert
>>>> >>> >> >
>>>> >>> >> > On Wed, Mar 25, 2015 at 10:58 AM, Shwetha Shivalingamurthy <
>>>> >>> >> > sshivalingamurthy@hortonworks.com> wrote:
>>>> >>> >> >
>>>> >>> >> > > Robert, will you be able to take up OOZIE-1963?
>>>> >>> >> > >
>>>> >>> >> > > Dev team, Are there any other un-resolved jiras that needs
>>>>to
>>>> be
>>>> >>> >>part
>>>> >>> >> of
>>>> >>> >> > > 4.2 release?
>>>> >>> >> > >
>>>> >>> >> > > Thanks,
>>>> >>> >> > > Shwetha
>>>> >>> >> > >
>>>> >>> >> > >
>>>> >>> >> > > On 11/02/15 1:44 pm, "Robert Kanter" <rk...@cloudera.com>
>>>> >>>wrote:
>>>> >>> >> > >
>>>> >>> >> > > >I 4.2.0 release sounds good; I don't have cycles to drive
>>>>it
>>>> >>> >>though.
>>>> >>> >> > > >
>>>> >>> >> > > >The Spark action currently has a number of problems with
>>>>it.
>>>> >>>I'd
>>>> >>> >>hold
>>>> >>> >> > off
>>>> >>> >> > > >on putting that into a release until we get those fixed
>>>> >>>(OOZIE-2071
>>>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2071> (it's
>>>>to
>>>> add
>>>> >>>an
>>>> >>> >> > > >example,
>>>> >>> >> > > >but the comments discuss the problems), OOZIE-2087
>>>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2087>).
>>>> >>> >> > > >
>>>> >>> >> > > >I'm all for including the Hive2 action; though it would be
>>>> good
>>>> >>>if
>>>> >>> >>we
>>>> >>> >> > > >could
>>>> >>> >> > > >create an example workflow for it for completeness
>>>>(OOZIE-1963
>>>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-1963>). I
>>>>can
>>>> >>> >>probably
>>>> >>> >> > take
>>>> >>> >> > > >care of this relatively easily.
>>>> >>> >> > > >
>>>> >>> >> > > >
>>>> >>> >> > > >- Robert
>>>> >>> >> > > >
>>>> >>> >> > > >On Tue, Feb 10, 2015 at 9:56 PM, Shwetha Shivalingamurthy
>>>><
>>>> >>> >> > > >sshivalingamurthy@hortonworks.com> wrote:
>>>> >>> >> > > >
>>>> >>> >> > > >> Hi All,
>>>> >>> >> > > >>
>>>> >>> >> > > >> Oozie trunk has a couple of changes since the last oozie
>>>> >>>release
>>>> >>> >>-
>>>> >>> >> > > >>re-run
>>>> >>> >> > > >> fixes, config cleanup, spark action, hive2 action,
>>>>external
>>>> >>> >> > > >>configuration
>>>> >>> >> > > >> for mapred action, better error reporting and many other
>>>>bug
>>>> >>> >>fixes.
>>>> >>> >> > > >>
>>>> >>> >> > > >> Can we have a oozie release from trunk? If someone wants
>>>>to
>>>> >>> >> volunteer
>>>> >>> >> > to
>>>> >>> >> > > >> drive the release, please take this forward. Else, I can
>>>> >>>drive
>>>> >>> >>it as
>>>> >>> >> > > >>well.
>>>> >>> >> > > >>
>>>> >>> >> > > >> If we want to do a release, let's identify the pending
>>>>jiras
>>>> >>> >>which
>>>> >>> >> are
>>>> >>> >> > > >> required for this release.
>>>> >>> >> > > >>
>>>> >>> >> > > >> Thanks,
>>>> >>> >> > > >> Shwetha
>>>> >>> >> > > >>
>>>> >>> >> > >
>>>> >>> >> > >
>>>> >>> >> >
>>>> >>> >>
>>>> >>> >>
>>>> >>> >>
>>>> >>> >> --
>>>> >>> >> Harsh J
>>>> >>> >>
>>>> >>>
>>>> >>>
>>>> >>
>>>> >>
>>>> >>
>>>> >
>>>>
>>>>
>>>
>>
>>
>>
>
Re: [DISCUSSION] Oozie 4.2.0 release
Posted by Shwetha Shivalingamurthy <ss...@hortonworks.com>.
Creating a branch for 4.2.0 release. Please hold off any commits to master
until further email
OOZIE-2232 and OOZIE-2210 are committed already. We can merge OOZIE-1993,
OOZIE-2229 into the release branch once they are closed. Are there any
other pending issues for the release?
Thanks,
Shwetha
On 12/05/15 5:17 am, "bowen zhang" <bo...@yahoo.com.INVALID> wrote:
>I am adding [OOZIE-2232] Oozie should invalidate bulk write command when
>"-filter" is missing - ASF JIRA
>| |
>| | | | | |
>| [OOZIE-2232] Oozie should invalidate bulk write command when "-filter"
>is missing - ASF JIRAThere are no comments yet on this issue. |
>| |
>| View on issues.apache.org | Preview by Yahoo |
>| |
>| |
>
> to 4.2 release
> This fixed a command line usability hole after the creation of bulk
>write API
> From: Robert Kanter <rk...@cloudera.com>
> To: "dev@oozie.apache.org" <de...@oozie.apache.org>
> Sent: Thursday, May 7, 2015 10:56 AM
> Subject: Re: [DISCUSSION] Oozie 4.2.0 release
>
>Can we add OOZIE-2210 to 4.2.0? It updates the extjs link because it's
>currently not working again. People have been filing JIRAs for it.
>
>- Robert
>
>
>
>On Tue, Apr 28, 2015 at 12:18 PM, Robert Kanter <rk...@cloudera.com>
>wrote:
>
>> I just filed a new JIRA, which we should probably fix: some directories
>>in
>> the war file have 777 permissions.
>> It's a pretty simple fix that I'll upload shortly.
>>
>> https://issues.apache.org/jira/browse/OOZIE-2218
>>
>> On Tue, Apr 28, 2015 at 4:27 AM, Shwetha Shivalingamurthy <
>> sshivalingamurthy@hortonworks.com> wrote:
>>
>>> Hello everyone,
>>>
>>> The pending(not resolved) jiras for this release so far are:
>>> OOZIE-1993 - its on me, patch available
>>> OOZIE-1963 - Harsh/Robert, can you close this please?
>>>
>>> Looks like all other jiras mentioned in this thread are resolved
>>>already.
>>> Thank you:)
>>>
>>> Are there any other issues required for this release?
>>>
>>> Thanks,
>>> Shwetha
>>>
>>> On 13/04/15 4:23 pm, "Shwetha Shivalingamurthy"
>>> <ss...@hortonworks.com> wrote:
>>>
>>> >Ryota, is this the only issue from regression?
>>> >
>>> >Dev team, does anyone want to take up OOZIE-1993?
>>> >
>>> >Regards,
>>> >Shwetha
>>> >
>>> >
>>> >On 10/04/15 12:38 am, "Ryota Egashira"
>>><eg...@yahoo-inc.com.INVALID>
>>> >wrote:
>>> >
>>> >>OOZIE-1993 need to be fixed before release.workflow rerun failed with
>>> >>oozie.wf.rerun.failnodes=true in some cases. actually because of
>>>this,
>>> we
>>> >>reverted OOZIE-1879 for our internal branch.
>>> >>
>>> >>ThanksRyota
>>> >>
>>> >>
>>> >>
>>> >> On Thursday, March 26, 2015 4:57 PM, Robert Kanter
>>> >><rk...@cloudera.com> wrote:
>>> >>
>>> >>
>>> >> Another JIRA that would be good to get is OOZIE-2186 which updates
>>>the
>>> >>Tomcat version.
>>> >>
>>> >>On Thu, Mar 26, 2015 at 2:46 PM, Shwetha Shivalingamurthy <
>>> >>sshivalingamurthy@hortonworks.com> wrote:
>>> >>
>>> >>> Ok, I will wait for them. Thanks
>>> >>>
>>> >>>
>>> >>> On 26/03/15 2:21 pm, "Rohini Palaniswamy" <ro...@gmail.com>
>>> >>>wrote:
>>> >>>
>>> >>> >We don't have a list of issues that need to be included. But
>>>Michelle
>>> >>>ran
>>> >>> >the regression with trunk yesterday and there were couple of
>>> failures.
>>> >>>We
>>> >>> >haven't investigated them yet. Those will have to be fixed though.
>>> >>>Ryota
>>> >>> >will file jiras and upload fixes next week after investigating
>>>them.
>>> >>> >
>>> >>> >Regards,
>>> >>> >Rohini
>>> >>> >
>>> >>> >On Thu, Mar 26, 2015 at 1:58 PM, Harsh J <ha...@cloudera.com>
>>>wrote:
>>> >>> >
>>> >>> >> I can take over OOZIE-1963. I need to test the modified hive(1)
>>> >>>example
>>> >>> >>and
>>> >>> >> will then attach the change to the JIRA.
>>> >>> >>
>>> >>> >> On Thu, Mar 26, 2015 at 6:20 AM, Robert Kanter
>>> >>><rk...@cloudera.com>
>>> >>> >> wrote:
>>> >>> >>
>>> >>> >> > I was hoping one of our QA engineers would take care of that,
>>>but
>>> >>>it
>>> >>> >> looks
>>> >>> >> > like he won't have time. I don't think I'm proficient enough
>>>in
>>> >>>Hive
>>> >>> >> > Server 2 to make the example, so I've unassigned OOZIE-1963
>>>from
>>> >>>me.
>>> >>> >> > Though I think it would still be good to include.
>>> >>> >> >
>>> >>> >> > If we include the Spark action, I think we should also include
>>> >>> >> OOZIE-2170.
>>> >>> >> > OOZIE-2174 would also be good; it addresses some long-standing
>>> >>> >> shortcomings
>>> >>> >> > of OozieClient/OozieCLI.
>>> >>> >> > Finally, we should also include OOZIE-2181, which fixes some
>>> >>>problems
>>> >>> >> > retrieving job info.
>>> >>> >> > I have patches available for all 3 of these.
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > - Robert
>>> >>> >> >
>>> >>> >> > On Wed, Mar 25, 2015 at 10:58 AM, Shwetha Shivalingamurthy <
>>> >>> >> > sshivalingamurthy@hortonworks.com> wrote:
>>> >>> >> >
>>> >>> >> > > Robert, will you be able to take up OOZIE-1963?
>>> >>> >> > >
>>> >>> >> > > Dev team, Are there any other un-resolved jiras that needs
>>>to
>>> be
>>> >>> >>part
>>> >>> >> of
>>> >>> >> > > 4.2 release?
>>> >>> >> > >
>>> >>> >> > > Thanks,
>>> >>> >> > > Shwetha
>>> >>> >> > >
>>> >>> >> > >
>>> >>> >> > > On 11/02/15 1:44 pm, "Robert Kanter" <rk...@cloudera.com>
>>> >>>wrote:
>>> >>> >> > >
>>> >>> >> > > >I 4.2.0 release sounds good; I don't have cycles to drive
>>>it
>>> >>> >>though.
>>> >>> >> > > >
>>> >>> >> > > >The Spark action currently has a number of problems with
>>>it.
>>> >>>I'd
>>> >>> >>hold
>>> >>> >> > off
>>> >>> >> > > >on putting that into a release until we get those fixed
>>> >>>(OOZIE-2071
>>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2071> (it's to
>>> add
>>> >>>an
>>> >>> >> > > >example,
>>> >>> >> > > >but the comments discuss the problems), OOZIE-2087
>>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2087>).
>>> >>> >> > > >
>>> >>> >> > > >I'm all for including the Hive2 action; though it would be
>>> good
>>> >>>if
>>> >>> >>we
>>> >>> >> > > >could
>>> >>> >> > > >create an example workflow for it for completeness
>>>(OOZIE-1963
>>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-1963>). I can
>>> >>> >>probably
>>> >>> >> > take
>>> >>> >> > > >care of this relatively easily.
>>> >>> >> > > >
>>> >>> >> > > >
>>> >>> >> > > >- Robert
>>> >>> >> > > >
>>> >>> >> > > >On Tue, Feb 10, 2015 at 9:56 PM, Shwetha Shivalingamurthy <
>>> >>> >> > > >sshivalingamurthy@hortonworks.com> wrote:
>>> >>> >> > > >
>>> >>> >> > > >> Hi All,
>>> >>> >> > > >>
>>> >>> >> > > >> Oozie trunk has a couple of changes since the last oozie
>>> >>>release
>>> >>> >>-
>>> >>> >> > > >>re-run
>>> >>> >> > > >> fixes, config cleanup, spark action, hive2 action,
>>>external
>>> >>> >> > > >>configuration
>>> >>> >> > > >> for mapred action, better error reporting and many other
>>>bug
>>> >>> >>fixes.
>>> >>> >> > > >>
>>> >>> >> > > >> Can we have a oozie release from trunk? If someone wants
>>>to
>>> >>> >> volunteer
>>> >>> >> > to
>>> >>> >> > > >> drive the release, please take this forward. Else, I can
>>> >>>drive
>>> >>> >>it as
>>> >>> >> > > >>well.
>>> >>> >> > > >>
>>> >>> >> > > >> If we want to do a release, let's identify the pending
>>>jiras
>>> >>> >>which
>>> >>> >> are
>>> >>> >> > > >> required for this release.
>>> >>> >> > > >>
>>> >>> >> > > >> Thanks,
>>> >>> >> > > >> Shwetha
>>> >>> >> > > >>
>>> >>> >> > >
>>> >>> >> > >
>>> >>> >> >
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> --
>>> >>> >> Harsh J
>>> >>> >>
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >
>>>
>>>
>>
>
>
>
Re: [DISCUSSION] Oozie 4.2.0 release
Posted by bowen zhang <bo...@yahoo.com.INVALID>.
I am adding [OOZIE-2232] Oozie should invalidate bulk write command when "-filter" is missing - ASF JIRA
| |
| | | | | |
| [OOZIE-2232] Oozie should invalidate bulk write command when "-filter" is missing - ASF JIRAThere are no comments yet on this issue. |
| |
| View on issues.apache.org | Preview by Yahoo |
| |
| |
to 4.2 release
This fixed a command line usability hole after the creation of bulk write API
From: Robert Kanter <rk...@cloudera.com>
To: "dev@oozie.apache.org" <de...@oozie.apache.org>
Sent: Thursday, May 7, 2015 10:56 AM
Subject: Re: [DISCUSSION] Oozie 4.2.0 release
Can we add OOZIE-2210 to 4.2.0? It updates the extjs link because it's
currently not working again. People have been filing JIRAs for it.
- Robert
On Tue, Apr 28, 2015 at 12:18 PM, Robert Kanter <rk...@cloudera.com>
wrote:
> I just filed a new JIRA, which we should probably fix: some directories in
> the war file have 777 permissions.
> It's a pretty simple fix that I'll upload shortly.
>
> https://issues.apache.org/jira/browse/OOZIE-2218
>
> On Tue, Apr 28, 2015 at 4:27 AM, Shwetha Shivalingamurthy <
> sshivalingamurthy@hortonworks.com> wrote:
>
>> Hello everyone,
>>
>> The pending(not resolved) jiras for this release so far are:
>> OOZIE-1993 - its on me, patch available
>> OOZIE-1963 - Harsh/Robert, can you close this please?
>>
>> Looks like all other jiras mentioned in this thread are resolved already.
>> Thank you:)
>>
>> Are there any other issues required for this release?
>>
>> Thanks,
>> Shwetha
>>
>> On 13/04/15 4:23 pm, "Shwetha Shivalingamurthy"
>> <ss...@hortonworks.com> wrote:
>>
>> >Ryota, is this the only issue from regression?
>> >
>> >Dev team, does anyone want to take up OOZIE-1993?
>> >
>> >Regards,
>> >Shwetha
>> >
>> >
>> >On 10/04/15 12:38 am, "Ryota Egashira" <eg...@yahoo-inc.com.INVALID>
>> >wrote:
>> >
>> >>OOZIE-1993 need to be fixed before release.workflow rerun failed with
>> >>oozie.wf.rerun.failnodes=true in some cases. actually because of this,
>> we
>> >>reverted OOZIE-1879 for our internal branch.
>> >>
>> >>ThanksRyota
>> >>
>> >>
>> >>
>> >> On Thursday, March 26, 2015 4:57 PM, Robert Kanter
>> >><rk...@cloudera.com> wrote:
>> >>
>> >>
>> >> Another JIRA that would be good to get is OOZIE-2186 which updates the
>> >>Tomcat version.
>> >>
>> >>On Thu, Mar 26, 2015 at 2:46 PM, Shwetha Shivalingamurthy <
>> >>sshivalingamurthy@hortonworks.com> wrote:
>> >>
>> >>> Ok, I will wait for them. Thanks
>> >>>
>> >>>
>> >>> On 26/03/15 2:21 pm, "Rohini Palaniswamy" <ro...@gmail.com>
>> >>>wrote:
>> >>>
>> >>> >We don't have a list of issues that need to be included. But Michelle
>> >>>ran
>> >>> >the regression with trunk yesterday and there were couple of
>> failures.
>> >>>We
>> >>> >haven't investigated them yet. Those will have to be fixed though.
>> >>>Ryota
>> >>> >will file jiras and upload fixes next week after investigating them.
>> >>> >
>> >>> >Regards,
>> >>> >Rohini
>> >>> >
>> >>> >On Thu, Mar 26, 2015 at 1:58 PM, Harsh J <ha...@cloudera.com> wrote:
>> >>> >
>> >>> >> I can take over OOZIE-1963. I need to test the modified hive(1)
>> >>>example
>> >>> >>and
>> >>> >> will then attach the change to the JIRA.
>> >>> >>
>> >>> >> On Thu, Mar 26, 2015 at 6:20 AM, Robert Kanter
>> >>><rk...@cloudera.com>
>> >>> >> wrote:
>> >>> >>
>> >>> >> > I was hoping one of our QA engineers would take care of that, but
>> >>>it
>> >>> >> looks
>> >>> >> > like he won't have time. I don't think I'm proficient enough in
>> >>>Hive
>> >>> >> > Server 2 to make the example, so I've unassigned OOZIE-1963 from
>> >>>me.
>> >>> >> > Though I think it would still be good to include.
>> >>> >> >
>> >>> >> > If we include the Spark action, I think we should also include
>> >>> >> OOZIE-2170.
>> >>> >> > OOZIE-2174 would also be good; it addresses some long-standing
>> >>> >> shortcomings
>> >>> >> > of OozieClient/OozieCLI.
>> >>> >> > Finally, we should also include OOZIE-2181, which fixes some
>> >>>problems
>> >>> >> > retrieving job info.
>> >>> >> > I have patches available for all 3 of these.
>> >>> >> >
>> >>> >> >
>> >>> >> > - Robert
>> >>> >> >
>> >>> >> > On Wed, Mar 25, 2015 at 10:58 AM, Shwetha Shivalingamurthy <
>> >>> >> > sshivalingamurthy@hortonworks.com> wrote:
>> >>> >> >
>> >>> >> > > Robert, will you be able to take up OOZIE-1963?
>> >>> >> > >
>> >>> >> > > Dev team, Are there any other un-resolved jiras that needs to
>> be
>> >>> >>part
>> >>> >> of
>> >>> >> > > 4.2 release?
>> >>> >> > >
>> >>> >> > > Thanks,
>> >>> >> > > Shwetha
>> >>> >> > >
>> >>> >> > >
>> >>> >> > > On 11/02/15 1:44 pm, "Robert Kanter" <rk...@cloudera.com>
>> >>>wrote:
>> >>> >> > >
>> >>> >> > > >I 4.2.0 release sounds good; I don't have cycles to drive it
>> >>> >>though.
>> >>> >> > > >
>> >>> >> > > >The Spark action currently has a number of problems with it.
>> >>>I'd
>> >>> >>hold
>> >>> >> > off
>> >>> >> > > >on putting that into a release until we get those fixed
>> >>>(OOZIE-2071
>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2071> (it's to
>> add
>> >>>an
>> >>> >> > > >example,
>> >>> >> > > >but the comments discuss the problems), OOZIE-2087
>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2087>).
>> >>> >> > > >
>> >>> >> > > >I'm all for including the Hive2 action; though it would be
>> good
>> >>>if
>> >>> >>we
>> >>> >> > > >could
>> >>> >> > > >create an example workflow for it for completeness (OOZIE-1963
>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-1963>). I can
>> >>> >>probably
>> >>> >> > take
>> >>> >> > > >care of this relatively easily.
>> >>> >> > > >
>> >>> >> > > >
>> >>> >> > > >- Robert
>> >>> >> > > >
>> >>> >> > > >On Tue, Feb 10, 2015 at 9:56 PM, Shwetha Shivalingamurthy <
>> >>> >> > > >sshivalingamurthy@hortonworks.com> wrote:
>> >>> >> > > >
>> >>> >> > > >> Hi All,
>> >>> >> > > >>
>> >>> >> > > >> Oozie trunk has a couple of changes since the last oozie
>> >>>release
>> >>> >>-
>> >>> >> > > >>re-run
>> >>> >> > > >> fixes, config cleanup, spark action, hive2 action, external
>> >>> >> > > >>configuration
>> >>> >> > > >> for mapred action, better error reporting and many other bug
>> >>> >>fixes.
>> >>> >> > > >>
>> >>> >> > > >> Can we have a oozie release from trunk? If someone wants to
>> >>> >> volunteer
>> >>> >> > to
>> >>> >> > > >> drive the release, please take this forward. Else, I can
>> >>>drive
>> >>> >>it as
>> >>> >> > > >>well.
>> >>> >> > > >>
>> >>> >> > > >> If we want to do a release, let's identify the pending jiras
>> >>> >>which
>> >>> >> are
>> >>> >> > > >> required for this release.
>> >>> >> > > >>
>> >>> >> > > >> Thanks,
>> >>> >> > > >> Shwetha
>> >>> >> > > >>
>> >>> >> > >
>> >>> >> > >
>> >>> >> >
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> --
>> >>> >> Harsh J
>> >>> >>
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >
>>
>>
>
Re: [DISCUSSION] Oozie 4.2.0 release
Posted by Robert Kanter <rk...@cloudera.com>.
Can we add OOZIE-2210 to 4.2.0? It updates the extjs link because it's
currently not working again. People have been filing JIRAs for it.
- Robert
On Tue, Apr 28, 2015 at 12:18 PM, Robert Kanter <rk...@cloudera.com>
wrote:
> I just filed a new JIRA, which we should probably fix: some directories in
> the war file have 777 permissions.
> It's a pretty simple fix that I'll upload shortly.
>
> https://issues.apache.org/jira/browse/OOZIE-2218
>
> On Tue, Apr 28, 2015 at 4:27 AM, Shwetha Shivalingamurthy <
> sshivalingamurthy@hortonworks.com> wrote:
>
>> Hello everyone,
>>
>> The pending(not resolved) jiras for this release so far are:
>> OOZIE-1993 - its on me, patch available
>> OOZIE-1963 - Harsh/Robert, can you close this please?
>>
>> Looks like all other jiras mentioned in this thread are resolved already.
>> Thank you:)
>>
>> Are there any other issues required for this release?
>>
>> Thanks,
>> Shwetha
>>
>> On 13/04/15 4:23 pm, "Shwetha Shivalingamurthy"
>> <ss...@hortonworks.com> wrote:
>>
>> >Ryota, is this the only issue from regression?
>> >
>> >Dev team, does anyone want to take up OOZIE-1993?
>> >
>> >Regards,
>> >Shwetha
>> >
>> >
>> >On 10/04/15 12:38 am, "Ryota Egashira" <eg...@yahoo-inc.com.INVALID>
>> >wrote:
>> >
>> >>OOZIE-1993 need to be fixed before release.workflow rerun failed with
>> >>oozie.wf.rerun.failnodes=true in some cases. actually because of this,
>> we
>> >>reverted OOZIE-1879 for our internal branch.
>> >>
>> >>ThanksRyota
>> >>
>> >>
>> >>
>> >> On Thursday, March 26, 2015 4:57 PM, Robert Kanter
>> >><rk...@cloudera.com> wrote:
>> >>
>> >>
>> >> Another JIRA that would be good to get is OOZIE-2186 which updates the
>> >>Tomcat version.
>> >>
>> >>On Thu, Mar 26, 2015 at 2:46 PM, Shwetha Shivalingamurthy <
>> >>sshivalingamurthy@hortonworks.com> wrote:
>> >>
>> >>> Ok, I will wait for them. Thanks
>> >>>
>> >>>
>> >>> On 26/03/15 2:21 pm, "Rohini Palaniswamy" <ro...@gmail.com>
>> >>>wrote:
>> >>>
>> >>> >We don't have a list of issues that need to be included. But Michelle
>> >>>ran
>> >>> >the regression with trunk yesterday and there were couple of
>> failures.
>> >>>We
>> >>> >haven't investigated them yet. Those will have to be fixed though.
>> >>>Ryota
>> >>> >will file jiras and upload fixes next week after investigating them.
>> >>> >
>> >>> >Regards,
>> >>> >Rohini
>> >>> >
>> >>> >On Thu, Mar 26, 2015 at 1:58 PM, Harsh J <ha...@cloudera.com> wrote:
>> >>> >
>> >>> >> I can take over OOZIE-1963. I need to test the modified hive(1)
>> >>>example
>> >>> >>and
>> >>> >> will then attach the change to the JIRA.
>> >>> >>
>> >>> >> On Thu, Mar 26, 2015 at 6:20 AM, Robert Kanter
>> >>><rk...@cloudera.com>
>> >>> >> wrote:
>> >>> >>
>> >>> >> > I was hoping one of our QA engineers would take care of that, but
>> >>>it
>> >>> >> looks
>> >>> >> > like he won't have time. I don't think I'm proficient enough in
>> >>>Hive
>> >>> >> > Server 2 to make the example, so I've unassigned OOZIE-1963 from
>> >>>me.
>> >>> >> > Though I think it would still be good to include.
>> >>> >> >
>> >>> >> > If we include the Spark action, I think we should also include
>> >>> >> OOZIE-2170.
>> >>> >> > OOZIE-2174 would also be good; it addresses some long-standing
>> >>> >> shortcomings
>> >>> >> > of OozieClient/OozieCLI.
>> >>> >> > Finally, we should also include OOZIE-2181, which fixes some
>> >>>problems
>> >>> >> > retrieving job info.
>> >>> >> > I have patches available for all 3 of these.
>> >>> >> >
>> >>> >> >
>> >>> >> > - Robert
>> >>> >> >
>> >>> >> > On Wed, Mar 25, 2015 at 10:58 AM, Shwetha Shivalingamurthy <
>> >>> >> > sshivalingamurthy@hortonworks.com> wrote:
>> >>> >> >
>> >>> >> > > Robert, will you be able to take up OOZIE-1963?
>> >>> >> > >
>> >>> >> > > Dev team, Are there any other un-resolved jiras that needs to
>> be
>> >>> >>part
>> >>> >> of
>> >>> >> > > 4.2 release?
>> >>> >> > >
>> >>> >> > > Thanks,
>> >>> >> > > Shwetha
>> >>> >> > >
>> >>> >> > >
>> >>> >> > > On 11/02/15 1:44 pm, "Robert Kanter" <rk...@cloudera.com>
>> >>>wrote:
>> >>> >> > >
>> >>> >> > > >I 4.2.0 release sounds good; I don't have cycles to drive it
>> >>> >>though.
>> >>> >> > > >
>> >>> >> > > >The Spark action currently has a number of problems with it.
>> >>>I'd
>> >>> >>hold
>> >>> >> > off
>> >>> >> > > >on putting that into a release until we get those fixed
>> >>>(OOZIE-2071
>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2071> (it's to
>> add
>> >>>an
>> >>> >> > > >example,
>> >>> >> > > >but the comments discuss the problems), OOZIE-2087
>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2087>).
>> >>> >> > > >
>> >>> >> > > >I'm all for including the Hive2 action; though it would be
>> good
>> >>>if
>> >>> >>we
>> >>> >> > > >could
>> >>> >> > > >create an example workflow for it for completeness (OOZIE-1963
>> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-1963>). I can
>> >>> >>probably
>> >>> >> > take
>> >>> >> > > >care of this relatively easily.
>> >>> >> > > >
>> >>> >> > > >
>> >>> >> > > >- Robert
>> >>> >> > > >
>> >>> >> > > >On Tue, Feb 10, 2015 at 9:56 PM, Shwetha Shivalingamurthy <
>> >>> >> > > >sshivalingamurthy@hortonworks.com> wrote:
>> >>> >> > > >
>> >>> >> > > >> Hi All,
>> >>> >> > > >>
>> >>> >> > > >> Oozie trunk has a couple of changes since the last oozie
>> >>>release
>> >>> >>-
>> >>> >> > > >>re-run
>> >>> >> > > >> fixes, config cleanup, spark action, hive2 action, external
>> >>> >> > > >>configuration
>> >>> >> > > >> for mapred action, better error reporting and many other bug
>> >>> >>fixes.
>> >>> >> > > >>
>> >>> >> > > >> Can we have a oozie release from trunk? If someone wants to
>> >>> >> volunteer
>> >>> >> > to
>> >>> >> > > >> drive the release, please take this forward. Else, I can
>> >>>drive
>> >>> >>it as
>> >>> >> > > >>well.
>> >>> >> > > >>
>> >>> >> > > >> If we want to do a release, let's identify the pending jiras
>> >>> >>which
>> >>> >> are
>> >>> >> > > >> required for this release.
>> >>> >> > > >>
>> >>> >> > > >> Thanks,
>> >>> >> > > >> Shwetha
>> >>> >> > > >>
>> >>> >> > >
>> >>> >> > >
>> >>> >> >
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> --
>> >>> >> Harsh J
>> >>> >>
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >
>>
>>
>
Re: [DISCUSSION] Oozie 4.2.0 release
Posted by Robert Kanter <rk...@cloudera.com>.
I just filed a new JIRA, which we should probably fix: some directories in
the war file have 777 permissions.
It's a pretty simple fix that I'll upload shortly.
https://issues.apache.org/jira/browse/OOZIE-2218
On Tue, Apr 28, 2015 at 4:27 AM, Shwetha Shivalingamurthy <
sshivalingamurthy@hortonworks.com> wrote:
> Hello everyone,
>
> The pending(not resolved) jiras for this release so far are:
> OOZIE-1993 - its on me, patch available
> OOZIE-1963 - Harsh/Robert, can you close this please?
>
> Looks like all other jiras mentioned in this thread are resolved already.
> Thank you:)
>
> Are there any other issues required for this release?
>
> Thanks,
> Shwetha
>
> On 13/04/15 4:23 pm, "Shwetha Shivalingamurthy"
> <ss...@hortonworks.com> wrote:
>
> >Ryota, is this the only issue from regression?
> >
> >Dev team, does anyone want to take up OOZIE-1993?
> >
> >Regards,
> >Shwetha
> >
> >
> >On 10/04/15 12:38 am, "Ryota Egashira" <eg...@yahoo-inc.com.INVALID>
> >wrote:
> >
> >>OOZIE-1993 need to be fixed before release.workflow rerun failed with
> >>oozie.wf.rerun.failnodes=true in some cases. actually because of this, we
> >>reverted OOZIE-1879 for our internal branch.
> >>
> >>ThanksRyota
> >>
> >>
> >>
> >> On Thursday, March 26, 2015 4:57 PM, Robert Kanter
> >><rk...@cloudera.com> wrote:
> >>
> >>
> >> Another JIRA that would be good to get is OOZIE-2186 which updates the
> >>Tomcat version.
> >>
> >>On Thu, Mar 26, 2015 at 2:46 PM, Shwetha Shivalingamurthy <
> >>sshivalingamurthy@hortonworks.com> wrote:
> >>
> >>> Ok, I will wait for them. Thanks
> >>>
> >>>
> >>> On 26/03/15 2:21 pm, "Rohini Palaniswamy" <ro...@gmail.com>
> >>>wrote:
> >>>
> >>> >We don't have a list of issues that need to be included. But Michelle
> >>>ran
> >>> >the regression with trunk yesterday and there were couple of failures.
> >>>We
> >>> >haven't investigated them yet. Those will have to be fixed though.
> >>>Ryota
> >>> >will file jiras and upload fixes next week after investigating them.
> >>> >
> >>> >Regards,
> >>> >Rohini
> >>> >
> >>> >On Thu, Mar 26, 2015 at 1:58 PM, Harsh J <ha...@cloudera.com> wrote:
> >>> >
> >>> >> I can take over OOZIE-1963. I need to test the modified hive(1)
> >>>example
> >>> >>and
> >>> >> will then attach the change to the JIRA.
> >>> >>
> >>> >> On Thu, Mar 26, 2015 at 6:20 AM, Robert Kanter
> >>><rk...@cloudera.com>
> >>> >> wrote:
> >>> >>
> >>> >> > I was hoping one of our QA engineers would take care of that, but
> >>>it
> >>> >> looks
> >>> >> > like he won't have time. I don't think I'm proficient enough in
> >>>Hive
> >>> >> > Server 2 to make the example, so I've unassigned OOZIE-1963 from
> >>>me.
> >>> >> > Though I think it would still be good to include.
> >>> >> >
> >>> >> > If we include the Spark action, I think we should also include
> >>> >> OOZIE-2170.
> >>> >> > OOZIE-2174 would also be good; it addresses some long-standing
> >>> >> shortcomings
> >>> >> > of OozieClient/OozieCLI.
> >>> >> > Finally, we should also include OOZIE-2181, which fixes some
> >>>problems
> >>> >> > retrieving job info.
> >>> >> > I have patches available for all 3 of these.
> >>> >> >
> >>> >> >
> >>> >> > - Robert
> >>> >> >
> >>> >> > On Wed, Mar 25, 2015 at 10:58 AM, Shwetha Shivalingamurthy <
> >>> >> > sshivalingamurthy@hortonworks.com> wrote:
> >>> >> >
> >>> >> > > Robert, will you be able to take up OOZIE-1963?
> >>> >> > >
> >>> >> > > Dev team, Are there any other un-resolved jiras that needs to be
> >>> >>part
> >>> >> of
> >>> >> > > 4.2 release?
> >>> >> > >
> >>> >> > > Thanks,
> >>> >> > > Shwetha
> >>> >> > >
> >>> >> > >
> >>> >> > > On 11/02/15 1:44 pm, "Robert Kanter" <rk...@cloudera.com>
> >>>wrote:
> >>> >> > >
> >>> >> > > >I 4.2.0 release sounds good; I don't have cycles to drive it
> >>> >>though.
> >>> >> > > >
> >>> >> > > >The Spark action currently has a number of problems with it.
> >>>I'd
> >>> >>hold
> >>> >> > off
> >>> >> > > >on putting that into a release until we get those fixed
> >>>(OOZIE-2071
> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2071> (it's to
> add
> >>>an
> >>> >> > > >example,
> >>> >> > > >but the comments discuss the problems), OOZIE-2087
> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2087>).
> >>> >> > > >
> >>> >> > > >I'm all for including the Hive2 action; though it would be good
> >>>if
> >>> >>we
> >>> >> > > >could
> >>> >> > > >create an example workflow for it for completeness (OOZIE-1963
> >>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-1963>). I can
> >>> >>probably
> >>> >> > take
> >>> >> > > >care of this relatively easily.
> >>> >> > > >
> >>> >> > > >
> >>> >> > > >- Robert
> >>> >> > > >
> >>> >> > > >On Tue, Feb 10, 2015 at 9:56 PM, Shwetha Shivalingamurthy <
> >>> >> > > >sshivalingamurthy@hortonworks.com> wrote:
> >>> >> > > >
> >>> >> > > >> Hi All,
> >>> >> > > >>
> >>> >> > > >> Oozie trunk has a couple of changes since the last oozie
> >>>release
> >>> >>-
> >>> >> > > >>re-run
> >>> >> > > >> fixes, config cleanup, spark action, hive2 action, external
> >>> >> > > >>configuration
> >>> >> > > >> for mapred action, better error reporting and many other bug
> >>> >>fixes.
> >>> >> > > >>
> >>> >> > > >> Can we have a oozie release from trunk? If someone wants to
> >>> >> volunteer
> >>> >> > to
> >>> >> > > >> drive the release, please take this forward. Else, I can
> >>>drive
> >>> >>it as
> >>> >> > > >>well.
> >>> >> > > >>
> >>> >> > > >> If we want to do a release, let's identify the pending jiras
> >>> >>which
> >>> >> are
> >>> >> > > >> required for this release.
> >>> >> > > >>
> >>> >> > > >> Thanks,
> >>> >> > > >> Shwetha
> >>> >> > > >>
> >>> >> > >
> >>> >> > >
> >>> >> >
> >>> >>
> >>> >>
> >>> >>
> >>> >> --
> >>> >> Harsh J
> >>> >>
> >>>
> >>>
> >>
> >>
> >>
> >
>
>
Re: [DISCUSSION] Oozie 4.2.0 release
Posted by Shwetha Shivalingamurthy <ss...@hortonworks.com>.
Hello everyone,
The pending(not resolved) jiras for this release so far are:
OOZIE-1993 - its on me, patch available
OOZIE-1963 - Harsh/Robert, can you close this please?
Looks like all other jiras mentioned in this thread are resolved already.
Thank you:)
Are there any other issues required for this release?
Thanks,
Shwetha
On 13/04/15 4:23 pm, "Shwetha Shivalingamurthy"
<ss...@hortonworks.com> wrote:
>Ryota, is this the only issue from regression?
>
>Dev team, does anyone want to take up OOZIE-1993?
>
>Regards,
>Shwetha
>
>
>On 10/04/15 12:38 am, "Ryota Egashira" <eg...@yahoo-inc.com.INVALID>
>wrote:
>
>>OOZIE-1993 need to be fixed before release.workflow rerun failed with
>>oozie.wf.rerun.failnodes=true in some cases. actually because of this, we
>>reverted OOZIE-1879 for our internal branch.
>>
>>ThanksRyota
>>
>>
>>
>> On Thursday, March 26, 2015 4:57 PM, Robert Kanter
>><rk...@cloudera.com> wrote:
>>
>>
>> Another JIRA that would be good to get is OOZIE-2186 which updates the
>>Tomcat version.
>>
>>On Thu, Mar 26, 2015 at 2:46 PM, Shwetha Shivalingamurthy <
>>sshivalingamurthy@hortonworks.com> wrote:
>>
>>> Ok, I will wait for them. Thanks
>>>
>>>
>>> On 26/03/15 2:21 pm, "Rohini Palaniswamy" <ro...@gmail.com>
>>>wrote:
>>>
>>> >We don't have a list of issues that need to be included. But Michelle
>>>ran
>>> >the regression with trunk yesterday and there were couple of failures.
>>>We
>>> >haven't investigated them yet. Those will have to be fixed though.
>>>Ryota
>>> >will file jiras and upload fixes next week after investigating them.
>>> >
>>> >Regards,
>>> >Rohini
>>> >
>>> >On Thu, Mar 26, 2015 at 1:58 PM, Harsh J <ha...@cloudera.com> wrote:
>>> >
>>> >> I can take over OOZIE-1963. I need to test the modified hive(1)
>>>example
>>> >>and
>>> >> will then attach the change to the JIRA.
>>> >>
>>> >> On Thu, Mar 26, 2015 at 6:20 AM, Robert Kanter
>>><rk...@cloudera.com>
>>> >> wrote:
>>> >>
>>> >> > I was hoping one of our QA engineers would take care of that, but
>>>it
>>> >> looks
>>> >> > like he won't have time. I don't think I'm proficient enough in
>>>Hive
>>> >> > Server 2 to make the example, so I've unassigned OOZIE-1963 from
>>>me.
>>> >> > Though I think it would still be good to include.
>>> >> >
>>> >> > If we include the Spark action, I think we should also include
>>> >> OOZIE-2170.
>>> >> > OOZIE-2174 would also be good; it addresses some long-standing
>>> >> shortcomings
>>> >> > of OozieClient/OozieCLI.
>>> >> > Finally, we should also include OOZIE-2181, which fixes some
>>>problems
>>> >> > retrieving job info.
>>> >> > I have patches available for all 3 of these.
>>> >> >
>>> >> >
>>> >> > - Robert
>>> >> >
>>> >> > On Wed, Mar 25, 2015 at 10:58 AM, Shwetha Shivalingamurthy <
>>> >> > sshivalingamurthy@hortonworks.com> wrote:
>>> >> >
>>> >> > > Robert, will you be able to take up OOZIE-1963?
>>> >> > >
>>> >> > > Dev team, Are there any other un-resolved jiras that needs to be
>>> >>part
>>> >> of
>>> >> > > 4.2 release?
>>> >> > >
>>> >> > > Thanks,
>>> >> > > Shwetha
>>> >> > >
>>> >> > >
>>> >> > > On 11/02/15 1:44 pm, "Robert Kanter" <rk...@cloudera.com>
>>>wrote:
>>> >> > >
>>> >> > > >I 4.2.0 release sounds good; I don't have cycles to drive it
>>> >>though.
>>> >> > > >
>>> >> > > >The Spark action currently has a number of problems with it.
>>>I'd
>>> >>hold
>>> >> > off
>>> >> > > >on putting that into a release until we get those fixed
>>>(OOZIE-2071
>>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2071> (it's to add
>>>an
>>> >> > > >example,
>>> >> > > >but the comments discuss the problems), OOZIE-2087
>>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2087>).
>>> >> > > >
>>> >> > > >I'm all for including the Hive2 action; though it would be good
>>>if
>>> >>we
>>> >> > > >could
>>> >> > > >create an example workflow for it for completeness (OOZIE-1963
>>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-1963>). I can
>>> >>probably
>>> >> > take
>>> >> > > >care of this relatively easily.
>>> >> > > >
>>> >> > > >
>>> >> > > >- Robert
>>> >> > > >
>>> >> > > >On Tue, Feb 10, 2015 at 9:56 PM, Shwetha Shivalingamurthy <
>>> >> > > >sshivalingamurthy@hortonworks.com> wrote:
>>> >> > > >
>>> >> > > >> Hi All,
>>> >> > > >>
>>> >> > > >> Oozie trunk has a couple of changes since the last oozie
>>>release
>>> >>-
>>> >> > > >>re-run
>>> >> > > >> fixes, config cleanup, spark action, hive2 action, external
>>> >> > > >>configuration
>>> >> > > >> for mapred action, better error reporting and many other bug
>>> >>fixes.
>>> >> > > >>
>>> >> > > >> Can we have a oozie release from trunk? If someone wants to
>>> >> volunteer
>>> >> > to
>>> >> > > >> drive the release, please take this forward. Else, I can
>>>drive
>>> >>it as
>>> >> > > >>well.
>>> >> > > >>
>>> >> > > >> If we want to do a release, let's identify the pending jiras
>>> >>which
>>> >> are
>>> >> > > >> required for this release.
>>> >> > > >>
>>> >> > > >> Thanks,
>>> >> > > >> Shwetha
>>> >> > > >>
>>> >> > >
>>> >> > >
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Harsh J
>>> >>
>>>
>>>
>>
>>
>>
>
Re: [DISCUSSION] Oozie 4.2.0 release
Posted by Shwetha Shivalingamurthy <ss...@hortonworks.com>.
Ryota, is this the only issue from regression?
Dev team, does anyone want to take up OOZIE-1993?
Regards,
Shwetha
On 10/04/15 12:38 am, "Ryota Egashira" <eg...@yahoo-inc.com.INVALID>
wrote:
>OOZIE-1993 need to be fixed before release.workflow rerun failed with
>oozie.wf.rerun.failnodes=true in some cases. actually because of this, we
>reverted OOZIE-1879 for our internal branch.
>
>ThanksRyota
>
>
>
> On Thursday, March 26, 2015 4:57 PM, Robert Kanter
><rk...@cloudera.com> wrote:
>
>
> Another JIRA that would be good to get is OOZIE-2186 which updates the
>Tomcat version.
>
>On Thu, Mar 26, 2015 at 2:46 PM, Shwetha Shivalingamurthy <
>sshivalingamurthy@hortonworks.com> wrote:
>
>> Ok, I will wait for them. Thanks
>>
>>
>> On 26/03/15 2:21 pm, "Rohini Palaniswamy" <ro...@gmail.com>
>>wrote:
>>
>> >We don't have a list of issues that need to be included. But Michelle
>>ran
>> >the regression with trunk yesterday and there were couple of failures.
>>We
>> >haven't investigated them yet. Those will have to be fixed though.
>>Ryota
>> >will file jiras and upload fixes next week after investigating them.
>> >
>> >Regards,
>> >Rohini
>> >
>> >On Thu, Mar 26, 2015 at 1:58 PM, Harsh J <ha...@cloudera.com> wrote:
>> >
>> >> I can take over OOZIE-1963. I need to test the modified hive(1)
>>example
>> >>and
>> >> will then attach the change to the JIRA.
>> >>
>> >> On Thu, Mar 26, 2015 at 6:20 AM, Robert Kanter <rk...@cloudera.com>
>> >> wrote:
>> >>
>> >> > I was hoping one of our QA engineers would take care of that, but
>>it
>> >> looks
>> >> > like he won't have time. I don't think I'm proficient enough in
>>Hive
>> >> > Server 2 to make the example, so I've unassigned OOZIE-1963 from
>>me.
>> >> > Though I think it would still be good to include.
>> >> >
>> >> > If we include the Spark action, I think we should also include
>> >> OOZIE-2170.
>> >> > OOZIE-2174 would also be good; it addresses some long-standing
>> >> shortcomings
>> >> > of OozieClient/OozieCLI.
>> >> > Finally, we should also include OOZIE-2181, which fixes some
>>problems
>> >> > retrieving job info.
>> >> > I have patches available for all 3 of these.
>> >> >
>> >> >
>> >> > - Robert
>> >> >
>> >> > On Wed, Mar 25, 2015 at 10:58 AM, Shwetha Shivalingamurthy <
>> >> > sshivalingamurthy@hortonworks.com> wrote:
>> >> >
>> >> > > Robert, will you be able to take up OOZIE-1963?
>> >> > >
>> >> > > Dev team, Are there any other un-resolved jiras that needs to be
>> >>part
>> >> of
>> >> > > 4.2 release?
>> >> > >
>> >> > > Thanks,
>> >> > > Shwetha
>> >> > >
>> >> > >
>> >> > > On 11/02/15 1:44 pm, "Robert Kanter" <rk...@cloudera.com>
>>wrote:
>> >> > >
>> >> > > >I 4.2.0 release sounds good; I don't have cycles to drive it
>> >>though.
>> >> > > >
>> >> > > >The Spark action currently has a number of problems with it.
>>I'd
>> >>hold
>> >> > off
>> >> > > >on putting that into a release until we get those fixed
>>(OOZIE-2071
>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2071> (it's to add
>>an
>> >> > > >example,
>> >> > > >but the comments discuss the problems), OOZIE-2087
>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-2087>).
>> >> > > >
>> >> > > >I'm all for including the Hive2 action; though it would be good
>>if
>> >>we
>> >> > > >could
>> >> > > >create an example workflow for it for completeness (OOZIE-1963
>> >> > > ><https://issues.apache.org/jira/browse/OOZIE-1963>). I can
>> >>probably
>> >> > take
>> >> > > >care of this relatively easily.
>> >> > > >
>> >> > > >
>> >> > > >- Robert
>> >> > > >
>> >> > > >On Tue, Feb 10, 2015 at 9:56 PM, Shwetha Shivalingamurthy <
>> >> > > >sshivalingamurthy@hortonworks.com> wrote:
>> >> > > >
>> >> > > >> Hi All,
>> >> > > >>
>> >> > > >> Oozie trunk has a couple of changes since the last oozie
>>release
>> >>-
>> >> > > >>re-run
>> >> > > >> fixes, config cleanup, spark action, hive2 action, external
>> >> > > >>configuration
>> >> > > >> for mapred action, better error reporting and many other bug
>> >>fixes.
>> >> > > >>
>> >> > > >> Can we have a oozie release from trunk? If someone wants to
>> >> volunteer
>> >> > to
>> >> > > >> drive the release, please take this forward. Else, I can drive
>> >>it as
>> >> > > >>well.
>> >> > > >>
>> >> > > >> If we want to do a release, let's identify the pending jiras
>> >>which
>> >> are
>> >> > > >> required for this release.
>> >> > > >>
>> >> > > >> Thanks,
>> >> > > >> Shwetha
>> >> > > >>
>> >> > >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Harsh J
>> >>
>>
>>
>
>
>