GCP Spanner transaction conflict scenarios when using Spring Data with optimistic locking
After trying multiple solutions online, I still can't figure this out... I'm getting frustrated with I'm working with a `TransactionConflictException` when attempting to save entities in Google Cloud Spanner while using Spring Data... My application is set up to utilize optimistic locking, but I keep getting this exception even for seemingly unrelated transactions. I've defined my entity like this: ```java @Entity @Table(name = "MyEntity") public class MyEntity { @PrimaryKey private String id; @Column(name = "name") private String name; @Version private Long version; // getters and setters } ``` When I attempt to save an entity with an existing `id`, I expect the optimistic locking mechanism to check the `version` field, but instead, I receive the following behavior: ``` com.google.api.gax.rpc.AlreadyExistsException: The transaction is aborted due to a conflict. ``` I've checked that I am correctly updating the `version` field before every save operation, and I also ensured that I am using the latest Spring Data Spanner version (1.3.0). Here’s how I’m performing the save: ```java @Service public class MyEntityService { @Autowired private MyEntityRepository repository; public void updateEntity(MyEntity entity) { repository.save(entity); } } ``` Multiple instances of my application are accessing the same Spanner instance, which I suspect could be contributing to the conflict. I've tried increasing the timeout settings and configured retry policies, but the scenario continues. Is there a best practice for handling optimistic locking with GCP Spanner in a concurrent environment? Any insights on how to avoid these transaction conflicts would be greatly appreciated! What's the best practice here? This is my first time working with Java LTS.