following schema refs causes ambiguous field names in indexes
Description
Environment
None
Potential Workaround
None
is blocked by
relates to
Checklist
hideTestRail: Results
Activity
Show:
Adam Dickmeiss October 12, 2018 at 12:04 PM
Cannot fix.. But see
Heikki Levanto October 12, 2018 at 11:10 AM
mod-users used to have a problem reading the schema, which caused a different problem with numerical-looking usernames being transformed into a numerical query, which didn't work. Julian pushed a fix for that yesterday, which explains why this surfaced now.
We should always require exact paths in searches, and not to try resolve partially specified names at all!
Won't Do
Details
Details
Assignee
Unassigned
UnassignedReporter
Zak BurkePriority
P2TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created October 12, 2018 at 11:03 AM
Updated October 12, 2018 at 9:50 PM
Resolved October 12, 2018 at 12:04 PM
TestRail: Cases
TestRail: Runs
Description
Queries against a schema such as mod-users' userdata.json that contain nested fields with the same name (lines 11 and 86) generate errors. This may be the result of recent work for CQLPG-60 (#77) and/or MODUSERS-90 (#86).
Steps to reproduce
On folio-testing, search for a user by entering any string in the "Search" field.
Expected behavior
Searching for a user succeeds without error.
Actual behavior
Searching for a user generates an alert box with an error from Okapi: