This sounds promising. I can give it a try. Assuming this is the proper place to download the code for ListFile, can you tell me how to pull the correct source code? I've not yet done this. I would definitely go the route of fixed folder path with Expression Language support. -Jim
On Sat, Jan 27, 2018 at 7:09 PM, Mike Thomsen <[email protected]> wrote: > It's input requirement is set to INPUT_FORBIDDEN. It shouldn't be too hard > to set that to INPUT_ALLOWED and make it able to handle a flowfile or a > fixed folder path (or even better, fixed folder path w/ EL support). If you > do a patch, I'll try to find time to do a review. > > On Fri, Jan 26, 2018 at 4:03 PM, James McMahon <[email protected]> > wrote: > >> My customer has posted a requirement for a generalized List / Fetch >> workflow. I would not be able to express the target directory in the >> ListFile as a fixed value because I would need to reset the input directory >> each workflow cycle, and the target input directories will not share any >> common parent. >> >> Has anyone recently explored an approach to feed the ListFile or >> equivalent its target input directory dynamically? It does not seem >> possible to do that. I've failed to figure this out before, not being able >> to determine a way to precede the ListFile in the workflow. >> > >
