[ 
https://issues.apache.org/jira/browse/FINERACT-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419266#comment-17419266
 ] 

Victor Romero commented on FINERACT-982:
----------------------------------------

[~awasum] I think that we should warn that there is no updated information 
about Drizzle driver (last date I could find is from 2016, this is the github 
project, which seems "dead" [https://github.com/krummas/DrizzleJDBC] ). I think 
it should not cause any issue, becase the drivers and url connections are 
different betweem Drizzle and MariaDB. We have selected a MariaDB version, 
which is compatible with MySQL 5.7. 

[~francisguchie] we have been looking for alternatives to Drizzle (which I 
think is prefered for the BSD license) until now only MySQL J Connector, 
MariaDB Connector and  AWS-MySQL Connector have been good candidates. It is 
important to look also for the compatibility required by Flyway. We have tried 
J-Asyc (Apache license), but the use cases are different.

I have the following thinking/opinion about having an oudated and "dead" 
artifact: we have to highlight and warn to tech and non tech that the JDBC 
connector is handling all the data from Fineract to the Database and if they go 
for a using it (Drizzle) is riskier for the data integrity and maintenance (for 
sure they are having issues and doing themselve a quick fix replacing with 
MySQL or MariaDB drivers). 

 

 

> Completely ditch use of Drizzle JDBC Driver after all
> -----------------------------------------------------
>
>                 Key: FINERACT-982
>                 URL: https://issues.apache.org/jira/browse/FINERACT-982
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Michael Vorburger
>            Priority: Blocker
>              Labels: scalability
>             Fix For: 1.6.0
>
>
> Fineract's use of the un-maintained Drizzle JDBC driver continues to cause 
> confusion and pains like FINERACT-980, and note e.g. the proposed removal of 
> the alternative MySQL JDBC driver in 
> [https://github.com/apache/fineract/pull/887.]
> Some of the background to this is recorded e.g. in FINCN-26, FINERACT-761 and 
> LEGAL-462.
> LEGAL-462 has clarified that the Fineract ZIP distribution must include 
> Drizzle and cannot distribute the MariaDB or MySQL JDBC clients. We CAN, and 
> currently (given the confusion in FINERACT-980 apparently do?!) use it for 
> tests.
> What if to reduce variability we just removed that old Drizzle JDBC driver 
> after all? We could run our tests using (preferably) the very well maintained 
> MariaDB JDBC driver client (the actual DB server is a totally separate 
> discussion, see FINERACT-896). We would (have to) distribute the ZIP for 
> download without a JDBC driver, and just some documentation inviting users to 
> DL and add one.
> But the exact situation about distributing in a Docker container image isn't 
> clear, to me...
> FYI [~awasum], [~ptuomola], [~xurror]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to