[
https://issues.apache.org/jira/browse/ARTEMIS-4205?focusedWorklogId=851415&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-851415
]
ASF GitHub Bot logged work on ARTEMIS-4205:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Mar/23 19:26
Start Date: 16/Mar/23 19:26
Worklog Time Spent: 10m
Work Description: funkyjive commented on PR #4403:
URL:
https://github.com/apache/activemq-artemis/pull/4403#issuecomment-1472621570
>
I took a look through that code for the artemis-jdbc-store. I think the
problem being solved, the reasoning and the approach around the locking
structure is very different from my approach. The approach I am taking is to
use a uniquely implemented database feature on a per-database basis which
provides the logical locking required without much of the accompanying overhead
in the form of tables and records.
Issue Time Tracking
-------------------
Worklog Id: (was: 851415)
Time Spent: 1h (was: 50m)
> Allow a database to be used to meet pluggable quorum vote locking requirements
> ------------------------------------------------------------------------------
>
> Key: ARTEMIS-4205
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4205
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Reporter: David Bennion
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Utilizing the new pluggable quorum vote locking api, implement the locking
> manager using a JDBC database connection. Support for Oracle, MSSQL and
> Postgres is included initially, with H2 being utilized for unit testing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
