Klaus

When using reactive sagas, duplicate message detector causes consumer to crash on a duplicate

2

This is because the doWithMessage() method inside ReactiveSqlTableBasedDuplicateMessageDetector class runs inside a transaction: ``` return Mono.defer(() -> isDuplicate(subscriberIdAndMessage) .flatMap(dup -> { if (dup) return Mono.empty(); else return Mono.from(processingFlow); })).as(transactionalOperator::transactional); ```...

ReactiveSqlQueryRow expects boolean fields to be Int

1

When migrating from the non-reactive Eventuate stack to reactive, then all the examples and SQLs had the saga_instance fields as boolean, which means the reactive stack won't work as expected,...

When using reactive sagas, the data is not persisted as expected

2

I'm not sure if this is intentional or not, but with non-reactive sagas we're able to update the saga data in the reply handlers and it gets persisted automatically. Right...