Thats what I am trying to find, "a work around", otherwise we can
never have instantly deployable opensource applications on Google
AppEngine, which most intermediate level users on the web demand.
On Jul 21, 9:01 pm, Darien Caldwell wrote:
> It's not a 'problem' per se, it's simply how the syste
It's not a 'problem' per se, it's simply how the system works. There's
a queue for indexes to be built, and depending on if the queue is long
or short when your index is added, the time you wait will be long or
short. Unless Google radically changes their approach to index
building, there will alw
Yeah, that does not work because the query is not executed in the try block,
hence it does not raise an exception. Try adding a .fetch(500) after order()
and see if that stops the exception.
Also check out Andrew Fuller's 2010 next gen query IO talk. Once that gets
implemented maybe you'll be a
This still doesn't solve my problem. Its not a one time project I am
trying to build. Had it been a single one time project I am ok with
the delay. I am trying to create generic product which anyone should
be able to use. But delay due to index creation will give a lot of
problem to the end user. S
Check this tip by Ikai Lan:
http://ikaisays.com/2010/07/12/google-app-engine-tips-and-tricks-prebuilding-indexes-using-a-non-default-version/
On Jul 21, 11:40 am, GeekTantra wrote:
> I am trying to segregate the queries that require indexes by using a
> try except block like following
>
> try:
I am trying to segregate the queries that require indexes by using a
try except block like following
try:
posts_list =
posts.Post.objects.all().filter(post_status__in=post_status).order_by('-
created')
except:
the_posts_list = posts.Post.objects.all()
posts_list = [ p for p in the_
I do not know of any way to monitor index build times currently.
For me building new indexes is usually fast. Typically under 30 minutes. But I
built one today that took 6 hours on a kind with 220 entities. :/
Robert
On Jul 21, 2010, at 3:09, GeekTantra wrote:
> Thanks a lot for your res
Thanks a lot for your response.
I just wanted to know whether this will be a perennial or just a
temporary problem? And any way of monitoring the index servers
something similar to http://code.google.com/status/
I need to know this because I want to launch my Open Source product
and don't want to
The above post contains the manually configured indexes from my
index.yaml. But as I said earlier its not configuring the indexes that
I am facing problem with but its the time it takes to start serving
the index even in an empty datastore thats causing the problem in
instantly deploying my applica
