Entity kind disappeared after HRD migration

34 views
Skip to first unread message

Nikolay Elenkov

unread,
Feb 28, 2012, 9:25:00 AM2/28/12
to google-a...@googlegroups.com
Hi, 

I finally decided to migrate one of my apps to HRD, because I was getting datastore failures occasionally. 
I followed the docs, everything went smoothly, but all of a sudden one of my entity kinds disappeared 
completely. I verified that data is copied over successfully before aliasing the app, and it did work 
for a while. Then I deployed a new version to the HRD app, and the entities are gone. Nothing 
in the logs suggests I've deleted them by mistake. 

The data structure is quite simple: Parent->Child. All the Child entities are there, but the 
Parent ones are gone. Not visible in the datastore viewer and datastore admin in the 
console, also not available from the app. Displaying a child entity in the viewer produces 
a link for the Parent, but clicking it naturally fails. Example:

Decoded entity key: Parent: id=1120615 > Child: id=1

Entity key: ahFzfmhrci1saWNlbnNlLWhyZHIeCxIGQ291cG9uGOeyRAwLEgpSZWRlbXB0aW9uGAEM

I have backups in the old MS blobstore, and I may attempt to recover them, 
but it seems that won't work, since the keys have changed. 

Any ideas about what might have caused this and what's the best way to 
proceed? 

Nikolay Elenkov

unread,
Feb 28, 2012, 11:18:03 PM2/28/12
to google-a...@googlegroups.com
On Tue, Feb 28, 2012 at 11:25 PM, Nikolay Elenkov
<nikolay...@gmail.com> wrote:

>
> I have backups in the old MS blobstore, and I may attempt to recover them,
> but it seems that won't work, since the keys have changed.
>
> Any ideas about what might have caused this and what's the best way to
> proceed?
>

I've recovered the Parent entities using the bulk loader based on output
from the old app's datastore viewer. The Child entities are log-like data,
so I can live without them for now.

Here's another question: is there a way to connect to the old app
and export the data after it's been redirected? The remote_api is
also going to the new app, so that obviously doesn't work.

Reply all
Reply to author
Forward
0 new messages