Re: Exporting to non standard databases

2014-08-24 Thread Muthu Pandi
Pls Ignore the previous mail Thanks guys for the help and for info found that "--batch" option is working which support batch export without " -Dsqoop.export.records.per.statement=1". *Regards Muthupandi.K* [image: Picture (Device Independent Bitmap)] On Mon, Aug 25, 2014 at 11:18 AM, Mut

Re: Exporting to non standard databases

2014-08-24 Thread Muthu Pandi
Thanks guys for the help and for info found that "--direct" option is working which support batch export without " -Dsqoop.export.records.per. statement=1". *Regards Muthupandi.K* [image: Picture (Device Independent Bitmap)] On Mon, Aug 25, 2014 at 11:04 AM, Gwen Shapira wrote: > It won'

Re: Exporting to non standard databases

2014-08-24 Thread Gwen Shapira
It won't be super fast since its row-by-row insert, but 2GB is not huge, so I'll expect this will take only few minutes. On Sun, Aug 24, 2014 at 10:23 PM, Muthu Pandi wrote: > Spot on!!! Jarcec > >Thanks for the quick reply, you have saved my lot of time. > >Can this be used for

Re: Exporting to non standard databases

2014-08-24 Thread Muthu Pandi
Spot on!!! Jarcec Thanks for the quick reply, you have saved my lot of time. Can this be used for exporting larger data since we are exporting in bulk. My data will be of size 2GB Per day and will export at end of the day. *Regards Muthupandi.K* [image: Picture (Device Indepen

Re: Exporting to non standard databases

2014-08-24 Thread Jarek Jarcec Cecho
Hi Muthu, the given message is a “Warning” and not an “Error”. Sqoop is warning you that you are using —driver option that will force Sqoop to use Generic JDBC connector. That is fine in your case as Sqoop don’t have specialized connector for Vertica. You can always use --connect-manager paramet