Re: [appengine-java] Mutation pool bug?

2011-01-18 Thread Stephen Johnson
e: > Thank you, Stephen. This works. I could not locate this earlier in the > mapreduce documentation. > > Regards, > Arun > > -- > *From:* Stephen Johnson > *To:* google-appengine-java@googlegroups.com > *Sent:* Sun, 16 January, 2011 1:33:31

Re: [appengine-java] Mutation pool bug?

2011-01-18 Thread Arun Ramanujapuram
Thank you, Stephen. This works. I could not locate this earlier in the mapreduce documentation. Regards, Arun From: Stephen Johnson To: google-appengine-java@googlegroups.com Sent: Sun, 16 January, 2011 1:33:31 AM Subject: Re: [appengine-java] Mutation pool

Re: [appengine-java] Mutation pool bug?

2011-01-15 Thread Stephen Johnson
Do you have this defined in your mapper class? @Override public void taskCleanup(Context context) { try { // make sure to call super classes taskCleanup so that the DatastoreMutationPool // gets flushed properly otherwise puts/deletes can be lost; super.taskCleanup(context); } catch (Excepti

[appengine-java] Mutation pool bug?

2011-01-14 Thread armanuj
Hi, I had earlier posted an issue such as "out of mapper quota" earlier (link below). I had about 260 entities being mapped (for a start), and not entities were getting updated. I was using the mutation pool for updates in the map routine. On further investigations, it appears that the mutation po