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-1252) Sqoop import from db2. Schema of import not in expected format.
Date Fri, 06 Dec 2013 16:05:36 GMT

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

Jarek Jarcec Cecho commented on SQOOP-1252:

Hi [~arijit999],
you seems to be using custom build of Sqoop that contains additional parameters not are not
usually available. I'm afraid that our abilities to help you will be therefore limited. I
would encourage you to contact provider of your custom build for additional help. 

Looking at the command line, Sqoop do not supports specifying the schema name inside the {{--table}}
parameter. You can use property {{currentSchema}} in the JDBC URL to specify different schema,
for example:

sqoop import --connect jdbc:db2://host/db:currentSchema=tstschema

> Sqoop import from db2. Schema of import not in expected format.
> ---------------------------------------------------------------
>                 Key: SQOOP-1252
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1252
>             Project: Sqoop
>          Issue Type: Bug
>          Components: sqoop2-api
>    Affects Versions: 1.4.2
>            Reporter: Arijit Choudhury
> When I try to sqoop import (Datastax 3.2.0) from DB2 database using the below command:
> ./dse sqoop import --connect jdbc:db2:// --username tst -P --table
tstschema."dsn_filter_table" --cassandra-keyspace SqoopTest --cassandra-column-family actest2
--cassandra-row-key PREDNO --cassandra-thrift-host --cassandra-create-schema
--split-by PREDNO
> [ DB2 Select query: select * from SchemaName.TableName with ur; ]
> Why I am not getting the schema in proper format as it is in DB2? Why in Cassandra column
name are getting into rows? Request your help to resolve the issue.

This message was sent by Atlassian JIRA

View raw message