[SQOOP-2243] Sqoop2: Improve GenericJDBC Connector

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.99.5
• Fix Version/s: 2.0.0
• Assignee: Jarek Jarcec Cecho
• Reporter: Jarek Jarcec Cecho
• Created: 20/Mar/15 00:36
• Updated: 30/Mar/15 06:07

Description

GenericJDBCConnector has been the first connector written several years back. Since then we've tweak it here and there, but it seems that the code base do need to fix few bugs and add additional features.

Sub-Tasks

• Sqoop2: Generic JDBC: Automatically escape table and column names from configuration objects: Resolved
• Sqoop2: Generic JDBC: Add support for schema name for staging table: Open
• Sqoop2: Use jdbcProperties when creating database connection in GenericJDBCExecutor: Resolved
• Sqoop2: Use LinkConfiguration in Executor rather then LinkConfig: Resolved
• Sqoop2: Generic JDBC: Drop support for specifying custom query when exporting data: Resolved
• Sqoop2: Generic JDBC: Drop tests for specifying schema name and custom SQL at the same time: Resolved
• Sqoop2: Generic JDBC: Properly detect compound primary keys in GenericJdbcExecutor: Resolved
• Sqoop2: Generic JDBC: Prevent use of tableColumns and sql at the same time: Resolved
• Sqoop2: Generic JDBC: Remove duplicate code to create schema from result set metadata: Open
• Sqoop2: Generic JDBC: Convert input Columns from String to List: Resolved