GitHub user pjfanning edited a comment on the discussion: Add new deleteObject functions to Persistence API
## Design Proposal for Pekko 1.1 changes * Add OutOfDateRevisionException and UnknownRevisionException to Pekko Persistence API * We will fail with OutOfDateRevisionException if the revision in the deleteObject is out of date * We will fail with UnknownRevisionException if the revision in the deleteObject call is ahead of the saved revision for the persistenceId * Change all 4 Persistence implementations (Cassandra, JDBC, R2DBC, DynamoDB) to respect the revision in deleteObject calls * We will use Java Reflection to create OutOfDateRevisionException and UnknownRevisionException to maintain Pekko 1.0 compatibility * If the Persistence v1.1 implementations are used with Pekko 1.0, they will not fail if the revision is out of date or unknown * Add migration/release notes for Pekko 1.1 specifying that `deleteObject(persistenceId, revision)` will respect the revision number and fail with OutOfDateRevisionException if the revision is not correct * the deprecated `deleteObject(persistenceId)` will not be changed and will continue to not fail if nothing is deleted wdyt @raboof @mdedetrich @Roiocam @kerr GitHub link: https://github.com/apache/pekko/discussions/1233#discussioncomment-8975620 ---- This is an automatically sent email for notifications@pekko.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@pekko.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
