<https://lh3.googleusercontent.com/pcMTiy_-SDxzfHNk178ORXaVoPB0GzQ6eoAGZ4nFsBLUqZi0XNCzFWLKx0xcttb6mA=s1600> Ouch ouch, it's even worse than expected. I ran an query with an IN filter with the same value repeated. eg IN[0,0,0,0,0,0,0,0,0,0,0] - The query runs completely in serial doing an independent query for each of the 0s. You are charged for the same entity returned multiple times, and the entity is returned to you multiple times even though it's obviously the same entity.
The IN filter should definitely be marked as deprecated in the SDK docs, and there should be a large warning against using it - it is ALWAYS better to use the async datastore to create multiple queries with an EQUALs filter - it will cost exactly the same, return the same data, and be far faster as it runs in parallel. The whole IN filter seems like a "user trap" on Google's part - at the minimum, the IN query should be changed to run in parallel! -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/kJ4oHDPjEPoJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
