Thank you Claus,
indeed, download=false I have overlooked.
However thinking further it would require to configure
two routes/pollers with size filters:
(1) for normal files with default &download= and
(2) for over-sized with &download=false and &move=away.
Unless &download= accepts an expression
alike ${file.size <= 1234567890}.
Best regards
Cc.
--
Mr. Petr Kužel, Software Engineer
-----Original Message-----
From: Claus Ibsen <[email protected]>
Sent: Wednesday, 11 December, 2024 7:22
To: [email protected]
Subject: Re: FTPS moving away over-sized files remotely without downloading them
Hi
There is a download=false option
On Tue, Dec 10, 2024 at 3:08 PM Petr Kuzel
<[email protected]> wrote:
> Hi riders,
>
> We have defined a max file size to be accepted and processed.
>
> Now, I wonder if it's possible to get the effect of &moveFailed= (a
> remote move) before a from()-exchange is created (which means a remote
> file body was already downloaded to the local working dir).
>
> I have tried at the level of poll filters, which have all needed file
> properties before a file body is downloaded, but to no avail.
>
> Have I overlooked anything evident, please?
>
> (Having said that, I do not need to over-optimize rejecting the
> over-sized files: downloading them just to check size and provoke
> moveFailed is terribly inefficient but acceptable.)
>
> Best regards
> Cc.
> --
> Mr. Petr Kužel, Software Engineer
> Eurofins Scientific S.E.
> L-8399 Windhof
>
>
>
--
Claus Ibsen
-----------------
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
