[
https://issues.apache.org/jira/browse/OOZIE-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270684#comment-14270684
]
Shwetha G S commented on OOZIE-2107:
------------------------------------
All action types part of oozie codebase should be enabled by
default(oozie.service.SchemaService.wf.schemas), custom user defined action
types(outside oozie codebase) can be added using
oozie.service.SchemaService.wf.ext.schemas(I thought thats what ext configs are
used for). If we want a feature to disable some default action types, why not
expose another config(which is empty by default and can be overridden)? This is
not backward compatible, but would this work?
> 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)
