Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: message received from 54.164.171.186
 which is an MX secondary for users@camel.apache.org)
MIME-Version: 1.0
In-Reply-To: <1429709445544-5766160.post@n5.nabble.com>
References: <1429622950073-5766108.post@n5.nabble.com>
 <CAGB5yNmLcPkZFHmmCTjJdnca=20hao2Ybg7cmfKNwuGjfP9Fxw@mail.gmail.com>
 <1429709445544-5766160.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 22 Apr 2015 17:49:04 +0200
Message-ID: 
 <CAGB5yNnM4jWCbH_QbFbD0+EaqDnCfUv2ABp-AeXyo_5m-veoxw@mail.gmail.com>
Subject: Re: Reading a file using camel stream component
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi

Yeah not sure how easy it is to add logic to detect when a file
rollover. Maybe it reads the first N bytes and make a hash or
something. And then if the retry do the same, and when the hash no
longer matches then its assume a new file that was rolled over, and it
beings emit the data.


On Wed, Apr 22, 2015 at 3:30 PM, Akram <akram.sa18@gmail.com> wrote:
> I tried it, but retry was keep on reading the same file again and again
> before the new file gets generated.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Reading-a-file-using-camel-stream-component-tp5766108p5766160.html
> Sent from the Camel - Users mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/