Hi Simon,
I wouldn't be surprised that it has to do with the changes made during
this downtime.
This being said, the downtime notice only mentions higher read/write
latencies, not changes in the data store behavior.
Someone from GAE team?
Cheers,
Marc.
--
Blog: http://mguillem.wordpress.com
Simon wrote:
I know that there was planned downtime yesterday (see
http://groups.google.com/group/google-appengine-downtime-notify if you
aren't monitoring it already) as part of their plan to try and fix
their datastore performance issues (mentioned here
http://googleappengine.blogspot.com/2010/07/upcoming-datastore-downtime.html).
It sounds to me like the problems your facing are very much linked to
these changes!
On Jul 8, 10:39 am, Marc Guillemot <[email protected]> wrote:
Hi,
yesterday my application worked just fine. Today data isn't reachable
with a simple query anymore (data is here, I can find it through the
Data Viewer).
Here is the exception thrown:
----------------
Uncaught exception from servlet
The primary key for mymodel.JarData is an unencoded string but the key
of the corresponding entity in the datastore does not have a name. You
may want to either change the primary key to be an encoded string (add
the "gae.encoded-pk" extension), change the primary key to be of type
com.google.appengine.api.datastore.Key, or, if you're certain that this
class will never have a parent, change the primary key to be of type Long.
org.datanucleus.store.appengine.FatalNucleusUserException: The primary
key for mymodel.JarData is an unencoded string but the key of the
corresponding entity in the datastore does not have a name. You may
want to either change the primary key to be an encoded string (add the
"gae.encoded-pk" extension), change the primary key to be of type
com.google.appengine.api.datastore.Key, or, if you're certain that this
class will never have a parent, change the primary key to be of type Long.
at
org.datanucleus.store.appengine.DatastoreFieldManager.fetchStringPKField(Dač˛ astoreFieldManager.java:246)
at
org.datanucleus.store.appengine.DatastoreFieldManager.fetchStringField(Datač˛toreFieldManager.java:192)
at
org.datanucleus.state.AbstractStateManager.replacingStringField(AbstractStač˛ eManager.java:1180)
....
----------------
My question: how can it happen, that changes in DataStore have such
breaking consequences? And how often will it happen?
Cheers,
Marc.
--
Blog:http://mguillem.wordpress.com
--
You received this message because you are subscribed to the Google Groups "Google
App Engine for Java" 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-java?hl=en.
