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 < [email protected]> 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 [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 -~----------~----~----~----~------~----~------~--~---
