pjfanning opened a new issue, #525: URL: https://github.com/apache/pekko-persistence-r2dbc/issues/525
Follow-up from the review of #510. In Pekko core 2.0.0-M5 (apache/pekko#3650), `SerializedEvent` is serialized by the `FilteredPayload` serializer with manifest `S`, as a `PersistentPayload` wrapping the inner serializer id, manifest and bytes. `R2dbcJournal.asyncWriteMessages` serializes each event with `serialization.serialize(event)`, so a `SerializedEvent` would be stored with the `FilteredPayload` serializer id, manifest `S`, and the wrapped bytes. It should instead store the inner serializer id, manifest and bytes directly, so the row looks the same as if the original event had been serialized normally. Queries can then deserialize it without going through the wrapper, and the row stays readable by tools that don't know about `SerializedEvent`. This needs the dependency on Pekko core to be bumped to 2.0.0-M5 or later (currently 2.0.0-M4). Until then, #510 checks the manifest as well as the serializer id, so a manifest `S` row is not mistaken for a `FilteredPayload`. Refs #510, apache/pekko#3650 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
