Details
-
Task
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
-
Core: F - Sprint 65
-
3
-
Prokopovych
Description
This is a temporary workaround for Q2 util RMB-385 is implemented (which is slated for mid-Q3).
1. given a search query that consists of a list of terms a b c d
2. the UI tokenises the query into individual tokens a, b, c, d
3. and creates a query expression with all possible combination for all indices searches, e.g assuming three indices: index1, index2, index3 the query generated is
(index1="a" OR index2="a" OR index3="a") AND (index1="b" OR index2 = "b" OR index3="b") AND ...
There is couple problems and limitations to this workaround, they are listed on RMB-385.
The ticket is for implementation in the ui-users, a similar approach may be also rolled out to inventory (to be verified with cboerema and charlotte)
TestRail: Results
Attachments
Issue Links
- blocks
-
UIU-939 Basic Search: Can't Find User by First and Last Name
-
- Closed
-
- duplicates
-
UIU-974 SPIKE: Solution for UIU-939 (Can't Find User by First and Last Name)
-
- Closed
-
- relates to
-
UIIN-602 no records found when searching titles for words out of order.
-
- Closed
-
-
RMB-385 add 'queryIndexName' to schema.json and allow compound indexes
-
- Closed
-
-
UXPROD-1941 Wait for POC of Elastic Search. Front-end query pre-processor: support words, phrases and booleans
-
- Draft
-