My understanding is that the “truncate prefix” option in the File Uploader node should truncate the prefix from the source URI to keep only the subdirectories within the search path (coming from the List Files node).
E.g: source file is in c:\files\FACT_EVENTS\2018\01
target directory is in s3://FACT_EVENTS
prefix is c:\files\FACT_EVENTS
so that the 2018/01 gets created in S3 below FACT_EVENTS
Unfortunately, it keeps creating a directory with an empty name and, below, the following structure: files/FACT_EVENTS/2018/01.
In other words, the source path is not truncated.
Has anyone a successful experience using this node?
Sry for a delay on this one. I have tested it and it is not working for me either. In the print screen from Upload node result you can see the double slash and that is the cause for a directory with empty name. For me there is no difference in options Use full path or Truncate prefix…
Just to catch up on this one. There has been some improvements on this matter in new KNIME version. However there are still some limitations when there is white space contained in truncate prefix path. This is still in investigation and hopefully will be fixed soon.
Note: When path from truncate prefix is not matched (whether it is written incorrectly or due to a bug) fallback to full path is used.
stumbled across this suuuper annoying issue too. Tried to mitigate it by escaping the space "\ ", by using URL encoded “%20” spaces and just plain white spaces " ". Nothing worked. Only workaround is to adjust all local files paths which why it’s suuuper annoying.
Update: It’s is not working at all. I used a URL and a truncate path without any white space but still the undesired path segments were present. IMPORTANT to note is that I used a variable. Upon using a fixed string, which is identical, it worked!
