[MGNLDAM-267] Prevent adjustments of JCR index for DAM mgnl:assets Created: 17/Jun/13  Updated: 25/Jun/13  Resolved: 25/Jun/13

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.0.1

Type: Improvement Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSTK-1186 Fix/adapt component stkDownloadList Closed
supersession
supersedes MGNLDAM-273 Adapt JCR indexing for DAM mgnl:assets Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes

 Description   

Changes to DAM consist of moving some information from the main node to the jcr:content (nt:resource) subnode (e.g. extension).
To be able to query these information, we should update queries to use JCR_SQL2 JOIN statements rather than updating the JCR index.

Update JcrAssetProvider:

  • getAssetsForFilter should use JOIN statment, so no index update is required
  • extract SQL statement creation to separate function (for better testing)

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