Ok, this is a very different problem then. Here is the function that reads the data: http://code.google.com/p/googleappengine/source/browse/trunk/python/google/appengine/api/datastore_file_stub.py#444 Here is the function that writes the data: http://code.google.com/p/googleappengine/source/browse/trunk/python/google/appengine/api/datastore_file_stub.py#484
Can you make sure it is reading and writing to the correct place? (by looking at self.__datastore_file) (we will try to reproduce and debug on our end as well) On Wed, Sep 7, 2011 at 1:38 PM, Joshua Smith <[email protected]>wrote: > Clarifying: > > >> > >> After running without --high_replication and writing to the datastore, > when you run it with --high_replication do you see those writes? > > > > No. > > > When I run with --high_replication I don't see ANY of my data, in any case. > It is as though that option causes the system to start with a clean slate > every time. > > Note that without the --high_replication option, I have to use > --default_partition= to see the data I created before a recent SDK update. > If I run without that, I have a clean slate to start with, but it does save > and have access to that data going forward. But the use of that option has > no impact on the --high_replication behavior, so I suspect those are not > related. > > -Joshua > > > -- > 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.
