[
https://issues.apache.org/jira/browse/OOZIE-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241473#comment-13241473
]
[email protected] commented on OOZIE-792:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4554/#review6527
-----------------------------------------------------------
Ship it!
+1
- Angelo K.
On 2012-03-29 12:45:11, Alejandro Abdelnur wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/4554/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2012-03-29 12:45:11)
bq.
bq.
bq. Review request for oozie.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Similar to hadoop configs per cluster, Oozie should support default action
configurations per cluster.
bq.
bq. This default config per action per cluster mechanism would act as defaults
for the action configuration section enabling things like:
bq.
bq. * defining a special queue for launcher jobs
bq. * setting properties required to tune pig/hive etc
bq.
bq. It should load/work in identical way as the hadoop configurations but
instead using just a 'host:name' key it would use a composed key 'host:name +
action-type'
bq.
bq. If the ACTION.xml file does not exist, then there are not defaults values.
bq.
bq. The default value for the action.configurations is identical to the
hadoop.configurations: *=hadoop-conf. It is a different property to allow
pointing to the HADOOP conf/ dir for hadoop configurations and to an Oozie dir
for action configurations (not to pollute Hadoop confs)
bq.
bq.
bq. This addresses bug OOZIE-792.
bq. https://issues.apache.org/jira/browse/OOZIE-792
bq.
bq.
bq. Diffs
bq. -----
bq.
bq.
trunk/core/src/test/java/org/apache/oozie/action/hadoop/TestDistCpActionExecutor.java
1306811
bq.
trunk/core/src/test/java/org/apache/oozie/action/email/TestEmailActionExecutor.java
1306811
bq.
trunk/core/src/test/java/org/apache/oozie/action/hadoop/ActionExecutorTestCase.java
1306811
bq. trunk/core/src/main/resources/oozie-default.xml 1306811
bq.
trunk/core/src/main/java/org/apache/oozie/service/HadoopAccessorService.java
1306811
bq.
trunk/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
1306811
bq.
trunk/core/src/test/java/org/apache/oozie/action/hadoop/TestFsActionExecutor.java
1306811
bq.
trunk/core/src/test/java/org/apache/oozie/action/hadoop/TestHiveActionExecutor.java
1306811
bq.
trunk/core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java
1306811
bq.
trunk/core/src/test/java/org/apache/oozie/action/hadoop/TestMapReduceActionError.java
1306811
bq.
trunk/core/src/test/java/org/apache/oozie/action/hadoop/TestMapReduceActionExecutor.java
1306811
bq.
trunk/core/src/test/java/org/apache/oozie/action/hadoop/TestPigActionExecutor.java
1306811
bq.
trunk/core/src/test/java/org/apache/oozie/action/hadoop/TestShellActionExecutor.java
1306811
bq.
trunk/core/src/test/java/org/apache/oozie/action/hadoop/TestSqoopActionExecutor.java
1306811
bq.
trunk/core/src/test/java/org/apache/oozie/service/TestHadoopAccessorService.java
1306811
bq. trunk/core/src/test/resources/test-action-config.xml PRE-CREATION
bq.
bq. Diff: https://reviews.apache.org/r/4554/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. * Run all testcases successfully with Hadoop 1 and Hadoop 0.23
bq.
bq. * Deployed Oozie, run examples, added actions configs values, and verified
the actions gets the values.
bq.
bq.
bq. Thanks,
bq.
bq. Alejandro
bq.
bq.
> add default action configs per cluster
> --------------------------------------
>
> Key: OOZIE-792
> URL: https://issues.apache.org/jira/browse/OOZIE-792
> Project: Oozie
> Issue Type: New Feature
> Components: workflow
> Affects Versions: 3.2.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Priority: Critical
> Fix For: 3.2.0
>
>
> Similar to hadoop configs per cluster, Oozie should support default action
> configurations per cluster.
> This default config per action per cluster mechanism would act as defaults
> for the action configuration section enabling things like:
> * defining a special queue for launcher jobs
> * setting properties required to tune pig/hive etc
> It should load/work in identical way as the hadoop configurations but instead
> using just a 'host:name' key it would use a composed key 'host:name +
> action-type'
--
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
