Re: [google-appengine] HRD migration broke tables & indexes

[Takashi Matsuo]

Hi Saurabh,

On Sun, Oct 7, 2012 at 7:07 PM, Saurabh <saurab...@gmail.com> wrote:

Hi,

HRD migration has been a nightmare for me.  I did a migration of over 55GB database to HRD yesterday. Post migration several of my indexes and datastore queries are broken.  

Some examples:

• Select * from table1 where col1=val1 => query.count() > 0 but query.get() = empty
• Select * from where col1=val1 => query.get() = empty in my python code. However, same query returns results in Datastore Viewer.
• Select * from table1 order by col1 desc => misses many rows

How can I get these tables & indexes repaired? 

I suspect all of these are expected behavior due to the eventually nature of the HR Datastore, and I hope those issues have resolved themselves automatically.

If you still have the issue, please let me know your app-id.

-- Takashi

 

Thanks in advance for your help,

Saurabh

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/2mBUkDu3OZ0J.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
Takashi Matsuo | Developers Advocate | tma...@google.com

[Andrew Mackenzie]

Indexes are not part of datastore and are not migrated, they are defined in your app and built after being uploaded as part of a deploy or index update via appcfg.

Existing entities (by key match) are overwritten. "Extra" entities you had at destination before copy are not deleted.

Mine worked fine and keys maintained.