[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: |
|
||||||||
| Template: |
|
||||||||
| Epic Name: | ES migration | ||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Story Points: | 13 | ||||||||
| Description |
|
Write ES equivalent of existing JCR queries
AC
|
| 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:
|