I just checked the change log, it looks like the patch of CAMEL-5883 didn't address the batch issue well. So I just reopen the JIRA[1] for it.
[1]https://issues.apache.org/jira/browse/CAMEL-5883 -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thursday, July 11, 2013 at 8:33 AM, Ashwin Pejavar wrote: > This is specific to camel 2.11.0. Done file deletion worked as expected in > 2.10.0 > > Scenario: > I have a fileConsumer configured for a directory with done files. It is > expected that every file dropped in the directory has a <filename>.done > file. > > In both 2.10.0 and 2.11.0 files are consumed successfully when copied over > with the appropriate done file. However in 2.11.0, only the done file > associated with the last file is deleted. All the other done files remain. > > Looking at the code in GenericFileOnCompletion.processStrategyCommit(...) > for 2.11.0, only the done file associated with the last file in batch is > deleted. > > It sounds like the intent was only one done file for a batch. But this is an > incorrect assumption that does not line up with documentation. It might work > when I have a non-specific done file name (e.g. start) when I want to > process all files in a directory, but definitely won't work when I have a > done file per input file. > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Done-file-not-deleted-tp5735497.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
