You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug is hitting ln 661 and then 689 in indexer_iterators.go, func IndexFetcher.determineFieldFilterConditions(). That function does not appear to have been written with compound operators in mind. In the above test case ln 659 is hit, but ln 663 is not.
The text was updated successfully, but these errors were encountered:
## Relevant issue(s)
Resolves#2572
## Description
Handles compound filters targeting related indexed fields, and one-many
joins from the many side.
The invertableJoin issue may be affecting non indexed joins.
There is another issue in this space not solved by this PR:
#2574
Querying with a compound (and/or) filter targeting related indexed field errors.
_and
or_or
, omitting the compound operator does not result in an error._ilike
,_eq
, etc) does not appear to matter.For example:
Bug is hitting ln 661 and then 689 in
indexer_iterators.go
, funcIndexFetcher.determineFieldFilterConditions()
. That function does not appear to have been written with compound operators in mind. In the above test case ln 659 is hit, but ln 663 is not.The text was updated successfully, but these errors were encountered: