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
## Relevant issue(s)
Resolves#490Resolves#1582 (indirectly)
## Description
This is a reduced version of #491. It takes a very different approach,
and tries to keep as much of the existing Fetcher structure as possible.
Basically, this will try to eagerly ignore documents that don't pass the
given filter at the fetcher level. This means we can apply various
optimizations then if the filter was applied at the scanNode level like
before.
## Relevant issue(s)
Resolvessourcenetwork#490Resolvessourcenetwork#1582 (indirectly)
## Description
This is a reduced version of sourcenetwork#491. It takes a very different approach,
and tries to keep as much of the existing Fetcher structure as possible.
Basically, this will try to eagerly ignore documents that don't pass the
given filter at the fetcher level. This means we can apply various
optimizations then if the filter was applied at the scanNode level like
before.
When we query with a
groupBy
, thegroupBy
item is returned in the result set even though it wasn't explicitly requested. This goes agains the graphql specs that states that the shape of the response must match that of the request. https://spec.graphql.org/October2021/#sec-Language.Fields, https://spec.graphql.org/October2021/#sec-Overviewreturns
but should return
The text was updated successfully, but these errors were encountered: