You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Sqoop QA bot (JIRA)" <ji...@apache.org> on 2015/03/20 03:10:39 UTC
[jira] [Commented] (SQOOP-2242) Sqoop2: Add support for full table
names into our DatabaseProvider infrastructure
[ https://issues.apache.org/jira/browse/SQOOP-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370566#comment-14370566 ]
Sqoop QA bot commented on SQOOP-2242:
-------------------------------------
Testing file [SQOOP-2242.patch|https://issues.apache.org/jira/secure/attachment/12705764/SQOOP-2242.patch] against branch sqoop2 took 0:54:20.968688.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} Patch add/modify test case
{color:green}SUCCESS:{color} License check passed
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All fast unit tests passed (executed 670 tests)
{color:green}SUCCESS:{color} All slow unit tests passed (executed 1 tests)
{color:green}SUCCESS:{color} All fast integration tests passed (executed 46 tests)
{color:green}SUCCESS:{color} All slow integration tests passed (executed 20 tests)
Console output is available [here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1194/console].
This message is automatically generated.
> 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)