You are viewing a plain text version of this content. The canonical link for it is here.

Posted to submarine-dev@hadoop.apache.org by "zhulinhao (Jira)" <ji...@apache.org> on 2019/09/10 08:58:00 UTC

[jira] [Resolved] (SUBMARINE-177) Replace mysql-driver in the submarine-service with derby-driver

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

zhulinhao resolved SUBMARINE-177.
---------------------------------
    Resolution: Won't Do

By verification, Derby's driver cannot access the mysql database, so this problem cannot be resolved.

The tentative alternative is to set mysql-connector-java.jar in the pom file to provide and test scope, without packing it into the final release package, and provide a script to help users download it.

> Replace mysql-driver in the submarine-service with derby-driver
> ---------------------------------------------------------------
>
>                 Key: SUBMARINE-177
>                 URL: https://issues.apache.org/jira/browse/SUBMARINE-177
>             Project: Hadoop Submarine
>          Issue Type: Sub-task
>            Reporter: zhulinhao
>            Assignee: zhulinhao
>            Priority: Major
>             Fix For: 0.2.0
>
>
> Mysql -connector- Java belongs to the GPL v3 protocol, to prevent pollution, pre-developed Derby driver, can normally access the mysql database.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)