[jira] [Updated] (FINERACT-762) Use of (unmaintained) Drizzle JDBC driver in Fineract at run-time (not build) is sub-optimal for performance
[ https://issues.apache.org/jira/browse/FINERACT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-762: --- Labels: scalability technical (was: performance technical) > 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: Improvement >Reporter: Michael Vorburger >Assignee: Michael Vorburger >Priority: Major > Labels: scalability, technical > Fix For: 1.4.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > 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)
[jira] [Updated] (FINERACT-762) Use of (unmaintained) Drizzle JDBC driver in Fineract at run-time (not build) is sub-optimal for performance
[ https://issues.apache.org/jira/browse/FINERACT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-762: --- Fix Version/s: 1.4.0 > 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: Improvement >Reporter: Michael Vorburger >Assignee: Michael Vorburger >Priority: Major > Labels: performance, technical > Fix For: 1.4.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > 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)
[jira] [Updated] (FINERACT-762) Use of (unmaintained) Drizzle JDBC driver in Fineract at run-time (not build) is sub-optimal for performance
[ https://issues.apache.org/jira/browse/FINERACT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-762: --- Issue Type: Improvement (was: Bug) > 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: Improvement >Reporter: Michael Vorburger >Priority: Major > Labels: performance, technical > > 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)
[jira] [Updated] (FINERACT-762) Use of (unmaintained) Drizzle JDBC driver in Fineract at run-time (not build) is sub-optimal for performance
[ https://issues.apache.org/jira/browse/FINERACT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-762: --- Labels: performance technical (was: performance) > 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, technical > > 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)
[jira] [Updated] (FINERACT-762) Use of (unmaintained) Drizzle JDBC driver in Fineract at run-time (not build) is sub-optimal for performance
[ https://issues.apache.org/jira/browse/FINERACT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-762: --- Labels: performance (was: ) > 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)
