agreed

 

Dr Mich Talebzadeh

 

LinkedIn  
https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw

 

http://talebzadehmich.wordpress.com <http://talebzadehmich.wordpress.com/> 

 

NOTE: The information in this email is proprietary and confidential. This 
message is for the designated recipient only, if you are not the intended 
recipient, you should destroy it immediately. Any information in this message 
shall not be understood as given or endorsed by Peridale Technology Ltd, its 
subsidiaries or their employees, unless expressly so stated. It is the 
responsibility of the recipient to ensure that this email is virus free, 
therefore neither Peridale Technology Ltd, its subsidiaries nor their employees 
accept any responsibility.

 

 

From: Russell Jurney [mailto:[email protected]] 
Sent: 19 February 2016 16:49
To: Jörn Franke <[email protected]>
Cc: Divya Gehlot <[email protected]>; user @spark <[email protected]>
Subject: Re: Spark JDBC connection - data writing success or failure cases

 

Oracle is a perfectly reasonable endpoint for publishing data processed in 
Spark. I've got to assume he's using it that way and not as a stand in for HDFS?

On Friday, February 19, 2016, Jörn Franke <[email protected] 
<mailto:[email protected]> > wrote:

Generally oracle db should not be used as a storage layer for spark due to 
performance reasons. You should consider HDFS. This will help you also with 
fault - tolerance.

> On 19 Feb 2016, at 03:35, Divya Gehlot <[email protected] 
> <javascript:;> > wrote:
>
> Hi,
> I am a Spark job which connects to RDBMS (in mycase its Oracle).
> How can we check that complete data writing is successful?
> Can I use commit in case of success or rollback in case of failure ?
>
>
>
> Thanks,
> Divya

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] <javascript:;> 
For additional commands, e-mail: [email protected] <javascript:;> 



-- 

Russell Jurney twitter.com/rjurney <http://twitter.com/rjurney>  
[email protected] <mailto:[email protected]>  relato.io 
<http://relato.io> 

 

Reply via email to