This Jira has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems email email@example.com
During investigation on SQOOP-818 I've noticed that automatically escaping table name when saving to mapreduce configuration introduced in SQOOP-601 might cause issues to third party connectors that are expecting that the name won't be ever escaped.
Missing method setConnManager(Lcom/cloudera/sqoop/manager/ConnManager;)V in ExportJobContContext breaks MS SQL Connector
Microsoft SQL Connector doesn't support custom schemas
Support custom schemas in PostgreSQL Connector