You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2015/03/20 00:45:38 UTC
[jira] [Created] (SQOOP-2242) Sqoop2: Add support for full table
names into our DatabaseProvider infrastructure
Jarek Jarcec Cecho created SQOOP-2242:
-----------------------------------------
Summary: Sqoop2: Add support for full table names into our DatabaseProvider infrastructure
Key: SQOOP-2242
URL: https://issues.apache.org/jira/browse/SQOOP-2242
Project: Sqoop
Issue Type: Bug
Affects Versions: 1.99.5
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 1.99.6
Currently our {{DatabaseProviders}} have various methods that accepts String as a table name. This imposes a problem as when we need to add schema name, we need to create additional set of methods which is unfortunate. It's also a bit of a problem because we're heavily using variable length arguments when we can easily get to ambiguous method calls.
Hence I would like to propose introducing a {{TableName}} class that will encode all that is necessary to describe table names - table name itself and then optional parts such as schema or database name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)