[
https://issues.apache.org/jira/browse/OOZIE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899714#comment-13899714
]
Robert Kanter commented on OOZIE-426:
-------------------------------------
I think this is the best approach. Yes, we'd have to update the pom to add
other filesystems later (if they're in a new jar not included automatically),
but its not like Hadoop is adding new {{FileSystem}} implementations everyday.
In the tarball installation used by Apache Oozie, I don't think there's a
convenient way to add jars after its been deployed. You have to put them in
the libext dir and run oozie-setup.sh. In CDH, you can simply drop the jar in
/var/lib/oozie and restart Oozie (e.g. you can put the mysql jar here); I don't
know about HDP, but it may have something similar.
> OOZIE-9: Support (Amazon) s3/s3n schemes
> ----------------------------------------
>
> Key: OOZIE-426
> URL: https://issues.apache.org/jira/browse/OOZIE-426
> Project: Oozie
> Issue Type: New Feature
> Reporter: Hadoop QA
> Assignee: Roman Shaposhnik
>
> Currently Oozie supports only the 'hdfs' scheme. For people having their
> hadoop cluster in Amazon EC2 and using S3 for storage, it would be very
> useful if oozie supports the 's3n/s3' scheme(s). The use case I am talking
> about is as follows
> Hadoop cluster in Amazon EC2
> Uses hdfs for intermediate storage
> Uses s3 for getting input for, storing output of map-reduce jobs.
> More details on the above use-case and the exceptions/failures I have seen is
> documented here (http://tech.groups.yahoo.com/group/Oozie-users/message/1138).
> There can be other use cases as well - say use s3 as the DFS instead of HDFS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
