On Thu, Jan 6, 2011 at 8:19 AM, Alexander Maslov <[email protected]>wrote:
+1 Well said, Alexander, and I wholeheartedly agree. The migration path should be automated from the back end when the developer selects the HRD from the admin application configuration console. I can see the lack of automation here as being a major impediment to the HRD's adaption for developers with existing applications.The process as it now stands exposes live data to possible erroneous migration processes that we create to migrate live data which could cause integrity issues if we don't get it 100% right the first time. And having to create a new application in order to migrate is a no starter IMO. Come on, Google guys and gals, you are definitely talented enough to automate the migration which would eliminate any chance of damaging live data and eliminate the need to create a new application. Sincerely, Jeff Speaking about current implementation. It's really weird that we do not have > any way to migrate to High Replication Datastore without creating new > application. It mite look not a big issue from Google's point of view, but > that makes a lot of troubles to those developers, who use appspot.comdomain > to host applications. New application name means new domain name, > etc. > > -- > 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. > -- *Jeff Schwartz* -- 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.
