[google-appengine] Re: 30 second request limit - a killer?
Your link to the Compass forum is broken for me. Not that I know anything really about Compass, anyways. You will have to figure out a way to rebuild the indexes incrementally. I would suggest looking at the new Task Queue api. It seems appropriate for something like this -- rebuild a bit of the indexes, then post a new task to rebuild some more, etc. On Jun 19, 10:57 pm, Dominik Steiner wrote: > Hi there, > > I have made my first steps with GAE on Java and it had been a pleasure > to develop with the eclipse plugin for GWT and GAE. As the JDO query > implementation of GAE is quite reduced, I used the Compass framework > to work around that and it looked like it could get my app going. > > But as you can read in the following forum post > > http://forum.compass-project.org/thread.jspa?messageID=298249 > > I have run into problems that my data in the GAE database and the > Compass cache is running out of sync. The solution from Compass side > to trigger an indexing of the Compass cache is failing because that > operation is taking more than 30 seconds and thus is throwing an > error. > > So my questions are: have others run into the same problem and could > fix it? what would be a workaround of the 30 second limit? > > I really would love to see my app running on GAE, but right now that > problem is killing it. > > Anybody with some hints or ideas? > > Thanks > > Dominik --~--~-~--~~~---~--~~ 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-appengine@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 -~--~~~~--~~--~--~---
[google-appengine] Re: 30 second request limit - a killer?
Thanks Charlie for the fast reply, here is the link to the Compass forum post http://forum.compass-project.org/forum.jspa?forumID=37 I will have a look in the Task Queue Api and write back to that forum if it helped. Dominik P.S. just to clarify, with Task Queue you mean the java.util.TaskQueue class? On 20 Jun., 05:08, Charlie wrote: > Your link to the Compass forum is broken for me. Not that I know > anything really about Compass, anyways. > > You will have to figure out a way to rebuild the indexes > incrementally. > > I would suggest looking at the new Task Queue api. It seems > appropriate for something like this -- rebuild a bit of the indexes, > then post a new task to rebuild some more, etc. > > On Jun 19, 10:57 pm, Dominik Steiner > > wrote: > > Hi there, > > > I have made my first steps with GAE on Java and it had been a pleasure > > to develop with the eclipse plugin for GWT and GAE. As the JDO query > > implementation of GAE is quite reduced, I used the Compass framework > > to work around that and it looked like it could get my app going. > > > But as you can read in the following forum post > > >http://forum.compass-project.org/thread.jspa?messageID=298249 > > > I have run into problems that my data in the GAE database and the > > Compass cache is running out of sync. The solution from Compass side > > to trigger an indexing of the Compass cache is failing because that > > operation is taking more than 30 seconds and thus is throwing an > > error. > > > So my questions are: have others run into the same problem and could > > fix it? what would be a workaround of the 30 second limit? > > > I really would love to see my app running on GAE, but right now that > > problem is killing it. > > > Anybody with some hints or ideas? > > > Thanks > > > Dominik --~--~-~--~~~---~--~~ 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-appengine@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 -~--~~~~--~~--~--~---
[google-appengine] Re: 30 second request limit - a killer?
I think Charlie is referring to the newly released Task Queue API: http://googleappengine.blogspot.com/2009/06/new-task-queue-api-on-google-app-engine.html Unfortunately for you, this is Python only at the moment. I would think you will see it in the Java version soon. On Jun 20, 3:56 pm, Dominik Steiner wrote: > Thanks Charlie for the fast reply, > > here is the link to the Compass forum post > > http://forum.compass-project.org/forum.jspa?forumID=37 > > I will have a look in the Task Queue Api and write back to that forum > if it helped. > > Dominik > > P.S. just to clarify, with Task Queue you mean the java.util.TaskQueue > class? > > On 20 Jun., 05:08, Charlie wrote: > > > > > Your link to the Compass forum is broken for me. Not that I know > > anything really about Compass, anyways. > > > You will have to figure out a way to rebuild the indexes > > incrementally. > > > I would suggest looking at the new Task Queue api. It seems > > appropriate for something like this -- rebuild a bit of the indexes, > > then post a new task to rebuild some more, etc. > > > On Jun 19, 10:57 pm, Dominik Steiner > > > wrote: > > > Hi there, > > > > I have made my first steps with GAE on Java and it had been a pleasure > > > to develop with the eclipse plugin for GWT and GAE. As the JDO query > > > implementation of GAE is quite reduced, I used the Compass framework > > > to work around that and it looked like it could get my app going. > > > > But as you can read in the following forum post > > > >http://forum.compass-project.org/thread.jspa?messageID=298249 > > > > I have run into problems that my data in the GAE database and the > > > Compass cache is running out of sync. The solution from Compass side > > > to trigger an indexing of the Compass cache is failing because that > > > operation is taking more than 30 seconds and thus is throwing an > > > error. > > > > So my questions are: have others run into the same problem and could > > > fix it? what would be a workaround of the 30 second limit? > > > > I really would love to see my app running on GAE, but right now that > > > problem is killing it. > > > > Anybody with some hints or ideas? > > > > Thanks > > > > Dominik --~--~-~--~~~---~--~~ 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-appengine@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 -~--~~~~--~~--~--~---
[google-appengine] Re: 30 second request limit - a killer?
Oops. Indeed, that is what I meant. I forgot it wasn't out for Java, yet. Shouldn't be long, though, is the back end is entirely language independent. On Jun 20, 6:28 pm, gadgster wrote: > I think Charlie is referring to the newly released Task Queue API: > > http://googleappengine.blogspot.com/2009/06/new-task-queue-api-on-goo... > > Unfortunately for you, this is Python only at the moment. I would > think you will see it in the Java version soon. > > On Jun 20, 3:56 pm, Dominik Steiner > wrote: > > > Thanks Charlie for the fast reply, > > > here is the link to the Compass forum post > > >http://forum.compass-project.org/forum.jspa?forumID=37 > > > I will have a look in the Task Queue Api and write back to that forum > > if it helped. > > > Dominik > > > P.S. just to clarify, with Task Queue you mean the java.util.TaskQueue > > class? > > > On 20 Jun., 05:08, Charlie wrote: > > > > Your link to the Compass forum is broken for me. Not that I know > > > anything really about Compass, anyways. > > > > You will have to figure out a way to rebuild the indexes > > > incrementally. > > > > I would suggest looking at the new Task Queue api. It seems > > > appropriate for something like this -- rebuild a bit of the indexes, > > > then post a new task to rebuild some more, etc. > > > > On Jun 19, 10:57 pm, Dominik Steiner > > > > wrote: > > > > Hi there, > > > > > I have made my first steps with GAE on Java and it had been a pleasure > > > > to develop with the eclipse plugin for GWT and GAE. As the JDO query > > > > implementation of GAE is quite reduced, I used the Compass framework > > > > to work around that and it looked like it could get my app going. > > > > > But as you can read in the following forum post > > > > >http://forum.compass-project.org/thread.jspa?messageID=298249 > > > > > I have run into problems that my data in the GAE database and the > > > > Compass cache is running out of sync. The solution from Compass side > > > > to trigger an indexing of the Compass cache is failing because that > > > > operation is taking more than 30 seconds and thus is throwing an > > > > error. > > > > > So my questions are: have others run into the same problem and could > > > > fix it? what would be a workaround of the 30 second limit? > > > > > I really would love to see my app running on GAE, but right now that > > > > problem is killing it. > > > > > Anybody with some hints or ideas? > > > > > Thanks > > > > > Dominik --~--~-~--~~~---~--~~ 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-appengine@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 -~--~~~~--~~--~--~---
[google-appengine] Re: 30 second request limit - a killer?
Hi Dominik, As I undestand it, the Compass support for App Engine currently stores the entire index in local instance memory, which makes it impractical for use in a production environment. As such, you're going to have to rebuild your index for every new runtime instance, which simply isn't practical. -Nick Johnson On Sat, Jun 20, 2009 at 3:57 AM, Dominik Steiner < dominik.j.stei...@googlemail.com> wrote: > > Hi there, > > I have made my first steps with GAE on Java and it had been a pleasure > to develop with the eclipse plugin for GWT and GAE. As the JDO query > implementation of GAE is quite reduced, I used the Compass framework > to work around that and it looked like it could get my app going. > > But as you can read in the following forum post > > http://forum.compass-project.org/thread.jspa?messageID=298249 > > I have run into problems that my data in the GAE database and the > Compass cache is running out of sync. The solution from Compass side > to trigger an indexing of the Compass cache is failing because that > operation is taking more than 30 seconds and thus is throwing an > error. > > So my questions are: have others run into the same problem and could > fix it? what would be a workaround of the 30 second limit? > > I really would love to see my app running on GAE, but right now that > problem is killing it. > > Anybody with some hints or ideas? > > Thanks > > Dominik > > > -- Nick Johnson, App Engine Developer Programs Engineer Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 --~--~-~--~~~---~--~~ 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-appengine@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 -~--~~~~--~~--~--~---
[google-appengine] Re: 30 second request limit - a killer?
Thanks for all your responses, the reason why I'm using Compass is because the JDO implementation of GAE is not allowing to use "LIKE" or "OR" which makes it difficult to make searching data user friendly and efficient. Or are there other alternatives to Compass which make querying the data on GAE easier? Thanks Dominik On 22 Jun., 03:51, "Nick Johnson (Google)" wrote: > Hi Dominik, > > As I undestand it, the Compass support for App Engine currently stores the > entire index in local instance memory, which makes it impractical for use in > a production environment. As such, you're going to have to rebuild your > index for every new runtime instance, which simply isn't practical. > > -Nick Johnson > > On Sat, Jun 20, 2009 at 3:57 AM, Dominik Steiner < > > > > dominik.j.stei...@googlemail.com> wrote: > > > Hi there, > > > I have made my first steps with GAE on Java and it had been a pleasure > > to develop with the eclipse plugin for GWT and GAE. As the JDO query > > implementation of GAE is quite reduced, I used the Compass framework > > to work around that and it looked like it could get my app going. > > > But as you can read in the following forum post > > >http://forum.compass-project.org/thread.jspa?messageID=298249 > > > I have run into problems that my data in the GAE database and the > > Compass cache is running out of sync. The solution from Compass side > > to trigger an indexing of the Compass cache is failing because that > > operation is taking more than 30 seconds and thus is throwing an > > error. > > > So my questions are: have others run into the same problem and could > > fix it? what would be a workaround of the 30 second limit? > > > I really would love to see my app running on GAE, but right now that > > problem is killing it. > > > Anybody with some hints or ideas? > > > Thanks > > > Dominik > > -- > Nick Johnson, App Engine Developer Programs Engineer > Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: > 368047 --~--~-~--~~~---~--~~ 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-appengine@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 -~--~~~~--~~--~--~---
