Wilson --
That's what I was trying to point out in my rudimentary explanation in the
post above yours. I'm wiring the two routes up as we speak.
I'm just curious as to why the original FTP route doesn't do the exact same
thing? If I specify a localWorkDirectory and streamDownload, shouldn't th
Yes I read that and understand how to do it. But If I do the FTP with a
localWorkingDirectory, once the route ends, doesn't the file get removed?
So Shouldn't it be:
from(ftp_endpoint).to(local_file)
Then Have another route started up
from(local_file).split().process().to(kafka_endpoint)
Th
Looks like I'm going to have to split this into two routes.
Using streamDownload=true doesn't really change it.
So it looks like I'm going to have to:
1.) Get the file from the FTP Endpoint and store it locally (Route 1)
2.) Stream in the local File and split it (Route 2)
Question is: How d
That's what I figured. But the body is already a String type, so if I do the
route above without the marshal(), I don't get the content of the file in
the Exchange, but rather I get just the file name and some other content
(see the last part of my original post above).
Here is my Route withou
That's sort of the problem. It seems I can't even do a
marshal().string("UTF-8") before the split as it seems to run out of heap
space.
Here's what I've tried:
public void configure() throws Exception {
from(ftpToKafkaObj.getFtpEndpoint())
.marshal().string("UTF-8")
Hey Guys,
So I'm trying to implement the following Route:
FTP --> Get Large log file (3G) --> Copy to Local Working Directory -->
Aggregate File into chunks of some size (BatchSize = 1000) --> Write Each
Batched Exchange to a Kafka Topic.
Now i'm able to get the route working for small files ( <
