$in operator fails on array fields about mongita HOT 6 CLOSED

Just acknowledging that I have seen this. I looked over the code and did some quick tests and it looks like I missed implementing the second part of $in functionality that you mention. That certainly needs to get fixed.

What I could not do was reproduce your TypeError which is a little more concerning to me. Do you have any example documents that will cause that to trigger? Are you using memory or disk?

from mongita.

Candidate patch to address $in/$nin behavior - https://github.com/scottrogowski/mongita/pull/21/files

Would still be curious if you have a way to reproduce the TypeError

from mongita.

@scottrogowski Sorry, my $in parameter was a set. I edited the traceback incorrectly. It should look like this.

result = list(col.find({"names: {"$in": {"asd", "qwe"}}}))

from mongita.

Ah, you had me worried there. PyMongo throws an error when you use sets as well. The difference is that it's a bson.errors.InvalidDocument rather than a TypeError. So while I think I'll try to reproduce that exact error, I'm not as worried.

Regardless, you helped me find something I had overlooked with the $in/$nin operators... so thank you.

from mongita.

Yes sorry I didn't test the code with pymongo. I noticed that sets did work with the standard (non-array field) $in operator so I just extended the code to the array field version and saw the error.

from mongita.

Addressed the $in/$nin with V1.1. I'll set aside document validation for sets for the moment in favor of a larger release later.

from mongita.