Hi Yong,
The usage of local filesystems are strictly prohibited in Oozie 5.0.
I'd guess you have a hdfs://seomnode as fs.defaultFS and you're providing
the S3 credentials for the job only.
I'll try to carve out some time to reproduce and fix this, but I can't
promise you anything soon due to other
Hi Yong
Have you also tried s3a in place of s3?
-
Suresh.
> On Mar 25, 2019, at 2:03 PM, Peter Cseh wrote:
>
> Hey Yong,
>
> Thanks for reporting this issue!
> If I see correctly, your Oozie is set up to talk to a HDFS instance and to
> S3 as well. This is not a scenario I'm too familiar w
share lib, another one
configured in oozie to be used as application base dir.
Yong
From: Peter Cseh
Sent: Monday, March 25, 2019 3:03 PM
To: user@oozie.apache.org
Subject: Re: oozie 5.0.0 on AWS EMR
Hey Yong,
Thanks for reporting this issue!
If I see correctly
Hey Yong,
Thanks for reporting this issue!
If I see correctly, your Oozie is set up to talk to a HDFS instance and to
S3 as well. This is not a scenario I'm too familiar with.
Could you give us some easy-to-follow steps to reproduce this?
Thanks
gp
On Thu, Mar 21, 2019 at 11:13 PM Daniel Zhang w
