It's best to just write your data directly to the datastore. Jeff
On Fri, Apr 27, 2012 at 3:24 PM, Deepak Singh <[email protected]> wrote: > Thanks Jeff. > yes i am in learning stage now. > Will it be better to use the url based task options instead of DeferredTask > for this scenario ? > > > On Sat, Apr 28, 2012 at 12:40 AM, Jeff Schnitzer <[email protected]> > wrote: >> >> You cannot. You could stash the data in memcache, but at the risk the >> data will disappear before your task executes. >> >> This sounds like premature optimization. You're still in the learning >> stage. Start by writing the simplest program that could possibly >> work, then figure out how to optimize it later. >> >> Jeff >> >> On Fri, Apr 27, 2012 at 2:46 PM, Deepak Singh <[email protected]> >> wrote: >> > But my objective to use the task is only to insert the file in >> > datastore. >> > its an uploaded file by user. >> > >> > I want to put this operation in task to just make the instance free and >> > insertion should happen in background. >> > >> > >> > On Fri, Apr 27, 2012 at 5:49 PM, Dale Humby <[email protected]> wrote: >> >> >> >> Passing the contents of a file around within a task is not really >> >> correct. >> >> Rather store the file in the blobstore (or the datastore) first and >> >> then >> >> pass a reference to the location of the file as a parameter to the >> >> task. >> >> >> >> >> >> >> >> >> >> >> >> On Thursday, April 26, 2012 11:37:06 PM UTC+2, Deepak Singh wrote: >> >>> >> >>> Hi, >> >>> >> >>> I have a deferred task and am doing database insertion in task queue >> >>> defined as below, >> >>> >> >>> <queue> >> >>> <name>dbinsert</name> >> >>> <rate>20/s</rate> >> >>> <bucket-size>100</bucket-size> >> >>> <max-concurrent-requests>10</max-concurrent-requests> >> >>> <retry-parameters> >> >>> <task-retry-limit>7</task-retry-limit> >> >>> </retry-parameters> >> >>> </queue> >> >>> >> >>> >> >>> Since i am uploading files in task, most often i get the exception >> >>> "Task >> >>> size too large". >> >>> >> >>> What can i do to avoid this ? >> >>> >> >>> >> >>> >> >>> thanks >> >>> Deepak Singh >> >> >> >> -- >> >> 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/-/bP6mraNokV0J. >> >> 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. >> > >> > >> > >> > >> > -- >> > Deepak Singh >> > >> > -- >> > 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. >> >> -- >> 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. >> > > > > -- > Deepak Singh > > -- > 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. -- 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.
