regarding compass: what about creating a task, which fetches a number of entities in batch mode and (re-)indexes them?
On 4 Dez., 11:28, Raphael André Bauer <[email protected]> wrote: > On Thu, Dec 3, 2009 at 7:25 PM, Jess Evans <[email protected]> wrote: > > The compass solution is probably sufficient for pet projects. If I > > correctly recall, there are still serious scalability issues due to the way > > indexes are currently stored and restrictions on app store blob size. The > > main issue is initial timeouts due to the GAE design flaw wrt startup / > > initial request -> timeout. Initializing compass, lucene, jdo, and serving > > even a simple request cuts very close to the deadline. > > I can confirm this. If you have a really small project you can use > Compass (both for JPA and JDO). If you have more than about 100MB to > index it will not work due to many many reasons (tested that 3 weeks > ago). > > So you have to come up with your own solution to this... > > ra! -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
