[
https://issues.apache.org/jira/browse/SQOOP-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370576#comment-14370576
]
ASF subversion and git services commented on SQOOP-2242:
--------------------------------------------------------
Commit 756a3c17e20c109e355f386e330985f1d4c695b5 in sqoop's branch
refs/heads/sqoop2 from [~abec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=756a3c1 ]
SQOOP-2242: Sqoop2: Add support for full table names into our DatabaseProvider
infrastructure
(Jarek Jarcec Cecho via Abraham Elmahrek)
> 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
>
> Attachments: SQOOP-2242.patch
>
>
> 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)
