Hi again Ben,
As far as we can tell, this is due to a one-off corruption in the index
building process. Are you able to delete and re-create the index in
question?
-Nick Johnson
On Wed, Jun 17, 2009 at 3:05 PM, Ben Nevile wrote:
>
> In fact, on second look, the problem has NOT been fixed.
>
>
In fact, on second look, the problem has NOT been fixed.
It has been fixed for the entity with id 128120, but now a different
entity with id 71134 has taken its place. like 128120, 71134 does not
belong at the top of this index.
The application relies on the integrity of this index. Please help
Hi Ben,
The issue was due to a bug in the way we generated index entries for your
entities. In addition to the correct index entries, a faulty one was
generated. We're working on ensuring this bug doesn't happen again right
now.
In general, yes, you should be able to trust the indexes absolutely.
Great, yes, now it is fixed. Can you provide any insight into the
nature of the problem? Should I be on guard for this type of thing in
the future? What level of trust should I have for the indices?
Ben
On Jun 17, 8:29 am, "Nick Johnson (Google)"
wrote:
> Hi Ben,
>
> We've taken another lo
Hi Ben,
We've taken another look; _now_ it should be fixed. :)
-Nick Johnson
On Tue, Jun 16, 2009 at 1:02 AM, Ben Nevile wrote:
>
> Hi Nick,
>
> Sadly it is NOT fixed. Here is the URL again:
>
>
> http://appengine.google.com/datastore/explorer?app_id=friendmonth&viewby=gql&kind=FacebookUser&qu
Hi Nick,
Sadly it is NOT fixed. Here is the URL again:
http://appengine.google.com/datastore/explorer?app_id=friendmonth&viewby=gql&kind=FacebookUser&query=SELECT+*+FROM+FacebookUser+where+expired_fotm%3DTrue+order+by+last_nudged_at
Ben
On Jun 15, 10:14 am, "Nick Johnson (Google)"
wrote:
>
Hi Ben,
Thanks for your patience, and for your consideration in leaving the app
as-is. We have all the data we need, and your index should now be fixed.
-Nick Johnson
On Mon, Jun 15, 2009 at 4:21 PM, Ben Nevile wrote:
>
> bumping. app still in a broken state, but I need some resolution wrt
> t
bumping. app still in a broken state, but I need some resolution wrt
this fundamental problem.
Ben
On Jun 11, 10:23 pm, Ben Nevile wrote:
> Okay, I'm just going to leave my app in a broken state so that someone
> from Google can look at this. I've been dealing with these broken
> indices for
