How to see which features have invalid source datasets when using a FeatureWrite?
Hi, i am copying files using the FeatureWriter with FileCopy and but some of them are missing but i dont get an attribute telling me which files are missing. All i get is this in the log: File Copy Writer: Skipped 401 features that contained invalid source datasets But what i would like is to route those with invalid source data set and have them write to an excel ark or similar so i know which files cant be found. But right now the features all come out of the same port with no distinction of wheter or not the copy was actually succesful. Which is not very useful for me.
Any help is very much appriciated :)
Page 1 / 1
One way to solve this is to use the Directory and File Pathnames reader to confirm if the file does exist or not, and only send the confirmed file features to the File Copy writer.
One way to solve this is to use the Directory and File Pathnames reader to confirm if the file does exist or not, and only send the confirmed file features to the File Copy writer.
Thank you for your answer.
How i wish this worked, that you could just set the source file as the data set for Directory and File Pathnames, but i seems it only reads folders not individual files. Is there a way to do this without having a Directory and File Pathnames reader read everything? It takes a very very long time. I have a 4TB harddrive with millions of files and i really only need to copy a few specific files over every time, but i do need to know if some files were not succesfully copied and which files they are.
Ah correct, sorry my bad. Then use good old Python. A PythonCaller with the following code works.
import fme import fmeobjects import os
class FeatureProcessor(object):
def __init__(self): pass
def input(self, feature: fmeobjects.FMEFeature): if os.path.exists(feature.getAttribute('FilePath')): feature.setAttribute("FileCheck","true") else: feature.setAttribute("FileCheck","false") self.pyoutput(feature)
def close(self): pass
Thank you very much :) It works great. I am going to save that as a custom transformer to use again another time.
