You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Mona Chitnis (Created) (JIRA)" <ji...@apache.org> on 2012/04/13 04:31:16 UTC
[jira] [Created] (OOZIE-813) Sub-workflow child job does not get
group name even if parent carries it
Sub-workflow child job does not get group name even if parent carries it
------------------------------------------------------------------------
Key: OOZIE-813
URL: https://issues.apache.org/jira/browse/OOZIE-813
Project: Oozie
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Mona Chitnis
Assignee: Mona Chitnis
Fix For: 3.2.0
Subworkflow AE needs to account for assigning group/acl name to child wf if parent has it. <propagate-configuration> should not be needed for something as basic as group/acl name.
Example output:
sub workflow child workflow job does not have the group name.
$ oozie jobs -len 2
Job ID App Name Status User Group Started Ended
-----------------------------------------------------------------------------------------------------------
0002-oozie-oozi-W child-wf KILLED joe - 2012-03-30 21:28 2012-03-30 21:31
-----------------------------------------------------------------------------------------------------------
0001-oozie-oozi-W parent-wf KILLED joe users 2012-03-30 21:28 2012-03-30 21:31
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OOZIE-813) Sub-workflow child job does not get
group name even if parent carries it
Posted by "Mona Chitnis (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mona Chitnis resolved OOZIE-813.
--------------------------------
Resolution: Fixed
> Sub-workflow child job does not get group name even if parent carries it
> ------------------------------------------------------------------------
>
> Key: OOZIE-813
> URL: https://issues.apache.org/jira/browse/OOZIE-813
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.2.0
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Labels: oozie
> Fix For: 3.2.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Subworkflow AE needs to account for assigning group/acl name to child wf if parent has it. <propagate-configuration> should not be needed for something as basic as group/acl name.
> Example output:
> sub workflow child workflow job does not have the group name.
> $ oozie jobs -len 2
> Job ID App Name Status User Group Started Ended
> -----------------------------------------------------------------------------------------------------------
> 0002-oozie-oozi-W child-wf KILLED joe - 2012-03-30 21:28 2012-03-30 21:31
> -----------------------------------------------------------------------------------------------------------
> 0001-oozie-oozi-W parent-wf KILLED joe users 2012-03-30 21:28 2012-03-30 21:31
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-813) Sub-workflow child job does not get
group name even if parent carries it
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253965#comment-13253965 ]
jiraposter@reviews.apache.org commented on OOZIE-813:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4715/
-----------------------------------------------------------
Review request for oozie.
Summary
-------
Subworkflow AE needs to account for assigning group/acl name to child wf if parent has it. <propagate-configuration> should not be needed for something as basic as group/acl name.
Example output:
sub workflow child workflow job does not have the group name.
$ oozie jobs -len 2
Job ID App Name Status User Group Started Ended
-----------------------------------------------------------------------------------------------------------
0002-oozie-oozi-W child-wf KILLED joe - 2012-03-30 21:28 2012-03-30 21:31
-----------------------------------------------------------------------------------------------------------
0001-oozie-oozi-W parent-wf KILLED joe users 2012-03-30 21:28 2012-03-30 21:31
This addresses bug OOZIE-813.
https://issues.apache.org/jira/browse/OOZIE-813
Diffs
-----
trunk/core/src/main/java/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.java 1325599
trunk/core/src/test/java/org/apache/oozie/action/oozie/TestSubWorkflowActionExecutor.java 1325599
Diff: https://reviews.apache.org/r/4715/diff
Testing
-------
yes. unit test for both negative and positive cases
Thanks,
Mona
> Sub-workflow child job does not get group name even if parent carries it
> ------------------------------------------------------------------------
>
> Key: OOZIE-813
> URL: https://issues.apache.org/jira/browse/OOZIE-813
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.2.0
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Labels: oozie
> Fix For: 3.2.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Subworkflow AE needs to account for assigning group/acl name to child wf if parent has it. <propagate-configuration> should not be needed for something as basic as group/acl name.
> Example output:
> sub workflow child workflow job does not have the group name.
> $ oozie jobs -len 2
> Job ID App Name Status User Group Started Ended
> -----------------------------------------------------------------------------------------------------------
> 0002-oozie-oozi-W child-wf KILLED joe - 2012-03-30 21:28 2012-03-30 21:31
> -----------------------------------------------------------------------------------------------------------
> 0001-oozie-oozi-W parent-wf KILLED joe users 2012-03-30 21:28 2012-03-30 21:31
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-813) Sub-workflow child job does not get
group name even if parent carries it
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255150#comment-13255150 ]
jiraposter@reviews.apache.org commented on OOZIE-813:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4715/#review6962
-----------------------------------------------------------
Ship it!
+1 committing
- Mohammad
On 2012-04-14 03:17:18, Mona Chitnis wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/4715/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2012-04-14 03:17:18)
bq.
bq.
bq. Review request for oozie.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Subworkflow AE needs to account for assigning group/acl name to child wf if parent has it. <propagate-configuration> should not be needed for something as basic as group/acl name.
bq.
bq. Example output:
bq.
bq. sub workflow child workflow job does not have the group name.
bq.
bq. $ oozie jobs -len 2
bq. Job ID App Name Status User Group Started Ended
bq. -----------------------------------------------------------------------------------------------------------
bq. 0002-oozie-oozi-W child-wf KILLED joe - 2012-03-30 21:28 2012-03-30 21:31
bq. -----------------------------------------------------------------------------------------------------------
bq. 0001-oozie-oozi-W parent-wf KILLED joe users 2012-03-30 21:28 2012-03-30 21:31
bq.
bq.
bq. This addresses bug OOZIE-813.
bq. https://issues.apache.org/jira/browse/OOZIE-813
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. trunk/core/src/main/java/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.java 1325599
bq. trunk/core/src/test/java/org/apache/oozie/action/oozie/TestSubWorkflowActionExecutor.java 1325599
bq.
bq. Diff: https://reviews.apache.org/r/4715/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. yes. unit test for both negative and positive cases
bq.
bq.
bq. Thanks,
bq.
bq. Mona
bq.
bq.
> Sub-workflow child job does not get group name even if parent carries it
> ------------------------------------------------------------------------
>
> Key: OOZIE-813
> URL: https://issues.apache.org/jira/browse/OOZIE-813
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.2.0
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Labels: oozie
> Fix For: 3.2.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Subworkflow AE needs to account for assigning group/acl name to child wf if parent has it. <propagate-configuration> should not be needed for something as basic as group/acl name.
> Example output:
> sub workflow child workflow job does not have the group name.
> $ oozie jobs -len 2
> Job ID App Name Status User Group Started Ended
> -----------------------------------------------------------------------------------------------------------
> 0002-oozie-oozi-W child-wf KILLED joe - 2012-03-30 21:28 2012-03-30 21:31
> -----------------------------------------------------------------------------------------------------------
> 0001-oozie-oozi-W parent-wf KILLED joe users 2012-03-30 21:28 2012-03-30 21:31
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-813) Sub-workflow child job does not get
group name even if parent carries it
Posted by "Mona Chitnis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mona Chitnis updated OOZIE-813:
-------------------------------
For the patch committed in trunk with this JIRA ID (also available under the same JIRA ID in Apache ReviewBoard system), I grant license to ASF for inclusion in ASF works (as per the Apache License §5)
> Sub-workflow child job does not get group name even if parent carries it
> ------------------------------------------------------------------------
>
> Key: OOZIE-813
> URL: https://issues.apache.org/jira/browse/OOZIE-813
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.2.0
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Labels: oozie
> Fix For: 3.2.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Subworkflow AE needs to account for assigning group/acl name to child wf if parent has it. <propagate-configuration> should not be needed for something as basic as group/acl name.
> Example output:
> sub workflow child workflow job does not have the group name.
> $ oozie jobs -len 2
> Job ID App Name Status User Group Started Ended
> -----------------------------------------------------------------------------------------------------------
> 0002-oozie-oozi-W child-wf KILLED joe - 2012-03-30 21:28 2012-03-30 21:31
> -----------------------------------------------------------------------------------------------------------
> 0001-oozie-oozi-W parent-wf KILLED joe users 2012-03-30 21:28 2012-03-30 21:31
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira