The ZipAggregationStrategy is a persistent store (it writes to a file), although I’ve never tested it to see what it does in failure scenarios.
Maybe you could use a different aggregation strategy with one of the persistent repositories, and then when you’re competition timeout hits you could use the ZipFileDataFormat to write the zip file? > On May 11, 2016, at 11:18 AM, [email protected] wrote: > > Wondering if anyone has an example of using the ZipAggregationStrategy backed > by a persistent repository like leveldb, SQL or hawt. I tried getting it to > work but I am getting an error that type file isn't supported. Trying to > store the zip file is likely causing the issue. > > The happy path process reads messages off a Queue into a zip file via > ZipAggregationStrategy with a completionInterval. Between the > completionInterval, any messages sent to the Queue are consumed realtime and > stored by Camel as a zip under data/tmp/camel-12345. When the 30 minutes > has expired, the final zip gets processed and the contents of the tmp > directory are removed. > > The requirement is to protect against potential data loss. Open to > suggestions Thanks! > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/ZipAggregationStrategy-with-persistent-store-tp5782458.html > Sent from the Camel - Users mailing list archive at Nabble.com.
