In the 2nd case, is there any producer’s error thrown in executor’s log?
Best Regards Richard From: kant kodali <kanth...@gmail.com> Date: Tuesday, December 5, 2017 at 4:38 PM To: "Qiao, Richard" <richard.q...@capitalone.com> Cc: "user @spark" <user@spark.apache.org> Subject: Re: Do I need to do .collect inside forEachRDD Reads from Kafka and outputs to Kafka. so I check the output from Kafka. On Tue, Dec 5, 2017 at 1:26 PM, Qiao, Richard <richard.q...@capitalone.com<mailto:richard.q...@capitalone.com>> wrote: Where do you check the output result for both case? Sent from my iPhone > On Dec 5, 2017, at 15:36, kant kodali > <kanth...@gmail.com<mailto:kanth...@gmail.com>> wrote: > > Hi All, > > I have a simple stateless transformation using Dstreams (stuck with the old > API for one of the Application). The pseudo code is rough like this > > dstream.map().reduce().forEachRdd(rdd -> { > rdd.collect(),forEach(); // Is this necessary ? Does execute fine but a > bit slow > }) > > I understand collect collects the results back to the driver but is that > necessary? can I just do something like below? I believe I tried both and > somehow the below code didn't output any results (It can be issues with my > env. I am not entirely sure) but I just would like some clarification on > .collect() since it seems to slow things down for me. > > dstream.map().reduce().forEachRdd(rdd -> { > rdd.forEach(() -> {} ); // > }) > > Thanks! > > ________________________________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. ________________________________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
