[ESRCH-16] ES migration Created: 11/Sep/20  Updated: 04/Feb/21

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

Type: Epic Priority: Neutral
Reporter: Laura Delnevo Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by ESRCH-44 [INVESTIGATION] Survey JCR queries an... Closed
Template:
Epic Name: ES migration
Acceptance criteria:
Empty
Date of First Response:
Story Points: 13

 Description   

Write ES equivalent of existing JCR queries

 

AC

  • Replace all the existing JCR queries with their ES counterparts (if ES is installed)


 Comments   
Comment by Michael Duerig [ 26/Nov/20 ]

We could abstract this as a query translation service. Its most basic implementation would just be a map from (known) JCR queries to their ES counterpart. Failed lookups would then also cover ESRCH-36 by means of collecting queries that lack ES counterparts.

Comment by Laura Delnevo [ 03/Dec/20 ]

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
Generated at Mon Feb 12 01:55:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.