+ - The query planner picked the best-matching index per field independently while scanning candidate indexes, but accumulated filters from every candidate it visited into one shared set instead of keeping only the winning index's filters. The resulting index scan filter set could carry filters from two unrelated indexes (e.g. a `String`-valued `eq` filter alongside a `Long`-valued range pair), which were then all applied against whichever single index the planner picked, comparing a value of the wrong type against that index's keys.
0 commit comments