[
https://issues.apache.org/jira/browse/OOZIE-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617731#comment-13617731
]
Robert Kanter commented on OOZIE-1284:
--------------------------------------
I'm not sure if I was just doing something stupid, but if you try to format it
like this (which we do for similar properties):
{code:xml}
<value>
shell-action-0.1.xsd,
shell-action-0.2.xsd,
email-action-0.1.xsd,
hive-action-0.2.xsd,
...
</value>
{code}
instead of like this (which is too long):
{code:xml}
<value>shell-action-0.1.xsd,shell-action-0.2.xsd,email-action-0.1.xsd,hive-action-0.2.xsd,...</value>
{code}
then Oozie will fail to startup!
> oozie.service.SchemaService.wf.ext.schemas in oozie-site is missing some
> newer xsd files
> ----------------------------------------------------------------------------------------
>
> Key: OOZIE-1284
> URL: https://issues.apache.org/jira/browse/OOZIE-1284
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: trunk
> Reporter: Robert Kanter
> Fix For: trunk
>
>
> In oozie-site.xml, we have the following listed under
> {{oozie.service.SchemaService.wf.ext.schemas}}:
> {noformat}
> shell-action-0.1.xsd
> shell-action-0.2.xsd
> email-action-0.1.xsd
> hive-action-0.2.xsd
> hive-action-0.3.xsd
> sqoop-action-0.2.xsd
> sqoop-action-0.3.xsd
> ssh-action-0.1.xsd
> distcp-action-0.1.xsd
> {noformat}
> It's missing the following xsd files:
> {noformat}
> distcp-action-0.2.xsd
> hive-action-0.4.xsd
> shell-action-0.3.xsd
> sqoop-action-0.4.xsd
> {noformat}
> If I recall correctly, this will cause Oozie to reject workflows using those
> versions of those extension action schemas.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
