Auditing broken for entities using optimistic locking via version properties in reactive mongo [DATAMONGO-2150]

[spring-projects-issues]

Mike Pellegrini opened DATAMONGO-2150 and commented

Entity class A has Id, version and auditing fields:

 

@Data
@Document
public class A {
  @Id String id;
  @Version Long version;
  @CreatedDate Instant createdAt;
  @LastModifiedDate Instant lastModifiedAt;
}

 

and I tried to save new A,

reactiveCrudRepository.save(new A());

but document stored in mongodb doesn't have createdAt field populaed. (lastModifiedAt field is populated)

There is a similar Jira DATAMONGO-2139 where this was fixed. But it still is broken in the reactive implementation.

 

---

Affects: 2.2 M1 (Moore), 2.1.3 (Lovelace SR3)

Issue Links:

• DATAMONGO-2158 MongoDB Reactive transactions do not support auditing
  ("is duplicated by")

• DATAMONGO-2147 @EnableMongoAuditing is not working correctly if @Version is used on entity
  ("is duplicated by")

• DATAMONGO-2139 Auditing broken for entities using optimistic locking via version properties

• DATAMONGO-2586 Add support for reactive auditing
  ("is superseded by")

Referenced from: pull request #627

Backported to: 2.1.4 (Lovelace SR4)

1 votes, 3 watchers

[spring-projects-issues]

Mike Pellegrini commented

Thanks for the quick turnaround.  Just confirming that this is working for me now with the build snapshots

[spring-projects-issues]

lloistborn commented

Hi Mike Pellegrini do we have update on this?