-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.7.3, 3.0.0-alpha3
-
Fix Version/s: 2.7.3
-
Component/s: None
-
Labels:None
Distcp should add a default AtomicWorkPath properties when using atomic
Distcp#configureOutputFormat using code below to generate atomic work path,
if (context.shouldAtomicCommit()) { Path workDir = context.getAtomicWorkPath(); if (workDir == null) { workDir = targetPath.getParent(); } workDir = new Path(workDir, WIP_PREFIX + targetPath.getName() + rand.nextInt());
When atomic is set and AtomicWorkPath == null, distcp will get the parent of current WorkDir. In this case, if workdir is "/", the parent will be null, wich means
workDir = new Path(workDir, WIP_PREFIX + targetPath.getName() + rand.nextInt()); will throw a nullpoint exception.
- is depended upon by
-
HADOOP-15788 Improve Distcp for long-haul/cloud deployments
-
- Open
-
- is related to
-
HADOOP-14567 DistCP NullPointerException when -atomic is set but -tmp is not
-
- Open
-