If you mean a custom composit index (ie via index.yaml) - then I believe there is a sequential processing queue.
The delay is as much about how many tasks (and their size!) are in the queue, rather than the size of your new index. Unless its stuck in some sort of error state - check your logs. In which case might need to do some vacuuming On Fri, Feb 10, 2012 at 6:30 PM, Christian Goudreau <queen...@arcbees.com> wrote: > Hi Everyone, > > Why my indexes takes forever to build while there's only two object? And two > field? > > -- > 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/-/uQ7fzt6wy6IJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
