Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Sqoop >> mail # user >> Sqoop Export with Netezza


Copy link to this message
-
Re: Sqoop Export with Netezza
Thanks Rakesh for your question.

For faster response, I would suggest directing Cloudera specific questions
to [EMAIL PROTECTED].

Regards, Kathleen

On Thu, May 31, 2012 at 7:42 AM, Neelavar Rao, Rakesh <
[EMAIL PROTECTED]> wrote:

>  Any suggestions/comments ?****
>
> ** **
>
> *From:* Neelavar Rao, Rakesh
> *Sent:* Tuesday, May 29, 2012 5:29 PM
> *To:* [EMAIL PROTECTED]
> *Subject:* Sqoop Export with Netezza****
>
> ** **
>
> Hi,****
>
> ** **
>
> Wanted to know the experience of people who have used sqoop export from
> HDFS to Netezza RDBMS.  Does it generate insert statements for each row to
> be inserted?  We did a small POC and saw from the query logs individual
> insert statements. Since Netezza does not support multi row inserts does it
> do individual insert statements?  Most of the netezza discussion forums
> advise not to have individual inserts in netezza specially if you have
> large dataset to insert.  Does Cloudera’s Netezza connector do something
> under the hood to speed up this process? ****
>
> ** **
>
> Any feedback would be greatly appreciated. ****
>
> ** **
>
> [image: Description: Description: Description: Quaero.png]****
>
> *Rakesh Neelavar Rao*
>
> *Quaero, A CSG Solution*
> Big Data - Platform Architecture
> (*O*) 704.687.5861 | (*M*) 704.840.2856
> www.quaero.com | Follow Quaero’s InsightIQ Blog<http://quaero.csgsystems.com/blog/>
> ****
>
> ** **
>
> ** **
>
> ------------------------------
> All emails in this message string and any attachments are the confidential
> information of CSG Systems International, Inc. (CSG), or its affiliates and
> subsidiaries, and may contain privileged and/or confidential material. If
> you are not an intended recipient, please delete it immediately and notify
> the sender; unintended recipients are not authorized to read or otherwise
> use the information contained herein.
>