[
https://issues.apache.org/jira/browse/OOZIE-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15591429#comment-15591429
]
Andras Piros commented on OOZIE-2715:
-------------------------------------
[~Bearricade] do you want a generic solution that handles any property key /
value pairs on a per action type basis?
If you only need to suppress the retry count based on the action types, you
could use inside {{workflow.xml}} the attribute {{retry-max}} of the
{{application}} element like that:
{code:xml}
<xs:complexType name="ACTION">
...
<xs:attribute name="retry-max" type="xs:string"/>
...
</xs:complexType>
{code}
> Provide possibility to set default values for properties of a particular
> action type
> ------------------------------------------------------------------------------------
>
> Key: OOZIE-2715
> URL: https://issues.apache.org/jira/browse/OOZIE-2715
> Project: Oozie
> Issue Type: Wish
> Components: action
> Affects Versions: 4.2.0
> Reporter: Istvan Vajnorak
>
> When it comes to retrying an action, one can set the default values for a
> retry on the global level, and the override can happen then on the individual
> step's level only.
> The proposal to be able to set retry and other properties on an action type
> basis, could allow defaulting things and help not to do repetitive work on
> each action instance in the workflow.
> Example:
> - One has 60 shell actions and 30 java actions in a workflow.
> - One sets " oozie.launcher.yarn.resourcemanager.am.max-attempts=1" globally
> - For shell steps they don't want this to get applied, so they have to
> suppress the retry on those steps each time
> The proposal would allow an intermediate level of override similarly like the
> hadoop conf allows with the *-default.xml, *-site.xml and code level
> properties override.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
