For the sake of anyone else who ends up needing this info... yes,
those steps are exactly right.  The only trick was that the python
bulkloader can't handle natural sparse (ie not autogenerated) long
keys.  Easy enough to disable (search bulkloader.py for IncrementId).

By the way... that code in the bulkloader assumes that generated ids
monotonically increase.  I thought that was supposed to be a bad
assumption, no?

Jeff

On Wed, Dec 16, 2009 at 10:51 AM, Jeff Schnitzer <[email protected]> wrote:
> Ouch :-(
>
> Can you tell me if these are indeed the steps necessary to migrate to
> a new application?
>
>  1) Install a python application version on both app_old and app_new
> which has remote_api enabled
>  2) Block access to app_old (maintenance page)
>  3) Create a data dump of app_old
>  4) Upload data dump to app_new
>  5) Reassign domain.old to point to the new app
>
> The one thing I am particularly concerned about is #5, being able to
> switch the old domain to the new application.  I have many thousands
> of iPhone clients making RPC calls to the old domain and they can't
> easily be changed.
>
> Will I need to delete app_old before I can reallocate the domain.old?
> When I reallocate the domain, will the change take affect immediately?
>
> Also... I have one entity type with generated ids.  The python data
> import/export says that generated ids will be imported
> appropriately...  but also I've read warnings that both creating
> explicit Long keys and autogenerating keys could result in a conflict.
>  Is this just because an explicit put() with an id could overwrite a
> generated key (easy enough to avoid) or because the generator could
> generate a key that has already been explicitly put() (nearly
> impossible to void)?  I am concerned that after I perform my restore
> and enable public access, new autogenerated keys will destroy data.
>
> BTW I've logged a bug regarding the verbiage here:
> http://code.google.com/p/googleappengine/issues/detail?id=2523
>
> Thanks,
> Jeff
>
> On Wed, Dec 16, 2009 at 4:19 AM, Nick Johnson (Google)
> <[email protected]> wrote:
>> Hi Jeff,
>> Unfortunately, it's not currently possible to change the authentication
>> settings after creating your app, and you cannot add a domain that doesn't
>> match the authentication settings. Sorry for the trouble.
>> Are you able to file a bug report for the verbiage on the creation page?
>> Thanks,
>> Nick Johnson
>> On Wed, Dec 16, 2009 at 8:41 AM, Jeff Schnitzer <[email protected]> wrote:
>>>
>>> So... my application is deployed, happy, and now populated with a fair
>>> amount of data.  But now we have acquired a new, sexier domain name
>>> and need to migrate the app to the new domain name.
>>>
>>> There seems to be one catch:  I created the application to
>>> authenticate against the Google Applications domain.  It was literally
>>> a coin-toss; our app authenticates against Facebook so I didn't think
>>> the answer was relevant.  But now it seems that you cannot add a
>>> second domain to an application if it was configured this way.
>>>
>>> First question:  Is it really true that I can't add a second domain to
>>> an application that was configured to auth against google apps?  There
>>> was no warning that this would be the case when I set it up to auth
>>> this way; it's only something I have inferred from several vaguely
>>> related discussion group threads and the fact that I keep getting
>>> errors ("You do not have permission...") when I try.
>>>
>>> Second question:  If this really is a restriction, is there *any* way
>>> of converting the application over to auth against google accounts?  I
>>> have a live running system in continual use, and while traffic is
>>> still relatively modest, it would be a major effort to synchronize the
>>> objects from one app to another during the transition.  I'm in
>>> Java-land, so I don't have easy access to bulk export/import.
>>>
>>> I hate to sound like a whiner, but this issue (not being able to
>>> migrate to a new domain name) is a really HUGE gotcha that really
>>> should be mentioned in the warning text when you create an app.  I
>>> still hope I'm just misunderstanding the system and there is an easy
>>> solution :-(
>>>
>>> Thanks in advance for any help or advice,
>>> Jeff
>>>
>>> --
>>>
>>> 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.
>>>
>>>
>>
>>
>>
>> --
>> Nick Johnson, Developer Programs Engineer, App Engine
>> Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number:
>> 368047
>>
>> --
>>
>> 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.
>>
>

--

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.


Reply via email to