You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Shwetha G S (JIRA)" <ji...@apache.org> on 2015/05/18 09:12:15 UTC
[jira] [Updated] (OOZIE-2107) Schema config properties should be
consistent with ActionExecutor config properties
[ https://issues.apache.org/jira/browse/OOZIE-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shwetha G S updated OOZIE-2107:
-------------------------------
Fix Version/s: (was: trunk)
4.2
> 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: 4.2
>
> Attachments: OOZIE-2107.patch, 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)