[google-appengine] Re: Indexes

Would be great to hear from the App Engine Team about this. It seems like one area that has never had any attention. Work could be done to: 1. Speed this process up or at least inform the user of the ETA 2. Explain why an index goes into error, or better yet just never let them be in error 3. Al

[google-appengine] Re: Indexes Error

Yes now my indexes is RE in deletion, my application is down, please you have the opportunity to expedite things I have billing enable and i use about 60$ per days. On 8 oct, 20:46, "Ikai Lan (Google)" wrote: > Did you run vacuum_indexes  on your indexes? > > -- > Ikai Lan > Developer Programs

[google-appengine] Re: Indexes Error

UP my indexes are always in deletion: Queued: 130 Running: 0 Completed: 47 Total: 177 Never way to get a better time?, because i need also to make all new indexes. Cordialy, Sahid On Oct 8, 9:15 pm, sahid wrote: > Yes now my indexes is RE in deletion, my application is down, please > you have

Re: [google-appengine] Re: Indexes

I also dislike the current workflow. At the minimum it could easily be made less painful for the users. I submitted a ticket with one proposed improvement. http://code.google.com/p/googleappengine/issues/detail?id=6573 Robert On Fri, Feb 10, 2012 at 20:58, Mike Wesner wrote: > Would be

Re: [google-appengine] Re: Indexes

Hi everyone, We have a project underway to rebuild our index-building pipeline from the ground up. It's going well, and we're in the process of rolling it out to a limited number of applications to make sure it's working the way we expect it to. The new pipeline should be fairer and less error

[google-appengine] Re: Indexes Stucked

I forgot to tell: there is only one UserRoles on db, so 30 minutes to build a index is too much. Segunda-feira, 28 de Janeiro de 2013 18:35:42 UTC-2, Renzo Nuccitelli escreveu: > > Application: qmaghomolog > Index: UserRoles > > It stucked on Building Indexes. I hava already run a vacuum_i

[google-appengine] Re: Indexes Stuck

Hi pdub, I've moved these indexes to the error state so it should now be possible to vacuum then and reupload. Happy coding, Jeff On Sep 17, 6:19 pm, pdub wrote: > appid: bidtective > > Hello, > > My indexes seem to have gotten stuck building.  I don't actually have > any data in my datastore

[google-appengine] Re: Indexes Stuck

Thanks, that did it. Cheers, On Sep 18, 12:01 pm, "Jeff S (Google)" wrote: > Hi pdub, > > I've moved these indexes to the error state so it should now be > possible to vacuum then and reupload. > > Happy coding, > > Jeff > > On Sep 17, 6:19 pm, pdub wrote: > > > appid: bidtective > > > Hello,

[google-appengine] Re: Indexes Stuck

I seem to be having the same problem (waiting on an index on a new entity type for ~19 hours). My application's name is "twitter-sync". Thank you! Adam On Sep 20, 8:34 am, pdub wrote: > Thanks, that did it. > > Cheers, > > On Sep 18, 12:01 pm, "Jeff S (Google)" wrote: > > > Hi pdub, > > > I've

[google-appengine] Re: Indexes Stuck

The admin console is reporting them as "serving" now. So, I should be good to go. On Sep 20, 10:07 am, Adam Loving wrote: > I seem to be having the same problem (waiting on an index on a new > entity type for ~19 hours). My application's name is "twitter-sync". > > Thank you! > Adam > > On Sep 2

Re: [google-appengine] Re: Indexes Error

My indexes are always in errors! i have vaccum indexes, after indexes are deleted i have RE update my indexes, but i have always indexes error! That is terrible, my application is down, who is the support? i use about 60$ per days... --   .  ..: On Fri, Oct 8, 2010 at 11:00 PM, sahid wrote: >

Re: [google-appengine] Re: Indexes Error

Try filing a production issue. http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue Robert On Fri, Oct 8, 2010 at 19:29, Sahid Orentino Ferdjaoui wrote: > My indexes are always in errors! > > i have vaccum indexes, after indexes are deleted i have RE update my

[google-appengine] Re: Indexes not updating

Also affecting another app - two out of five - so may be more general. On Tuesday, 31 July 2012 12:57:06 UTC+12, GregF wrote: > > One of my apps has stopped updating indexes when entities are added or > updated. This affects all indexes, including implicit indexes not > explicitly set up. > > Ot

[google-appengine] Re: Indexes not updating

This is fixed now, all new entities are indexed. Looks like eventual consistency took a very long time, but came through. Many thanks to whoever fixed it. On Tuesday, 31 July 2012 12:57:06 UTC+12, GregF wrote: > > One of my apps has stopped updating indexes when entities are added or > updated

[google-appengine] Re: Indexes stuck building

The typical procedure is to remove them, vacuum indexes, and then re-add. On Friday, October 4, 2013 12:14:04 PM UTC-5, Justin Ellison wrote: > > First time GAE user, but I'm trying to deploy a simple open source app and > my indexes stay stuck in "building". Any guidance appreciated. > > applic

[google-appengine] Re: Indexes stuck building!

Can someone from Google help me out on this? It's a little scary that if an app breaks, we have to hope someone from Google picks up on the groups thread. On Sep 3, 2:36 pm, Michael Air <[EMAIL PROTECTED]> wrote: > Hi, > > I've got three indexes that have been stuck on building for days now. >

[google-appengine] Re: Indexes stuck building!

Hi Michael, I'd be happy to take a look, please email me your app id. Thank you, Jeff On Sep 3, 11:11 pm, Michael Air <[EMAIL PROTECTED]> wrote: > Can someone from Google help me out on this? > > It's a little scary that if an app breaks, we have to hope someone > from Google picks up on the g

[google-appengine] Re: indexes over quota

A thread like this is off-topic for Google Groups and would be most appropriate to open a case on public issue tracker , which we monitor closely. Please feel free to link the case here so it may help other users in the community that experiences the same issue

[google-appengine] Re: Indexes Not Building

Another two days has gone by and these indexes are still not building. This is causing errors galore in our cron jobs and queued tasks. On Feb 27, 10:05 am, jread wrote: > Hello, > > We deployed a new version of our app (appid: steprep) yesterday > afternoon and we have seven new indexes that say

[google-appengine] Re: Indexes Not Building

Thanks Nick. I cleared the indexes that are in error from our index.yaml and did a vacuum, but the delete operations have now almost all gone to the error state themselves. Any idea what we should try next? Thanks, Jeff. On Mar 1, 10:03 am, "Nick Johnson (Google)" wrote: > Hi, > > I've reset y

[google-appengine] Re: indexes exceeding quota

Above in the search box do a search for 'exploding index' --~--~-~--~~~---~--~~ 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 unsubscri

[google-appengine] Re: indexes exceeding quota

Thank you. I read many posts and still have troubles with seemingly trivial queries, specifically to filter by category, boolean, time and ordered by time. There were too many combinations. On Aug 4, 5:20 pm, Holger wrote: > Above in the search box do a search for 'exploding index' --~--~---

[google-appengine] Re: Indexes stuck building

This is a known Bug, someone from google must correct it for you. I am having the same issue and waiting for a response from someone over here: http://groups.google.com/group/google-appengine/browse_thread/thread/20f9c68627e4b762# On Sep 13, 7:04 pm, Dave wrote: > Hi, I have two indexes that a

[google-appengine] Re: Indexes stuck building

Hi Dave, What is your App ID? -Nick Johnson On Mon, Sep 14, 2009 at 1:04 AM, Dave wrote: > > Hi, I have two indexes that are stuck building and have been in this > state for more than a day. I've deleted everything out and done the > vacuum but they stay in the building state. > > How can I g

[google-appengine] Re: Indexes stuck building

Hi Nick, thx for the response. It's myblindrebel. Dave On Sep 14, 6:35 am, "Nick Johnson (Google)" wrote: > Hi Dave, > What is your App ID? > > -Nick Johnson > > On Mon, Sep 14, 2009 at 1:04 AM, Dave wrote: > > > Hi, I have two indexes that are stuck building and have been in  this > > state f

[google-appengine] Re: Indexes stuck building

Hi Dave, I've reset your index states to 'error', so you should be able to vacuum and recreate them now. -Nick Johnson On Mon, Sep 14, 2009 at 1:10 PM, Dave wrote: > > Hi Nick, thx for the response. It's myblindrebel. > > Dave > > On Sep 14, 6:35 am, "Nick Johnson (Google)" > wrote: > > Hi Dav

[google-appengine] Re: Indexes still 'Building'

Apologies Szczepan, I had indeed missed your email and you should now be able to vacuum. Please keep me posted if you get stuck again. Since your app has a large number of indexes, you may encounter issues if you delete and re-add the indexes multiple times in a day as there is currently a known i

[google-appengine] Re: Indexes still 'Building'

Thanks Jeff, I was able to vacuum the indexes, waited till they disappeared and then updated my app with desired indexes. Now they are again stuck in 'Building' state since two days. Should I expect them to complete or are they stuck again? Szczepan On Sep 22, 7:44 pm, "Jeff S (Google)" wrote:

[google-appengine] Re: Indexes still 'Building'

Hi Szczepan, These indexes were in fact stuck, I've taken this discussion into direct email since this is related to this app's large number of indexes. Thanks for reporting :-) -Jeff On Thu, Sep 24, 2009 at 4:41 AM, Szczepan wrote: > > Thanks Jeff, > > I was able to vacuum the indexes, waited

[google-appengine] Re: Indexes building stuck

Hi, The app ID you provided, "gchalange", isn't valid. Did you misspell it? -Nick On Tue, Sep 29, 2009 at 4:54 PM, riklaunim wrote: > > I have app of id: "gchalange" (development version of app that my > customer will get later), and new indexes uploaded last friday didn't > build yet: > > col1

[google-appengine] Re: Indexes building stuck

Ach... yes ;) It's "gchalanage" On 30 Wrz, 12:03, "Nick Johnson (Google)" wrote: > Hi, > The app ID you provided, "gchalange", isn't valid. Did you misspell it? > > -Nick > > > > On Tue, Sep 29, 2009 at 4:54 PM, riklaunim wrote: > > > I have app of id: "gchalange" (development version of app th

[google-appengine] Re: Indexes building stuck

Hi, You should be able to vacuum and re-create your indexes now. -Nick Johnson On Wed, Sep 30, 2009 at 11:49 AM, riklaunim wrote: > > Ach... yes ;) It's "gchalanage" > > On 30 Wrz, 12:03, "Nick Johnson (Google)" > wrote: > > Hi, > > The app ID you provided, "gchalange", isn't valid. Did you mi

[google-appengine] Re: Indexes building stuck

Ok, they are gone now after vacuum_indexes. But trying to rebuild them with update_indexes (and the index.yaml that has them) i get 500 server error Uploading index definitions. Error 500: --- begin server output --- Server Error (500) A server error has occurred. --- end server output --- upd

[google-appengine] Re: Indexes building stuck

Hi, You should be able to upload new indexes now. -Nick On Fri, Oct 2, 2009 at 2:22 PM, riklaunim wrote: > > Ok, they are gone now after vacuum_indexes. But trying to rebuild them > with update_indexes (and the index.yaml that has them) i get 500 > server error > > Uploading index definitions.

[google-appengine] Re: Indexes building stuck

everything works :) Thanks. --~--~-~--~~~---~--~~ 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

[google-appengine] Re: Indexes not deleting

You need to vacuum your indices manually: appcfg.py vacuum_indexes http://code.google.com/appengine/docs/appcfgpy.html On Dec 26, 6:05 am, dloomer wrote: > I have several indexes on the Google server that are not only no > longer in my local index.yaml, but reference properties that no long

[google-appengine] Re: Indexes are broken

All my indexes are cleaned up now after12 hours deleting or error status. My commercial live service have been downed 12 hours by this indexing broken & rebuild. On Jun 8, 10:23 pm, ksjun wrote: > After adding some new indexes, my old indexes were broken. So I > deleted all indexes at index.ya

[google-appengine] Re: Indexes Not Building (again)

These indexes finished building over the weekend. Thanks ;) On Jun 4, 9:24 am, jread wrote: > We added a new index to our app (appid: steprep-demo) 24 hours ago and > it has yet to start building. Can someone give it a kickstart? We have > also added the index this morning to our production app (

[google-appengine] Re: Indexes - Production issue - urgent

Not sure what the problem you have. I had a similar problem before. I used the following command to create indexes and fixed the problem >gcloud datastore indexes create src/main/webapp/WEB-INF/index.yaml cheers Jerry On Saturday, 2 January 2021 at 13:49:51 UTC+11 rajesh...@veersoftsolutions

[google-appengine] Re: Indexes - Production issue - urgent

Hello, Please follow the next Official Documentation [1] to create the Support case. Could you please share the error you are getting when creating an index in your Cloud Datastore? Looking forward to your reply. Best Regards, Nibrass = [1] https://cloud.google.com/support/d

Re: [google-appengine] Re: Indexes Not Building

Hi, I've reset your indexes to error state. You can try building them again now. -Nick Johnson On Mon, Mar 1, 2010 at 3:22 PM, jread wrote: > Another two days has gone by and these indexes are still not building. > This is causing errors galore in our cron jobs and queued tasks. > > On Feb 27,

[google-appengine] Re: Indexes in Error State

Hi Ishmael, It appears that the two indices that you mentioned were removed and have been recreated successfully. I'm sorry I didn't get to this sooner. Cheers, Jeff On Jul 2, 6:51 am, Wooi Koay wrote: > What I did, as a temporary work around until the index problem is > fixed, was to modify

[google-appengine] Re: Indexes stuck in building

Hi Peecho, I've moved your indexes to 'error'. Try vacuuming them now. -Nick Johnson On Sat, Aug 8, 2009 at 2:48 PM, Peecho wrote: > > Hi, > My indexes seem stuck in Building for over 4 days now. I tried to > vacuum them but alas. Could anybody help me out, please? > My app's name is peechotest

[google-appengine] Re: Indexes stuck in building

Thanks, I could vacuum them now. However, my second attempt does not seem to do much either. I am a Python newbie, so I fear I do something wrong... For some reason, I see only 4 indexes 'building' in my console, while my index.yaml actually describes 7 indexes. Does that mean some error in the o

[google-appengine] Re: Indexes stuck in building

On Mon, Aug 10, 2009 at 8:46 PM, Peecho wrote: > > Thanks, I could vacuum them now. > > However, my second attempt does not seem to do much either. I am a > Python newbie, so I fear I do something wrong... > For some reason, I see only 4 indexes 'building' in my console, while > my index.yaml actu

[google-appengine] Re: Indexes stuck in building

Yes, I have run these commands, but the indexes are still stuck (again). Since the indexes are standard Bloog (and I don't see anybody else complaining), would it be worth a try to deploy the code into another app to see if it would work there? Or is there anything else I could do? Thanks for you

[google-appengine] Re: Indexes stuck in building

I created an extra app, named peechobloog. The indexes get stuck in that one, too. However, I played around with the actual order of the indexes in the index.yaml file, and it seems that this index... - kind: Article properties: - name: published direction: desc ...is causing problems. I

[google-appengine] Re: Indexes stuck in building

Hi Nick I also have 3 indexes in my app (alin) which are stuck since two days in the building state. Could you please help me set them to the error state so I can perform a vacuum. Is there actually a way to set the stuck indexes to the error state myself so I and maybe others dont have to harass

[google-appengine] Re: Indexes stuck in building

On Tue, Aug 11, 2009 at 3:28 PM, Peecho wrote: > > Yes, I have run these commands, but the indexes are still stuck > (again). Since the indexes are standard Bloog (and I don't see anybody > else complaining), would it be worth a try to deploy the code into > another app to see if it would work the

[google-appengine] Re: Indexes stuck in building

On Tue, Aug 11, 2009 at 5:56 PM, Peecho wrote: > > I created an extra app, named peechobloog. The indexes get stuck in > that one, too. However, I played around with the actual order of the > indexes in the index.yaml file, and it seems that this index... > > - kind: Article >  properties: >  - na

[google-appengine] Re: Indexes stuck in building

The app you specify doesn't _have_ any indexes. -Nick Johnson On Tue, Aug 11, 2009 at 4:26 PM, Endri wrote: > > Hi Nick > I also have 3 indexes in my app (alin) which are stuck since two days > in the building state. Could you please help me set them to the error > state so I can perform a vacuu

[google-appengine] Re: Indexes stuck in building

Sorry, my mistake. You should now be able to vaccum your indexes. -Nick Johnson On Wed, Aug 12, 2009 at 10:32 AM, Nick Johnson (Google) wrote: > The app you specify doesn't _have_ any indexes. > > -Nick Johnson > > On Tue, Aug 11, 2009 at 4:26 PM, Endri wrote: >> >> Hi Nick >> I also have 3 inde

[google-appengine] Re: Indexes Stuck On Building

Hi Arun, I've reset your indexes; you should be able to vacuum and rebuild them now. -Nick Johnson On Sun, Oct 18, 2009 at 7:41 PM, Arun Shanker Prasad < arunshankerpra...@gmail.com> wrote: > > Hi All, > > I was deploying a new application there was no data in the datastore, > there was some err

[google-appengine] Re: Indexes Stuck On Building

Hi Nick, Thank you Nick for resetting the indexes. Was able to vacuum and re- upload them. Thanks, Arun Shanker Prasad. On Oct 19, 7:10 pm, "Nick Johnson (Google)" wrote: > Hi Arun, > I've reset your indexes; you should be able to vacuum and rebuild them now. > > -Nick Johnson > > On Sun, Oct

[google-appengine] Re: indexes for "and" queries

Hi bernd, You are correct, matching on two members of a list (which is how Searchable works) requires the list property to be listed twice in the index. One thing to watch out for, is that there is currently a limit of 5000 index rows per entity (index row counts are described here: http://code.g

[google-appengine] Re: indexes for "and" queries

Where is Searchable defined? (Windows explorer search won't look at contents of .py files) On Nov 6, 2:30 am, dobee <[EMAIL PROTECTED]> wrote: > if i do this to find any entities that match house and dog i do > > Searchable.all().filter('content_type =', 'something').filter('words > =', 'ho

[google-appengine] Re: indexes for "and" queries

In ext/search On Nov 8, 1:24 am, Andy Freeman <[EMAIL PROTECTED]> wrote: > Where is Searchable defined?  (Windows explorer search won't look at > contents of .py files) > > On Nov 6, 2:30 am, dobee <[EMAIL PROTECTED]> wrote: > > > if i do this to find any entities that match house and dog i d

[google-appengine] Re: indexes for expando objects

On Fri, Feb 20, 2009 at 12:13 PM, pedepy wrote: > > Hi .. I just stumbed upon a NeedIndexError. I understand why it > happens, but I dont quite understand the 'motivations' behind it. > > If the development server can just generate indexes for queries as I > make them, why would that not be possi

[google-appengine] Re: indexes for expando objects

On Feb 20, 3:13 pm, pedepy wrote: > Hi .. I just stumbed upon a NeedIndexError. I understand why it > happens, but I dont quite understand the 'motivations' behind it. > > If the development server can just generate indexes for queries as I > make them, why would that not be possible for the de

[google-appengine] Re: indexes for expando objects

This is not the main reason why i chose to go with expando objects, but it does a little like this: In expando's, I can store just information i need; that is, if I happen to have a 'color' attribute for a given entry, I can just store it's 'color' information even if others dont have it; Also,

[google-appengine] Re: Indexes stuck at Building

This fixed itself, although I still have one (old) index in Error that I can't delete. Is it typical for an index for a new model to take a few hours to build? I thought the building process would only apply if existing entities had to be indexed? thanks Michael On Apr 24, 9:22 am, "Michael O'B

[google-appengine] Re: Indexes stuck at Building

I'm having the same issue - both updating an app with no data (I deleted the data before updating), and with a completely new app. Old app named "kirentest1", fresh app "duckbiller" On Apr 24, 1:22 am, "Michael O'Brien" wrote: > Hi there, > > I just changed the name of one of my models, which m

[google-appengine] Re: Indexes in Error State

Forgot to include my App ID: dd-pdigm and the Indexes are for "PlaceHoodIndex" and "PlaceTagIndex" entities. On Jul 1, 1:35 pm, Ishmael wrote: > Dear Google?: > > I have two indexes in an Error state. I've removed them from > index.yaml and deployed. Then ran vacuum_indexes which said it was >

[google-appengine] Re: Indexes in Error State

It's been more than 24 hours now and my Indexes are both still in the Error State! I've been using App Engine for nearly a year now and every time I post to this group I NEVER get a response. Our application is in a production state and I realize this product is in Beta, but WHY CAN'T I DELETE MY

[google-appengine] Re: Indexes in Error State

What I did, as a temporary work around until the index problem is fixed, was to modify my query slightly to require a new index. On Jul 2, 8:02 am, Ishmael wrote: > It's been more than 24 hours now and my Indexes are both still in the > Error State! > > I've been using App Engine for nearly a ye

[google-appengine] Re: Indexes may be stuck

Hi Ikai! Thank you very much. On Dec 21, 6:36 pm, "Ikai Lan (Google)" wrote: > They've been placed into error state. Go ahead and run vacuum_indexes. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > Blogger:http://googleappengine.blogspot.com > Reddit:http://www.reddit.com/r/

[google-appengine] Re: Indexes serving but not working

Index entries for each entity are only created when the entity is saved, so if your data is older than your index you'll have to load-save each entity. Could that be the case? On Wednesday, September 5, 2012 1:08:48 PM UTC+2, mmedio wrote: > > I have 3 new indexes in a Kind type of my app, but

[google-appengine] Re: Indexes won't Vacuum or Update

Hi Aaron, It seems like the indexes for this app are stuck, if you would like, I can move the stuck indexes to the 'error' state which should allow you to vacuum and re-upload your index definitions. -Marzia On Wed, Sep 24, 2008 at 6:14 AM, Aaron OBrien <[EMAIL PROTECTED]> wrote: > I saw the ou

Re: [google-appengine] Re: Indexes - Production issue - urgent

I tried deploying the indexes again the next day. everything is fine now. Thanks for the pointers. On Tue, Jan 5, 2021 at 10:36 PM 'nibrass' via Google App Engine < google-appengine@googlegroups.com> wrote: > Hello, > > Please follow the next Official Documentation [1] to create the Support > c

[google-appengine] Re: Indexes stuck in building status

Hi Tom, I've errored out these indexes for you, so you can now vacuum and recreate. If my memory serves me correctly, I've reset these before and I'm wondering if there is something in your usual upload procedure which is triggering the stuck indexes issue. Could you describe the process you use w

[google-appengine] Re: Indexes building for 3 days

I've reset your index count and moved the stuck indexes into the error state. I think the issue may have been related to the fact that this app had 100 indexes, which is the upper limit. Would it be possible to use fewer indexes? If not, we can discuss the possibility of allowing this app to have

[google-appengine] Re: Indexes building for 3 days

Thank you. I vacuumed the indexes and tried again, with a subset of 28 indexes. It has been 48 hours and they are still building. Any help is appreciated. On Oct 8, 4:04 pm, "Jeff S (Google)" wrote: > I've reset your index count and moved the stuck indexes into the error > state. I think the

[google-appengine] Re: Indexes building for 3 days

Apologies, I've move these indexes to the error state, so you'll need to re-vacuum. Thank you, Jeff On Sun, Oct 11, 2009 at 11:05 AM, visadm543 wrote: > > Thank you. I vacuumed the indexes and tried again, with a subset of > 28 indexes. It has been 48 hours and they are still building. Any

[google-appengine] Re: Indexes building for 3 days

Thanks. I vacuumed and updated the indexes. It worked this time, but now 16 new indexes are stuck building. If these 16 indexes are a problem, I can modify the application not to use them. On Oct 12, 10:38 am, "Jeff S (Google)" wrote: > Apologies, I've move these indexes to the error state, s

[google-appengine] Re: Indexes building for 3 days

Interesting. I don't recall the old indexes which were stuck, are the ones that are now stuck the same ones? I'm investigating this in greater depth. Thank you, Jeff On Tue, Oct 13, 2009 at 9:53 AM, visadm543 wrote: > > Thanks. I vacuumed and updated the indexes. It worked this time, but > n

[google-appengine] Re: Indexes building for 3 days

The indexes now stuck are not the same as the ones that were stuck before. They are new indexes. The original set of indexes are currently serving correctly. On Oct 13, 11:05 am, "Jeff S (Google)" wrote: > Interesting. I don't recall the old indexes which were stuck, are the ones > that are no

[google-appengine] Re: Indexes stuck in "Building" state

Anyone? This is for my senior project and I need to make sure it works correctly ASAP... On Jan 11, 8:30 am, mercies wrote: > My indexes are stuck in "Building" state and have been so for a couple > of days now. > > Could someone please clear them out? > > Also, I know I need to run vacuum_index

[google-appengine] Re: Indexes stuck in "Building" state

I had no idea that was there, thank you so much! You're a lifesaver! On Jan 13, 9:08 am, Wim den Ouden wrote: > http://code.google.com/p/googleappengine/issues/entry?template=Produc... > > 2011/1/13 mercies : > > > > > > > > > > > Anyone?  This is for my senior project and I need to make sure it

[google-appengine] Re: indexes stuck building for 4 days

There is another index over another property. I believe both should have the same number of entities. The other index currently always has about 600k more entities than this one that is building. Each day the total numbers for both go up about the same, but this 600k diff remains. This suggests to

[google-appengine] Re: Indexes not updated (manually or automatically)

When you start your app and run the search, do you see a message that says something like: 2009-12-29 17:58:11,395 dev_appserver_index.py:205] Updating .../ index.yaml or do you see one that says "Detected manual index.yaml, won't update"? I have had a problem where the line enders will prevent up

[google-appengine] Re: Indexes not updated (manually or automatically)

Thank you for your help John. It wasn't either of those issues, but it did help me to look through the output and discover that there was a miscellaneous tab character on an empty line that was interfering with the processing of index.yaml. Thanks! On Dec 29 2009, 3:41 pm, John Gardner wrote: >

[google-appengine] Re: Indexes on lists of 'tags' & queries

Hi Kyle, Exploding indexes only come into play when you're _defining_ indexes - for example, an index like this would be an exploding one: - kind: Foo property: tags property: tags As long as you can satisfy your queries using the built in merge join support (which is the case in your exampl

[google-appengine] Re: Indexes on lists of 'tags' & queries

Hi Nick, I noticed that the dev server will automatically add indexes that appear to be exploding indexes when I run queries like the example above. Ie, if I do Foo.get_by_tags(['tag1', 'tag2']) the dev server will create an index in index.yaml that is identical to the one you posted above: - k

[google-appengine] Re: Indexes on lists of 'tags' & queries

On Mon, Jul 27, 2009 at 4:16 PM, Kyle Jensen wrote: > > Hi Nick, > > I noticed that the dev server will automatically add indexes that > appear to be exploding indexes when I run queries like the example > above. Ie, if I do Foo.get_by_tags(['tag1', 'tag2']) the dev server > will create an index

[google-appengine] Re: Indexes on lists of 'tags' & queries

Hi Kyle, I think what Nick meant was this: - kind: Foo property: tags1 property: tags2 that is having two different properties of type ListProperty because then the index will have rows for each combination of values for each of the property and number of rows will be multiplication of numb

[google-appengine] Re: Indexes on lists of 'tags' & queries

Hi Jai, Both your example and my original example are cases of exploding indexes. In my example, indexing on the same listproperty twice is required for certain queries (for example, the Foo.all().filter('tags =', foo).filter('tags =', bar).order('bar') example), but likewise results in an explodi

[google-appengine] Re: Indexes on lists of 'tags' & queries

Hi Nick, Thanks for replying, that made the things a bit more clear. But I still don't understand the reasoning behind it. You said the following example Foo.all().filter('tags =', foo).filter('tags =', bar).order('bar') will result in an exploding index. But why so? I believe above statemen

[google-appengine] Re: Indexes on lists of 'tags' & queries

On Mon, Jul 27, 2009 at 7:39 PM, Jai wrote: > > Hi Nick, > > Thanks for replying, that made the things a bit more clear. But I > still don't understand the reasoning behind it. > > You said the following example > > Foo.all().filter('tags =', foo).filter('tags =', bar).order('bar') > > will resul

[google-appengine] Re: Indexes on lists of 'tags' & queries

Thanks nick that made it crystal clear. Now I get it, it was the 'order by' clause that was preventing it from being a merge-join and the zig-zagging to be in effect, as you stated in your reply to Kyle. I also understand why is that so - because that would require an additional sort over the que

[google-appengine] Re: Indexes on lists of 'tags' & queries

Hi Jai, Your only options for satisfying that query are: - Tolerate an exploding index - which is not really a problem if you have fewer than about 100 tags. - Write your own query planner that performs a scan for each tag and takes the intersection of the results. - Look into using Brett's index

[google-appengine] Re: Indexes building stuck on empty datastore

this limit of 100 indexes, i hope that's for composite indexes? or I'll eventually will get in trouble... On 7 Nov., 03:38, "Jeff S (Google)" wrote: > Ah I see. Since the upper limit was reached for the number of indexes on the > index upload, none of them completed building so I've moved all of

[google-appengine] Re: Indexes building stuck on empty datastore

Hi Tonny, Yes this limit is for the custom composite indexes which are defined in index.yaml. Also if you really do need more than 100, it is possible to enable an app to use more than 100 indexes but we handle these requests on a case by case basis. Since more indexes could make a write request

Re: [google-appengine] Re: Indexes stuck in "Building" state

http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue 2011/1/13 mercies : > Anyone?  This is for my senior project and I need to make sure it > works correctly ASAP... > > On Jan 11, 8:30 am, mercies wrote: >> My indexes are stuck in "Building" state and have been so f

[google-appengine] Re: Indexes very very very slow to create

I am having the same problem, but appear to be stuck at "Queued: 0 Running: 0 Completed: 0 Total: 0". On May 24, 8:55 am, Geoff wrote: > That should read 4/5 not 45.  But still... > > On May 24, 2:50 pm, Geoff wrote: > > > I created some (3) indexes on an empty bigtable about45 hours ago and > >

[google-appengine] Re: Indexes not building for over 24 hrs

Confirmed they are built. Thx. Perhaps a good thing to add to the System Status page (http:// code.google.com/status/appengine) would be the time to get a new index through the wait queue. j On Jun 10, 1:13 pm, "Ikai L (Google)" wrote: > They look to have been built. The index building processe

[google-appengine] Re: Indexes not building for over 24 hrs

Yes, I agree, but we are on 1 week sprints, so often we only have perhaps 12-48 hrs heads up on a newly required index. Movin' and shakin', j On Jun 10, 3:07 pm, "Ikai L (Google)" wrote: > Doesn't seem like a bad idea. It's not quite as simple, though. > > I think it may be possible to push a ne

[google-appengine] Re: Indexes stuck in deleting/error state - urgent

Any way someone can take a look at this? It's been 4 days now. On Jun 17, 8:51 pm, Lenny Rachitsky wrote: > I've got two indexes in error state, one in "deleting" state (https:// > skitch.com/lennysan/ffkuf/data-store-indexes-localmind) . I've > followed the instructions to vacuum and re-index, b

[google-appengine] Re: Indexes stuck in deleting/error state - urgent

Well that's good to know about :) Thanks Barry. On Jun 20, 6:29 pm, Barry Hunter wrote: > Did you file a production issue ticket? > > http://code.google.com/p/googleappengine/issues/entry?template=Produc... > > > > > > > > On Mon, Jun 20, 2011 at 6:04 PM, Lenny Rachitsky wrote: > > Any way some

[google-appengine] Re: Indexes stuck in "Buildling" state -- Cannot vacuum

resolved On Wednesday, 16 May 2012 20:22:16 UTC+8, Ofer wrote: > > 2 indexes in my app (breadbrowser) are stuck in Buildling state and I > cannot vacuum them. > Can anybody help, please? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To

[google-appengine] Re: Indexes very very very slow to create

That should read 4/5 not 45. But still... On May 24, 2:50 pm, Geoff wrote: > I created some (3) indexes on an empty bigtable about45 hours ago and > they are still saying > > Building > Queued: 1 Running: 0 Completed: 1 Total: 2 > > Is this not unusually (unacceptably) slow? > > Geoff. > > -- >

  1   2   >