Description
The built-in search UI does not return the full array when matched, only the first one or so. Or at least that is what it seems like - it's a bit of a complex object to display, e.g. trying to match reviews.content:
"reviews": [{
"author": "Miss Kaia Nicolas",
"content": "Great People..."},{...}]
If the matched term is later in the array, then highlighting cannot be done properly. So it highlights the wrong term. Or at least that is what I think might be happening, not 100% sure.
For example see travel-sample bucket, type:hotels
query string search for:
reviews.content=worst
Document hotel_16045 shows as a match
UI shows:
reviews.content
- …wn to the beach early to get one. There is a shopping area not too far down the beach. You must bargain with them or you will pay too much. My husband bought me a charm for my bracelet and the guy sta…
Now when I goto look at hotel_16045 I can't even find a match to "worst" anyway, so more confused now. I expect this is more of an array indexing problem, perhaps?
Attachments
For Gerrit Dashboard: MB-29654 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
94165,3 | bump up bleve SHA to the latest on vulcan, alice & master manifests | master | manifest | Status: MERGED | +2 | +1 |