[
https://issues.apache.org/jira/browse/FINERACT-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yemdjih Kaze Nasser reassigned FINERACT-982:
--------------------------------------------
Assignee: Yemdjih Kaze Nasser
> 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
> Assignee: Yemdjih Kaze Nasser
> Priority: Major
> Labels: scalability
>
> 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)
