Hi, The first release of the mapper API will require a manual invocation of the task.
If you need to map all entities, you will have to run the task. There's no continuous process monitoring changed entities. You can probably build this into your update workflow. On Wed, May 26, 2010 at 1:29 AM, Waldemar Kornewald <[email protected]>wrote: > Hi, > looking at the screenshots of the mapreduce library > http://code.google.com/p/appengine-mapreduce/ > gives me the impression that I'll have to manually execute those > mapreduce tasks. Will this change in the final release? > > Also, will I always have to periodically rerun the mapreduce task over > the *whole* DB even if just a single entity has changed? Or will there > be some CouchDB-like mapreduce tasks which run continuously in the > background and react to DB changes such that only a subset of the DB > needs to be recomputed? > > 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]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine -- 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.
