Hi Dan, Unfortunately when the driver option is included in the Sqoop command, the built-in connection manager selection defaults to the generic connection manager - please see SQOOP-461, which is applicable to other databases besides Oracle.
Regards, Kathleen On Thu, Jul 12, 2012 at 2:57 PM, Dan Richelson <[email protected]> wrote: > Hi, > I am using Sqooop 1.4.1-cdh4.0.0 hitting a PostgreSQL 8 server. > > Since I need a working call to "SELECT CURRENT_TIMESTAMP" (PostgreSQL > specific) instead of "SELECT CURRENT_TIMESTAMP()" (more generic, found > in the default connection manager), I added > --connection-manager org.apache.sqoop.manager.PostgresqlManager > to my command. I also added: > --driver org.postgresql.Driver (which i have now learned is irrelevant > in my case since sqoop infers the proper driver from the jdbc url.) > > However, this setup caused the --connection-manager setting to be > ignored (even though it shows up in my saved job), so I ended up > getting the problem described here: > https://issues.apache.org/jira/browse/SQOOP-364 > > Omitting the --driver argument fixed my problem, but this was not easy > to track down and there was no message stating that my > connection-manager setting was being ignored. > Is this a defect? > > > > > > > > > -- > Dan Richelson, Software Engineer > > Tendril > 2560 55th St. | Boulder, Colorado 80301 > M 303-709-2214 > www.tendrilinc.com > > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > If you have received this email in error please notify the sender. > Please note that any views or opinions presented in this email are solely > those of the author and do not necessarily represent those of the company. > Finally, the recipient should check this email and any attachments for the > presence of viruses. > The company accepts no liability for any damage caused by any virus > transmitted by this email. >
