summaryrefslogtreecommitdiffstats
path: root/feature-distributed-locking/src/main/feature/db
AgeCommit message (Collapse)AuthorFilesLines
2022-10-19Support optional cluster name in policy enginejhh2-8/+15
This allows also for correlation with running pod hostnames in the case of multiple drools pdp flavors coexist. Issue-ID: POLICY-4403 Signed-off-by: jhh <jorge.hernandez-herrero@att.com> Change-Id: I81affeeec622e6c0e9627651bf34c0775a796827 Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
2022-08-24made lock sql compatible with both mysql/mariadbjhh1-2/+2
Issue-ID: POLICY-4329 Signed-off-by: jhh <jorge.hernandez-herrero@att.com> Change-Id: I784a3f8456a201262056803169204d499a4a68a2 Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
2021-03-04Fix default timestamp in upgrade scriptJim Hahn2-10/+10
The 1811 upgrade script for distributed locking is failing, because the default timestamp value is invalid for the new column type. Modified the value and also added one for the downgrade script. Issue-ID: POLICY-3117 Change-Id: I8dff748cb089db551820418b1d597a1be207c9b5 Signed-off-by: Jim Hahn <jrh3@att.com>
2018-06-29Use DB time instead of jvm timeJim Hahn2-0/+42
Modified distributed locking code to use the DB time (i.e., "now()") when determining expiration times of locks. This will eliminate concerns that may arise from different timestamps on different JVMs. As part of the change, the expirationTime column was changed from BIGINT to TIMESTAMP. Rename 1810 sql scripts to 1811, to match release date. Change-Id: Ibfb15742f447133b001e4340027657ac202864a6 Issue-ID: POLICY-872 Signed-off-by: Jim Hahn <jrh3@att.com>
2018-04-03Implementation of distributed locking featureMagnusen, Drew (dm741q)2-0/+43
This feature is a very basic implementation of a distributed locking system. Issue-ID: POLICY-699 Change-Id: I012fd37926ccbbdd87a3e4acb2788b53680115f0 Signed-off-by: Magnusen, Drew (dm741q) <dm741q@att.com>