[
https://issues.apache.org/jira/browse/OOZIE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250837#comment-15250837
]
Robert Kanter commented on OOZIE-2330:
--------------------------------------
[~satishsaley], thanks for fixing that. While we're at it, I think we should
also fix another spark schema problem I noticed where the {{<file>}} and
{{<archive>}} fields that most actions have are missing from the Spark Action.
{code:xml}
<xs:element name="file" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="archive" type="xs:string" minOccurs="0"
maxOccurs="unbounded"/>
{code}
I don't think any code changes are required for this because the
{{JavaActionExecutor}} probably handles this, but it would be good to verify
that.
I also wonder if we should do both of these changes in a new spark-action-0.2
given that 0.1 has already been available.
> Spark action should take the global jobTracker and nameNode configs by default
> ------------------------------------------------------------------------------
>
> Key: OOZIE-2330
> URL: https://issues.apache.org/jira/browse/OOZIE-2330
> Project: Oozie
> Issue Type: Improvement
> Components: action
> Reporter: Wei Yan
> Assignee: Satish Subhashrao Saley
> Priority: Minor
> Attachments: OOZIE-2330-1.patch
>
>
> In Spark Action 0.1 schema, the job-tracker and name-node are required.
> {code}
> <xs:element name="job-tracker" type="xs:string" minOccurs="1" maxOccurs="1"/>
> <xs:element name="name-node" type="xs:string" minOccurs="1" maxOccurs="1"/>
> {code}
> It would be better that the spark action can take default values from the
> global configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
