On 18 Sep., 10:14, ryan <[EMAIL PROTECTED]> wrote: > merge join is unrelated to list properties. it's a way to support > multiple = filters without dedicated indexes. in a nutshell, multiple > index segments are scanned in parallel and intersected. to fetch a > result, each scan skips ahead to the key found by the previous scan, > and so on. this avoids full table scans, which as you mention, don't > scale.
Sorry, it's still not 100% clear to me. :( If merge-join isn't used for multiple = filters on list properties (that's what I understood) then how does the datastore perform such a search and what does the index look like? Unfortunately, the "Under the Covers ..." video doesn't explain list properties and it would be nice to know a few more details. Thanks! Bye, Waldemar Kornewald --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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 -~----------~----~----~----~------~----~------~--~---
