[
https://issues.apache.org/jira/browse/FINERACT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081743#comment-17081743
]
Michael Vorburger commented on FINERACT-762:
--------------------------------------------
Given that we cannot distribute Fineract on
[http://fineract.apache.org|http://fineract.apache.org/] with the MariaDB or
MySQL JDBC driver instead of Drizzle, I think what we should do here is to
create (an) alternative Docker image(s), which remove Drizzle and configure the
other driver(s) instead.
We could either distribute those on Apache Docker Hub, or do this outside of
the Apache project, and just have a small repo with the Dockerfile on
[https://github.com/openMF/] and distribute it there (similarly to
https://github.com/openMF/community-app/issues/3112).
> Use of (unmaintained) Drizzle JDBC driver in Fineract at run-time (not build)
> is sub-optimal for performance
> ------------------------------------------------------------------------------------------------------------
>
> Key: FINERACT-762
> URL: https://issues.apache.org/jira/browse/FINERACT-762
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Michael Vorburger
> Priority: Major
> Labels: performance
>
> Creating this issue to clarify that while FINERACT-761 is focused on (only)
> the build time use of the Drizzle JDBC driver (which does not lead to it
> being included in the final Fineract end-user distribution), this is re. the
> use of it at run-time, which is packaged in the distribution.
> The two uses are technically unrelated. While the use of Drizzle instead of
> Connector/J in the build is a a blocking issue, the use at run-time is not a
> blocking problem, currently. It's perhaps still not ideal to maintain on a
> completely unmaintained library (Drizzle) for database access, e.g. for
> performance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
