[
https://issues.apache.org/jira/browse/OOZIE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900610#comment-13900610
]
Kevin Risden commented on OOZIE-426:
------------------------------------
{quote}
Thoughts on this as a universal deployment strategy for any HCFS.... Is it
viable ? Sure would make things easier for the oozie community if "yes" (that
we we dont have to do funny stuff like redeploy the war file at runtime).
{quote}
The issue that I see is that if Oozie is upgraded and the Oozie war is
redeployed you lose any jars you added to WEB-INF/lib. I don't think that it is
a terrible workflow to have to add the jars back after an upgrade it just has
to be documented.
> 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)
