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] [Updated] (SQOOP-2242) Sqoop2: Add support for full table names into our DatabaseProvider infrastructure
Date Fri, 20 Mar 2015 00:14:38 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Jarcec Cecho updated SQOOP-2242:
--------------------------------------
    Attachment: SQOOP-2242.patch

> 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)

Mime
View raw message