I'm seeing inconsistency in transactions behavior between Cloud Datastore and Cloud Firestore running in Datastore mode. The sample code below runs fine when working with Cloud Datastore, but fails when working with Cloud Firestore running in Datastore mode.
import com.google.cloud.datastore.Datastore;
import com.google.cloud.datastore.DatastoreOptions;
import com.google.cloud.datastore.FullEntity;
import com.google.cloud.datastore.IncompleteKey;
import com.google.cloud.datastore.Transaction;
public class TransactionTest {
public static void main(String[] args) {
//change it to a project ID that has plain old Datastore and then try again
//with a different project that has Firestore running in Datastore mode.
final String projectId = "xxx-xxx";
Datastore datastore = DatastoreOptions.newBuilder().setProjectId(projectId).build()
.getService();
IncompleteKey incompleteKey = datastore.newKeyFactory().setKind("TransactionTest").newKey();
FullEntity<IncompleteKey> fullEntity = FullEntity.newBuilder().setKey(incompleteKey)
.set("name", "Bob").build();
com.google.cloud.datastore.Entity entity = datastore.add(fullEntity);
Transaction t1 = datastore.newTransaction();
try {
com.google.cloud.datastore.Entity entity2 = t1.get(entity.getKey());
update(entity, datastore);
t1.commit();
System.out.println("t1 is committed successfully");
} finally {
if (t1.isActive()) {
t1.rollback();
}
}
}
private static void update(com.google.cloud.datastore.Entity entity, Datastore datastore) {
Transaction t2 = datastore.newTransaction();
try {
t2.update(entity);
t2.commit();
System.out.println("t2 is committed successfully");
} finally {
if (t2.isActive()) {
t2.rollback();
}
}
}
}
Running this code against good old Datastore completes normally and I get the below printed to the console:
t2 is committed successfully
t1 is committed successfully
However, running this against a different project_id, which has Firestore running in Datastore mode, produces the below exception, after running for about a minute:
Exception in thread "main" com.google.cloud.datastore.DatastoreException: The referenced transaction has expired or is no longer valid.
at com.google.cloud.datastore.spi.v1.HttpDatastoreRpc.translate(HttpDatastoreRpc.java:129)
at com.google.cloud.datastore.spi.v1.HttpDatastoreRpc.translate(HttpDatastoreRpc.java:114)
at com.google.cloud.datastore.spi.v1.HttpDatastoreRpc.rollback(HttpDatastoreRpc.java:173)
at com.google.cloud.datastore.DatastoreImpl$6.call(DatastoreImpl.java:530)
at com.google.cloud.datastore.DatastoreImpl$6.call(DatastoreImpl.java:527)
at com.google.api.gax.retrying.DirectRetryingExecutor.submit(DirectRetryingExecutor.java:89)
at com.google.cloud.RetryHelper.run(RetryHelper.java:74)
at com.google.cloud.RetryHelper.runWithRetries(RetryHelper.java:51)
at com.google.cloud.datastore.DatastoreImpl.rollback(DatastoreImpl.java:527)
at com.google.cloud.datastore.DatastoreImpl.rollbackTransaction(DatastoreImpl.java:522)
at com.google.cloud.datastore.TransactionImpl.rollback(TransactionImpl.java:120)
at com.jmethods.catatumbo.TransactionTest.main(TransactionTest.java:30)
Caused by: com.google.datastore.v1.client.DatastoreException: The referenced transaction has expired or is no longer valid., code=INVALID_ARGUMENT
at com.google.datastore.v1.client.RemoteRpc.makeException(RemoteRpc.java:226)
at com.google.datastore.v1.client.RemoteRpc.makeException(RemoteRpc.java:275)
at com.google.datastore.v1.client.RemoteRpc.call(RemoteRpc.java:186)
at com.google.datastore.v1.client.Datastore.rollback(Datastore.java:111)
at com.google.cloud.datastore.spi.v1.HttpDatastoreRpc.rollback(HttpDatastoreRpc.java:171)
... 9 more
Any idea why this difference? Which one is behaving correctly, Datastore or Firestore in Datastore mode?
I'm seeing inconsistency in transactions behavior between Cloud Datastore and Cloud Firestore running in Datastore mode. The sample code below runs fine when working with Cloud Datastore, but fails when working with Cloud Firestore running in Datastore mode.
Running this code against good old Datastore completes normally and I get the below printed to the console:
However, running this against a different project_id, which has Firestore running in Datastore mode, produces the below exception, after running for about a minute:
Any idea why this difference? Which one is behaving correctly, Datastore or Firestore in Datastore mode?