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
My expectation in this case would be that the document layer would do two indexed lookups and return the results, and it shouldn't need to do a table scan to accomplish this? I read through the differences and caveats but don't see this documented anywhere.
The text was updated successfully, but these errors were encountered:
I read through the code for the query planner, this is definitely just unsupported at present. Any plans to implement this? It seems like it shouldn't be that difficult, but I suspect there are things I don't understand about the underlying system.
I read through the code for the query planner, this is definitely just unsupported at present. Any plans to implement this? It seems like it shouldn't be that difficult, but I suspect there are things I don't understand about the underlying system.
It's only for "_id" field. I've fixed this issue in my fork. But I've not time for separate fix.
It's possible I'm doing something wrong, but it appears that indexes are not used when performing
$in
queries. Here's an example Mongo query:On the backend trace, this is emitted:
I verified, just to be sure, that the index exists:
My expectation in this case would be that the document layer would do two indexed lookups and return the results, and it shouldn't need to do a table scan to accomplish this? I read through the differences and caveats but don't see this documented anywhere.
The text was updated successfully, but these errors were encountered: