[ESRCH-44] [INVESTIGATION] Survey JCR queries and check whether we can translate them to semantically equivalent ES queries Created: 01/Dec/20  Updated: 03/Dec/20  Resolved: 03/Dec/20

Status: Closed
Project: External Enterprise Search
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Michael Duerig Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates ESRCH-16 ES migration Accepted
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Elastic Search

 Description   

Once the basic bits are put together and we are able to run queries against an ES index, we should run a quick validation so we are confident our approach works:

  • Gather some JCR queries that Magnolia relies on. Look out for queries against the hierarchy (isDescendantNode, etc.), full test searches against string and binary properties, ...
  • Determine how their ES counterpart would look like
  • Test the ES counterparts for equal outcome

 



 Comments   
Comment by Laura Delnevo [ 03/Dec/20 ]

Covered by ESRCH-16

Generated at Mon Feb 12 01:55:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.