Martin, Thanks for the reply. This wasn't exactly the problem. I figured out that the problem is the 'newline' character in the password file is interpreted by the --password-file logic.
I got around it by 'echo -n <password> > password.file' and now the --password-file option works. I had the same problem earlier with the MySQL driver, but, it was a few weeks ago and I forgot that caused a problem. Might be something to put in the Sqoop User Guide, or remedy in Sqoop? It occurs to me this may have been addressed in Sqoop2 already, but I am not using Sqoop2 currently. For the record, I am using Sqoop 1.4.3 CDH 4.6. Thanks again all! *Devin Suiter* Jr. Data Solutions Software Engineer 100 Sandusky Street | 2nd Floor | Pittsburgh, PA 15212 Google Voice: 412-256-8556 | www.rdx.com On Thu, Mar 6, 2014 at 12:08 PM, Martin Thiele <[email protected]>wrote: > https://issues.apache.org/jira/browse/SQOOP-1226 has work around to try > > Sent from my iPhone > > > On Mar 6, 2014, at 11:59 AM, Devin Suiter RDX <[email protected]> wrote: > > Hello all, > > When building import jobs for Sqoop from MSSQL, I'm finding that the only > options for password-protected databases are to pass the password as part > of the connect string or to pass the 'integrated-security' parameter, which > doesn't work since I'm running from CentOS and it needs a Windows .dll > installed. If I pass it with the Sqoop --password or --password-file args > it does not work. > > Is there a --password-file option that is compatible in syntax with the > Microsoft JDBC4 SQL Server driver that anyone knows of? This seems a little > irresponsible and I am hoping I am missing something. The password file > option works great for the MySQL driver. > > Thanks, > *Devin Suiter* > Jr. Data Solutions Software Engineer > 100 Sandusky Street | 2nd Floor | Pittsburgh, PA 15212 > Google Voice: 412-256-8556 | www.rdx.com > >
