[
https://issues.apache.org/jira/browse/OOZIE-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288160#comment-14288160
]
Purshotam Shah commented on OOZIE-2107:
---------------------------------------
Ok.
+1 after minor change in oozie-default.xml
{quote}
+ <property>
+ <name>oozie.service.SchemaService.bundle.schemas</name>
+ <value>
+ oozie-bundle-0.1.xsd,oozie-bundle-0.2.xsd
+ </value>
+ <description>
+ List of schemas for coordinators (separated by commas).
</description>
</property>
{quote}
Change the description to bundle
{quote}
<property>
- <name>oozie.service.SchemaService.sla.ext.schemas</name>
+ <name>oozie.service.SchemaService.bundle.ext.schemas</name>
<value> </value>
<description>
- Schemas for semantic validation for GMS SLA.
+ List of additional schemas for coordinators (separated by commas).
+ </description>
+ </property>
{quote}
Change the description to bundles
> 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)
