Robert Kanter created OOZIE-2107:
------------------------------------
Summary: 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
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)
