It's my understanding that, with HR, getting an entity by key is only
strongly consistent within a transaction.
If this is wrong, then a significant portion of my own task handling
code may need revisiting...
Perhaps someone who knows more could clarify this.
Tom.
On 21 March 2011 22:10, Simon
I thought that it was strongly consistent because in the background the
get-by-key was forced into a transaction and that you didn't have to declare
it yourself. If it didn't happen so sporadically, I'd test to see whether
this fixed the issue!
As you say, if someone could clarify that would
According to the docs, gets, puts, deletes, and ancestor queries are all
strongly consistent:
http://code.google.com/appengine/docs/java/datastore/hr/
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send
Thanks for the link, somehow I'd managed to miss that page of
documentation entirely*; it's good to know, though it indicates other
problems for the OP.
I'm not clear on why eventually consistent gets aren't an option, ie.
why all gets are indicated as being strongly consistent. Is this a
direct
I've got a query about tasks and transactions on a High-replication app that
I'm hoping someone can help me with.
I've got the following scenario:
1) Begin a transaction
2) Persist an entity
3) Enqueue a task within the transaction
4) Commit the transaction
Within the task, I get the entity via
