Really simple use case, but extremely frustrating issue. Processors Used:
- ListS3 for a prefix (directory path) without filename (so multiple files) included
- I see the files I want in the queue a few seconds later correctly named with full prefix
- Run FetchS3Object
- On the other side of this processor there is something odd:
It's at this point that I can see the filenames are wacky. Sometimes the filenames are from other locations in s3, other times they will be the name of file that I haven't pulled in weeks. Seems like we're in a corrupt state, but I don't know how to get back to 0. The file contents are CORRECT, this is an issue with the filename property.