I think there is something missing which has been not covered properly in the example....My job is finishing successfully & not showing error on Oozie Web UI...but no changes are occuring in HDFS ..I checked my Oozie logs which are showing error messages as follows : 2016-06-09 07:29:58,168 INFO BundleSubmitXCommand:520 - SERVER[ip-172-31-3-226.ec2.internal] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] configDefault Doesn't exist hdfs://52.91.246.198:80 2016-06-09 07:29:58,218 WARN BundleStartXCommand:523 - SERVER[ip-172-31-3-226.ec2.internal] USER[ambari-qa] GROUP[-] TOKEN[] APP[FALCON_FEED_rawEmailFeed] JOB[0000026-160609052025426-oozie-oozi-B] ACTION[-] E1100: Command precondition does not hold before execution, [Bundle 0000026-160609052025426-oozie-oozi-B is not in PREP status. It is in : RUNNING], Error Code: E1100 2016-06-09 07:29:58,230 INFO CoordSubmitXCommand:520 - SERVER[ip-172-31-3-226.ec2.internal] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0000026-160609052025426-oozie-oozi-B] ACTION[] configDefault Doesn't exist hdfs://52.91.246.198:8020/apps/falcon/primaryCluster/staging/falcon/workflows/feed/rawEmailFeed/b31810f3199e7b861dce158ca674de17_1465457397722/RETENTION/coord-config-default.xml 2016-06-09 07:30:02,690 WARN JobResourceUploader:64 - SERVER[ip-172-31-3-226.ec2.internal] Hadoop command-line option parsing not performed. Implement the Tool interface and execute your application with ToolRunner to remedy this. 2016-06-09 07:30:03,226 WARN MRApps:610 - SERVER[ip-172-31-3-226.ec2.internal] cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/hcatalog/aws-java-sdk-1.7.4.jar conflicts with cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/oozie/aws-java-sdk-1.7.4.jar This will be an error in Hadoop 2.0 2016-06-09 07:30:03,226 WARN MRApps:610 - SERVER[ip-172-31-3-226.ec2.internal] cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/hcatalog/azure-storage-2.2.0.jar conflicts with cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/oozie/azure-storage-2.2.0.jar This will be an error in Hadoop 2.0 2016-06-09 07:30:03,227 WARN MRApps:610 - SERVER[ip-172-31-3-226.ec2.internal] cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/hcatalog/commons-lang3-3.3.2.jar conflicts with cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/oozie/commons-lang3-3.3.2.jar This will be an error in Hadoop 2.0 2016-06-09 07:30:03,227 WARN MRApps:610 - SERVER[ip-172-31-3-226.ec2.internal] cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/hcatalog/guava-11.0.2.jar conflicts with cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/oozie/guava-11.0.2.jar This will be an error in Hadoop 2.0 2016-06-09 07:30:03,227 WARN MRApps:610 - SERVER[ip-172-31-3-226.ec2.internal] cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/hcatalog/hadoop-aws-2.7.1.2.3.4.7-4.jar conflicts with cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/oozie/hadoop-aws-2.7.1.2.3.4.7-4.jar This will be an error in Hadoop 2.0 2016-06-09 07:30:03,228 WARN MRApps:610 - SERVER[ip-172-31-3-226.ec2.internal] cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/hcatalog/hadoop-azure-2.7.1.2.3.4.7-4.jar conflicts with cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/oozie/hadoop-azure-2.7.1.2.3.4.7-4.jar This will be an error in Hadoop 2.0 2016-06-09 07:30:03,228 WARN MRApps:610 - SERVER[ip-172-31-3-226.ec2.internal] cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/hcatalog/jackson-annotations-2.2.3.jar conflicts with cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/oozie/jackson-annotations-2.2.3.jar This will be an error in Hadoop 2.0 2016-06-09 07:30:03,229 WARN MRApps:610 - SERVER[ip-172-31-3-226.ec2.internal] cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/hcatalog/jackson-core-2.2.3.jar conflicts with cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/oozie/jackson-core-2.2.3.jar This will be an error in Hadoop 2.0 2016-06-09 07:30:03,229 WARN MRApps:610 - SERVER[ip-172-31-3-226.ec2.internal] cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/hcatalog/jackson-databind-2.2.3.jar conflicts with cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/oozie/jackson-databind-2.2.3.jar This will be an error in Hadoop 2.0 2016-06-09 07:30:03,230 WARN MRApps:610 - SERVER[ip-172-31-3-226.ec2.internal] cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/hcatalog/joda-time-2.1.jar conflicts with cache file (mapreduce.job.cache.files) hdfs://ip-172-31-3-226.ec2.internal:8020/user/oozie/share/lib/lib_20160609051953/oozie/joda-time-2.1.jar This will be an error in Hadoop 2.0 Can you please help me out how can I run this example?? ... View more

Apart from defining location for data, can you please try setting "stats" and "meta" to "/tmp/${YEAR}-${MONTH}-${DAY}" ? Please let us know if this works. Also, please let me know the Java version you are using, I suspect the change in behavior is due to possible change in how pattern matcher behaves between Java 7 and 8. ... View more

@Akshay Shingote has this been resolved? Can you post your solution or accept best answer? ... View more