Yes, you are correct and those indexes will work. It's a trade of, composite indexes 'pre-intersect' (at write time) properties while zigzag merge join 'post-intersects' properties (at read time). I left the ancestor in because it is probably very 'selective' which has the potential to greatly reduce the amount of data that needs intersected at read time (though this is very data dependent).
On Thu, Jul 14, 2011 at 11:35 AM, PK <p...@gae123.com> wrote: > Alfred thanks for the clarification. > > However, isn't ancestor a list too that could contribute to an explosion > (albeit minor assuming shallow hierarchies). If this is the case, would > these indexes help/work? > > - kind: Model > ancestor: yes > properties: > - name: int > - name: date > direction: desc > - kind: Model > properties: > - name: list1 > - name: int > - name: date > direction: desc > - kind: Model > properties: > - name: list2 > - name: int > - name: date > direction: desc > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "google-appengine-python" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-python/-/aQh0Xx49xlsJ. > To post to this group, send email to > google-appengine-pyt...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-python+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-python?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
