Hi Jarek, Thanks for your explanation and I understand the situation now.
However, unfortunately in my case, I must use the 1.4.1-incubating release and should apply patch-540 on it :-( So how can I know which other patches should be applied on 1.4.1-incubating release before patch-540 in advance? 2013/1/8 Jarek Jarcec Cecho (JIRA) <[email protected]> > > [ > https://issues.apache.org/jira/browse/SQOOP-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546698#comment-13546698] > > Jarek Jarcec Cecho commented on SQOOP-540: > ------------------------------------------ > > Hi Sam, > 1.4.1-incubating is quite old release. It might simply happened that the > underlying files has been changed and thus the patch is not applying > cleanly. The patch is already committed, so you might simply build trunk in > order to get build with this patch. > > Jarcec > > > Microsoft SQL Connector doesn't support custom schemas > > ------------------------------------------------------ > > > > Key: SQOOP-540 > > URL: https://issues.apache.org/jira/browse/SQOOP-540 > > Project: Sqoop > > Issue Type: New Feature > > Components: connectors/sqlserver > > Affects Versions: 1.4.1-incubating, 1.4.2 > > Reporter: Giovanni Ruggiero > > Assignee: Jarek Jarcec Cecho > > Fix For: 1.4.3 > > > > Attachments: SQOOP-540.patch > > > > > > Trying list-tables on the Microsoft test db AdventureWorks2008R2, Sqoop > lists only the tables of the dbo (default) schema. > > Trying to import a table which belongs to a schema different from dbo, > it fails with the message Invalid object name. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira >
