CommittedButStillApplyingException should be supressed
Opened this issue · 0 comments
GoogleCodeExporter commented
According to documentation:
"CommittedButStillApplyingException is thrown when the write or transaction was
committed,
but some entities or index rows may not have been fully updated.
Those updates should automatically be applied soon.
You can roll them forward immediately by reading one of the entities inside a
transaction."
transactOnce should supress this exception.
version: 4.0rc2
Original issue reported on code.google.com by simplex....@gmail.com on 18 Dec 2013 at 3:15