Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
Description
I'm using the 'move' fs action and I first got the following error:
FS001: Missing scheme in path [/projects/ngdstone/user/ogg_oozie/intermediate/tmp_price_feats_uniq/.pig_header]
when I had the following in my workflow.xml :
<fs>
<move source='${OUT}/intermediate/tmp_price_feats_uniq/.pig_header'
target='${OUT}/intermediate/tmp_predict_supply_feats/'/>
<move source='${OUT}/intermediate/tmp_price_feats_uniq/.pig_header'
target='${OUT}/intermediate/tmp_predict_supply_feats/'/>
</fs>
I then prefixed the namenode URI to the paths (like I did for the <prepare> paths), as such:
<fs>
<move source='${nameNode}${OUT}/intermediate/tmp_price_feats_uniq/.pig_header'
target='${nameNode}${OUT}/intermediate/tmp_predict_supply_feats/'/>
<move source='${nameNode}${OUT}/intermediate/tmp_price_feats_uniq/.pig_header'
target='${nameNode}${OUT}/intermediate/tmp_predict_supply_feats/'/>
</fs>
However, I now get this error:
FS003: Scheme [hdfs] not allowed in path
[hdfs://mithrilblue-nn1.blue.ygrid.yahoo.com:8020/projects/ngdstone/user/ogg_oozie/intermediate/tmp_predict_supply_feats]
it seems the 'scheme' is only needed for the source path, but not the target. This is inconsistent.
Finally, if the source path is a file and the target path is a directory, Oozie will complain that the target already
exists. I feel it should be consistent with the Hadoop CLI (and Unix) and simply understand that the source should be
placed under the target directory.