Eric, we're currently tracking the issue in http://code.google.com/p/googleappengine/issues/detail?id=2481. Please star it so you will be notified when we make status changes.
- Jason On Fri, Dec 4, 2009 at 4:24 PM, Eric Rannaud <[email protected]> wrote: > On Fri, Dec 4, 2009 at 4:17 PM, Jason (Google) <[email protected]> > wrote: > > Hi Eric. Yes, the reason why you see 3 instead of 4 was because we re-put > > one of the incorrect entities. If you re-put the other (either > > programatically or via the Admin Console), you should see it appear when > you > > execute the query. We're still working on determining why they weren't > > returned with the original index. > > It's possible that several of your other entities are affected, and we'll > > It's indeed likely. Since I found that example by chance, it's > unlikely these are the only 2 out of 500,000. > > > > try to clear that up for you soon. If you can't wait, you can always > write a > > remote_api script that queries for all entities and writes each in an > > individual transaction yourself or continue filtering in memory until we > > repair the index on our end. > > It's alright, I'm sorting the results manually in application code. > The overhead is negligible with my current level of activity. This > will do fine for now. > > 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > -- 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.
