hello maybe you should try 11 parts so each would be below the max 1MB api limit. You definitely need separate entities for each part
I use this technique right now to store large images and it does work. In the future, if Google adds a BlobStore api for manipulating large files from your app code, you could switch over to that. until then, you'll need to split them up or use an external service like S3 (although the 1MB limit on urlfetch makes this very difficult as well) cheers brian On Mar 10, 2:51 am, Adhi <adhi.ramanat...@orangescape.com> wrote: > Hi Barry, > Thanks for your reply. I tried in 2 ways > > Split the data into 10 parts and > 1. Created separate entity for each part (as you told) > 2. In a single entity with 10 dynamic properties (since its not always > 10 parts might be less for some cases) > > In both ways I'm getting "RequestTooLargeError: The request to API > call datastore_v3.Put() was too large." > when I try to put the entity(s) in a single db.put(). > > So do I've to use separate db.put for each entity? > > Thankyou > Adhi > > On Mar 2, 6:45 pm, Barry Hunter <barrybhun...@googlemail.com> wrote: > > > > > > Is it possible to increase thelimitforblobpropertysize upto 10 MB? > > > no. > > > Split the Blob and store in 10 Separate entities. -- 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-appeng...@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.
