[MAGNOLIA-8185] Extract path lock mechanism from publishing modules into core Created: 16/Sep/21  Updated: 21/Sep/21  Resolved: 21/Sep/21

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.12

Type: Improvement Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Done Votes: 0
Labels: headless-team-support, maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by PUBLISHING-125 Conflicts between publishing and auto... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Sprint: HL & LD 37
Story Points: 3

 Description   

Due to migrating away from JCR Locks in publication, a concurrency issue was revealed where auto generated content might under some circumstances conflict with content being imported during publication process.

Since we made path locks in publishing JCR-agonostic, the PathLockManager does not know that there's content being autogenerated, and so it allows publication module to import the content even though there's JCR lock in place.

This improvements aims for extraction of path locks from publishing module into core, so that it is possible to replace JCR locks and prevent concurrency issues when modifying same content.


Generated at Mon Feb 12 04:30:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.