[
https://issues.apache.org/jira/browse/OOZIE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900770#comment-13900770
]
Robert Kanter commented on OOZIE-426:
-------------------------------------
{quote}
Would it make sense to make the hadooplibs pom include jets3t to specifically
support S3/S3N since that is what this JIRA is about?
{quote}
Yes. This is what I was trying to say before, but I might have been unclear.
{quote}
We can then open another JIRA to decide the best way to include jars for other
filesystems which may just be to use /var/lib/oozie in certain cases and
oozie-setup.sh prepare-war in other cases.
{quote}
I agree that this is a different topic, but I'm not sure how we're going to do
something like this with the tarball installation. Bigtop/CDH's use of
/var/lib/oozie works by doing some "magic" with exploded WAR files, which may
be tricky in a tarball. But let's move that discussion to another JIRA.
> 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)
