[
https://issues.apache.org/jira/browse/SQOOP-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718190#comment-14718190
]
Sqoop QA bot commented on SQOOP-2538:
-------------------------------------
Testing file
[SQOOP-2538.001.patch|https://issues.apache.org/jira/secure/attachment/12752949/SQOOP-2538.001.patch]
against branch sqoop2 took 0:53:09.394072.
{color:red}Overall:{color} -1 due to an error(s), see details below:
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:red}ERROR:{color} Patch does not add/modify any test case
{color:green}SUCCESS:{color} License check passed
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All unit tests passed (executed 1408 tests)
{color:green}SUCCESS:{color} Test coverage did not decreased
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/1649/artifact/patch-process/cobertura_report.txt])
{color:green}SUCCESS:{color} No new findbugs warnings
([report|https://builds.apache.org/job/PreCommit-SQOOP-Build/1649/artifact/patch-process/findbugs_report.txt])
{color:green}SUCCESS:{color} All integration tests passed (executed 73 tests)
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1649/console].
This message is automatically generated.
> Sqoop2: Use the table name variable instead of the table name string
> --------------------------------------------------------------------
>
> Key: SQOOP-2538
> URL: https://issues.apache.org/jira/browse/SQOOP-2538
> Project: Sqoop
> Issue Type: Bug
> Reporter: Dian Fu
> Assignee: Dian Fu
> Fix For: 1.99.7
>
> Attachments: SQOOP-2538.001.patch
>
>
> In {{DerbySchemaUpgradeQuery}}, there are some places which directly use the
> table name string instead of the table name variable when referring a table
> name. This makes it difficult to maintain.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)