Ok, I see what you mean. The same issue then also exists in the `nested` query and filter, since it uses a similar mechanism to resolve the actual parent filter later on in the query execution.