[OOZIE-1695] Generic HCFS supported integration path

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: jay vyas
• Created: 13/Feb/14 23:39
• Updated: 09/Mar/15 19:32

Description

The dizzying OOZIE-426 JIRA indicates that at the moment it is not clear wether oozie does, or doesn't, support any HCFS file system.

• the good news is, after some digging : It does !

So we have two tasks, mostly documentation i guess, but possibly some modifications in code/comments would be nice as well to clarify things further for developers:

• So now we need to all agree on and document the "right" way to add file system plugins into Oozie. Hopefully we can do so using semantics which is not dependant on HDFS/S3 to avoid confusion.

• In addition, Some clarity on why and how the "nameNode" parameter is enforced as part of the XML schema for java tasks should also be clarified. Clearly that is a bug since oozie supports non-HDFS deployments.

Specifically, it appears that in the http://oozie.apache.org/docs/3.2.0-incubating/WorkflowFunctionalSpec.html "The java action has to be configured with the job-tracker, name-node, main Java class, JVM options and arguments.".....

Issue Links

• relates to: OOZIE-477 Adding configurable filesystem support instead of hardcoded "hdfs"
• relates to: OOZIE-426 OOZIE-9: Support (Amazon) s3/s3n schemes