Add support for auditing

[DVMaslov]

Entity:

@Table("orders")
public class OrdersEntity {
    @Id
    private Long id;
    private String type;
    private String description;
    @CreatedDate @Column("created_date")
    private LocalDateTime createdDate;
    private Integer amount;

   // getter setter
}

Repository:

interface OrderRepository : ReactiveCrudRepository<OrdersEntity, Long>

After repo.save(..) createdDate remains null

[mp911de]

Thanks for your ticket. Auditing is not yet supported. We first require an entity callback/lifecycle event infrastructure, see #215.

[sheiy]

Will support be provided in the future?

[mp911de]

Yes, auditing will come to Spring Data R2DBC. The reason we do not support auditing yet is that we do not have a reactive auditing infrastructure that is able to return the auditor.

[riba2101]

Would it be beneficial to port auditing as is and convert to reactive at some low level?

Update:
Was checking for envers alternatives and found javers/javers#972
It is an AOP approach but for the time being lacking R2DBC support. Would this be a viable replacement for envers?

[mp911de]

Depends on spring-projects/spring-data-commons#458.

[riba2101]

Btw, just a question, but wouldn't it make sense to be able to have a SQL database and be able to log audits to somewhere else like ELK?

would it make sense to create such auditing?

[mp911de]

The approach sounds similar to Hibernate Envers (while envers stores revisions in the SQL database). The generic EntityCallback infrastructure that will be introduced with #215 will allow you to write revisions to any kind of target as reactive callbacks operate on a Publisher level.