On Fri, Oct 23, 2009 at 7:30 AM, Kris Buelens <[email protected]> wrote:
> As for the original problem here: it is supposed to filter SCIF messages, so > I guess it is in a long running server, so keeping the files open until the > servers stops is probably not a good idea. So either EXECIO or FILESLOW > with a FINIS every now and then would be required. It's Plumbday already :-) If you made the "addpipe" append to the output file, you could for example put a "take 10" in and have it go away automatically after 100 records. The next record would then fire another addpipe again for this recipient. With SCIF it is not unlikely that records would be clustered, and a time-based approach might be more appealing. So you would put in a "beat" stage that closes a "gate" when no more records flowed for this particular recipient during 10 seconds or so. And nothing prevents you from combining these criteria. Another nifty approach would be to set up a pipeline warp for each recipient file. Maybe a bit overkill in this case (because all records come out of one place already) but fun to play with. Rob PS My apologies for not looking in whatever package you had on the download pages. I already have trouble to find my own left-over plumbing. And it is way more fun to write a fresh pipeline for what you really need at this point. Depends on your skills and tools. With installing a new faucet at home, I first look for a left-over piece of pipe that already has an appendix soldered on and see whether I can live with the place where it was bent already. And my wife would say "I thought you were going to put the faucet a bit more to the right..." :-)
