[
https://issues.apache.org/jira/browse/OOZIE-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275790#comment-14275790
]
Robert Kanter commented on OOZIE-2107:
--------------------------------------
[~puru], I think it makes sense that all bundled actions should be enabled by
default. Currently, if someone wants to disable a schema, they have to
override {{oozie.service.SchemaService.wf.ext.schemas}} with all of the schemas
they do want. Unless we add a "negative" version of this property for removing
schemas, you'll still have to override something to remove schemas; but I'm not
sure we want to do that. Having 3 configs for one thing seems unnecessarily
complicated. With the patch, we can at least (a) make it easy for users to add
schemas and (b) make it consistent with other properties like
{{oozie.service.ActionService.executor.classes}} and the Services property,
which is easier for the user.
The backwards compatibility that would be broken is that users removing schemas
would have to rename {{oozie.service.SchemaService.wf.ext.schemas}} to
{{oozie.service.SchemaService.wf.schemas}}. We could note this as an
"Incompatible Change"; Hadoop allows for this sort of thing as long as it's
documented.
> Schema config properties should be consistent with ActionExecutor config
> properties
> -----------------------------------------------------------------------------------
>
> Key: OOZIE-2107
> URL: https://issues.apache.org/jira/browse/OOZIE-2107
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: trunk
>
> Attachments: OOZIE-2107.patch
>
>
> For specifying ActionExecutors, we have
> {{oozie.service.ActionService.executor.classes}} and
> {{oozie.service.ActionService.executor.ext.classes}}. The former specifies
> the default ones, and the latter allows adding/overriding them.
> For specifying the corresponding action schemas, we have just:
> {{oozie.service.SchemaService.wf.ext.schemas}}. This makes it difficult for
> users to add/override schemas. We should add a
> {{oozie.service.SchemaService.wf.schemas}} with the default schemas, where
> the "ext" config would add/override. This should be backwards compatible
> because both properties get loaded. We can also remove the workflow schemas
> from being hardcoded in the SchemaService class.
> Similarly, we should do the same for the coordinators, bundles, and sla
> schema properties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
