Yeah, so far I've went with option 3 because one set of transfers involved apps with several hundred million entities. Would have been a real bummer to have the datastore admin crap-put midstream with that. And downloading then reuploading that.... well, you decide. The other *much* more envolved migration was a small but very complex dataset and I wanted to make some very large schema changes. The migration basically gave a fresh-start, I just had to write a old to new conversion script.
On Mon, Jun 27, 2011 at 02:11, Greg <g.fawc...@gmail.com> wrote: > The built-in datastore admin tool is excellent - see > http://neogregious.blogspot.com/2011/04/migrating-app-to-high-replication.html > for a discussion of data transfer options. > > It won't do schema changes or data subsets, but knowing what I know > now I'd change the schema (see > http://groups.google.com/group/google-appengine/browse_thread/thread/9ae4c6fc3ca5acc0/520c294137bc8dbf) > and delete the unwanted entities in place, then use the datastore > admin tool. This keeps your keys, IDs and indexes correct. > > Cheers > Greg. > > -- > 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 to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
