One of my end points need to handle storing over 1-5000 entities belonging to a single EG. This needs to happen atomically such that in case of error everything is reverted to the orignal state.
The problem I'm running into is occasional "datastore transaction or write too big." exception. Since all my entities are small in size, I assume I'm hitting the entity limit of 500 per commit (though at times I'm able to store 900 at once). Splitting the save statement into batches, but within the same transaction doesn't seem to help. What is the best practice to handle that limit? Are transactions out of the question in this scenario? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/490239f1-35a7-4806-bb41-659b236e9e89%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
