You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/08/28 10:07:01 UTC
[jira] [Commented] (SQOOP-3196) Modify MySQLAuthTest to use
configurable test database parameters
[ https://issues.apache.org/jira/browse/SQOOP-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143579#comment-16143579 ]
ASF subversion and git services commented on SQOOP-3196:
--------------------------------------------------------
Commit 606eb5f581d7dd7f7c8f37d845799270d7656f78 in sqoop's branch refs/heads/trunk from [~anna.szonyi]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=606eb5f ]
SQOOP-3196: Modify MySQLAuthTest to use configurable test database parameters
(Szabolcs Vasas via Anna Szonyi)
> Modify MySQLAuthTest to use configurable test database parameters
> ------------------------------------------------------------------
>
> Key: SQOOP-3196
> URL: https://issues.apache.org/jira/browse/SQOOP-3196
> Project: Sqoop
> Issue Type: Test
> Reporter: Szabolcs Vasas
> Assignee: Szabolcs Vasas
> Attachments: SQOOP-3196.patch, SQOOP-3196.patch, SQOOP-3196.patch
>
>
> Most of the MySQL third party test cases use MySQLTestUtils to get the test database parameters because these parameters can be configured using system properties.
> One exception is MySQLAuthTest which uses a predefined database name, username and password which cannot be configured.
> The goal of this JIRA is to change MySQLAuthTest to use MySQLTestUtils since it would make setting up a new test database easier and make the MySQL third party test suite more consistent.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)