sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1654) Sqoop cannot export data to SQLServer when table is not belongs to user's default schema
Date Sun, 02 Nov 2014 23:33:34 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194089#comment-14194089
] 

Jarek Jarcec Cecho commented on SQOOP-1654:
-------------------------------------------

I'm wondering how you are entering the schema name [~q79969786]? The parameter {{\-\-table}}
should be used exclusively for table name (no schema name there). We have a special extra
argument called {{\-\-schema}} in Microsoft SQL Server Connector for specifying custom schema
names:

{code}
sqoop import ... -- --schema your_schema
{code}

> Sqoop cannot export data to SQLServer  when table is not belongs to user's default schema
> -----------------------------------------------------------------------------------------
>
>                 Key: SQOOP-1654
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1654
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.4.4
>         Environment: hadoop-1.2.1 + hive-0.12 + sqoop-1.4.4 + SQLServer 2008
>            Reporter: q79969786
>              Labels: patch
>         Attachments: 1654.patch
>
>
> if my default schame is dbo, I can export to table belongs dbo without specify schame
name, but if I  want to export to other schema, like [guest].[test], sqoop use ' SELECT t.*
FROM [[guest].[test]] AS t WHERE 1=0' to get column types. It will throw Exception.
> I try to fix it by modify org.apache.sqoop.manager.SQLServerManager ant it worked



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message