If you use noop=true then you need to use idempotentKey to tell Camel that file size / timestamp can denote a new file.
See more details at idempotentKey http://camel.apache.org/file2 And mind there was a bug that was just fixed in the upcoming 2.12.2 release, and 2.11.3 what is on the way. On Tue, Nov 26, 2013 at 6:34 PM, Tobias Hinz <tobias.h...@gmail.com> wrote: > eek, something got lost: > > > public void configure() { > > CsvDataFormat csv = new CsvDataFormat(); > csv.setDelimiter("\t"); > > > from("file:///data/csv/test/?charset=ISO8859-1&noop=true&moveFailed=.error/${file:name.noext}-${date:now:yyyyMMddHHmmssSSS}.${file:ext}") > .split().tokenize("\n") > .choice() > .when(simple("${property.CamelSplitComplete} == > true")) > .log("set or update alias") > .to("direct:setAlias") > .when(simple("${property.CamelSplitIndex} > 0")) > .unmarshal(csv) > .to("direct:doMapping") > .otherwise() > .log("Loading new Feed-File") > .end() > ; > > from("direct:doMapping") > .process(new Mapping()) // mapping processor sets new index > name > for the elasticsearch index > > .to("elasticsearch://elasticsearch?operation=INDEX&indexName=data_test&indexType=es_t_data_product&ip=192.168.101.139&port=9300"); > > from("direct:setAlias") > .process(new SetAlias()) // mapping processor sets new index > name > for the elasticsearch index > .log("Done setting or updating new Alias..."); > } > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/consume-existing-already-consumed-files-on-modifed-date-or-size-tp5743867p5743868.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
