the camel-hdfs producer will throw an error if the send operation fails...internally it just uses a standard HdfsOutputStream...so any step in the route following this send would only be triggered upon successful send operation, and you can use standard Camel onException/doCatch routing exception handling to deal with errors, etc.
mister blinky wrote > Thanks for your response. I think i got it. Let me state it to confirm, > then I have a follow up question. > > So the / > .to( > <endpoint-type> > : > <URL-of-endpoint-API> > ) / > establishes a contract with Camel that a) the / > endpoint-type / > defines the message format among other things required by the endpoint; > and b) the / > URL-of-endpoint-API / > establishes where the service is located and any other arguments that the > service generally requires. > > As such, in this one-way case, there is no need for Camel on the HDFS > side, since, from HDFS's point of view, it's just getting a normal web API > call. Correct? * > Here's my follow up. * > What if I want the HDFS server to reply back to the calling server to say > "ok i'm done and i failed/succeeded"? Assuming for the moment that there > is no such thing on the remote side, how would one use Camel to facilitate > not just the sending of the message to the API, but a response from the > API saying it's done? Is that a case, what role would Camel play on the > remote server? Is this a typical scenario? > > thank you. ----- Ben O'Day IT Consultant -http://consulting-notes.com -- View this message in context: http://camel.465427.n5.nabble.com/Super-basic-questions-tp5746261p5746288.html Sent from the Camel - Users mailing list archive at Nabble.com.
