[
https://issues.apache.org/jira/browse/SQOOP-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho resolved SQOOP-2042.
---------------------------------------
Resolution: Not A Problem
Semantics of the "schema" fields depend on database implementation. Derby,
PostgreSQL and Microsoft SQL Server do have the notion of schema whereas MySQL
and Oracle don't. The generic JDBC Connector supports all databases, so having
the concept of schema seems correct and sadly won't work for databases that
doesn't that concept.
> Sqoop2: "schema name" job config in JDBC FROM connector doesn't work as
> expected
> --------------------------------------------------------------------------------
>
> Key: SQOOP-2042
> URL: https://issues.apache.org/jira/browse/SQOOP-2042
> Project: Sqoop
> Issue Type: Bug
> Reporter: Gwen Shapira
> Fix For: 2.0.0
>
>
> 1. Created link with following connection string:
> jdbc:mysql://kafkaf-1:3306/hive1
> 2. Created job with this connector as "from" and schema = cm, table = hosts
> 3. Running job failed with error:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'hive1.HOSTS' doesn't exist
> ....
> at
> org.apache.sqoop.connector.jdbc.GenericJdbcExecutor.getPrimaryKey(GenericJdbcExecutor.java:208)
> 4. Created new link, this time with connection string:
> jdbc:mysql://kafkaf-1:3306
> 5. Created job with same configs but new connector
> 6. Got following error:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Incorrect
> database name ''
> ...
> at
> org.apache.sqoop.connector.jdbc.GenericJdbcExecutor.getPrimaryKey(GenericJdbcExecutor.java:208)
> It looks like the "schema name" config is completely useless.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
