Ask Your Question

MaprFS executor ${record:value('/filepath')} returning empty string?

asked 2018-03-13 19:02:51 -0600

lampshadesdrifter gravatar image

Trying to follow the example case for changing meta data for a hadoopFS using an executor as per the docs ( However using file_path=${record:value('/filepath')} for the executor task, I get the error:

java.lang.IllegalArgumentException: Can not create a Path from an empty string

Yet looking at the docs for the MaprFS executor (which I am using) (, I seem to be using the correct variable for the path. Note that the data that I am using is in wholefile format. Does anyone know what is happening here? Thanks.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2018-03-14 16:00:12 -0600

lampshadesdrifter gravatar image

As per the docs (, there is another field to try: ${record:value('/targetFileInfo/path')} (I don't exactly understand the difference between when each applies, but...). Running the pipeline and examining the error records from the maprFS destination event outputs, I see that there is the field /targetFileInfo/path that does appears to contain a string that is the absolute path to the file that was just transferred. Using that in the executor seems to have resolved that problem.

However, now we get error:

2018-03-14 09:50:35,769 jabsom-test-pilot_brfss/jabsomtestpilotbrfsse1245d50-7b59-4dd6-b3fc-76d446b4ae4a ERROR Failure when applying metadata changes to HDFS HdfsMetadataExecutor *admin 0 Spool Directory Runner - 0 Could not set owner/group mapr/mapr for path /data_repo_mt/tenant_volumes/jabsom_chen/jabsom_chen_sa/brfss/2018_03_14/ Edit Pin to top Mark as spam Delete an hour ago reed REPORTER

The problem there seems to be that while the sdcuser can change the permission bits and group ownership of the files, only root can change the owner of a file (the sdcuser can't "give away" their files) (see

In any case, the empty string problem has been solved and just wanted to include that extra bit of info because it seems like a likely next-error that users with this same problem are likely to encounter.

edit flag offensive delete link more
Login/Signup to Answer

Question Tools

1 follower


Asked: 2018-03-13 19:02:51 -0600

Seen: 337 times

Last updated: Mar 14 '18