Sure I’ll add standalone scenario. On Sat, 18 Feb 2023 at 15:01, Matthew Benedict de Detrich <[email protected]> wrote:
> > My worry is around lines like > > https://github.com/apache/incubator-pekko/blob/864ee821b99799a08392c2f3c143b40cecfda6c1/persistence/src/main/protobuf/MessageFormats.proto#L16 > where the Pekko specific package name appears. > > So I did some primitive research on this when I did the package rename in > pekko some time back and from what I gathered it should be a non issue > because the java_package is not something that is sent over the wire, it's > only used when generating the source files for the client. > > Would be great if someone can confirm/deny this. > > On Sat, Feb 18, 2023 at 2:58 PM PJ Fanning <[email protected]> wrote: > > > Thanks Seeta. > > > > If you have time to write a standalone scenario, that would be great. > > Maybe a Github project that imports akka-persistence and > > pekko-persistence. We can look later at adding similar test scenarios > > to the pekko build. > > > > My worry is around lines like > > > > > https://github.com/apache/incubator-pekko/blob/864ee821b99799a08392c2f3c143b40cecfda6c1/persistence/src/main/protobuf/MessageFormats.proto#L16 > > where the Pekko specific package name appears. > > > > On Sat, 18 Feb 2023 at 14:52, seetaramayya vadali <[email protected]> > > wrote: > > > > > > As far as I understand, *akka-persistence* should be compatible with > > > *pekko-persistence*. > > > > > > If I am not mistaken, > > > > > > 1. Messages are serialized with AtomicWrite > > > < > > > https://github.com/apache/incubator-pekko/blob/864ee821b99799a08392c2f3c143b40cecfda6c1/persistence/src/main/protobuf/MessageFormats.proto#L42 > > > > > > which > > > has payload > > > 2. The payload needs to be serialized by user given serializer > > > (documentation about serialization > > > < > > > https://doc.akka.io/docs/akka/current/typed/persistence.html#serialization > > > > > > ) > > > > > > Of course this is the theory, I can write a small project that > > > serializes with akka-persistence and expect it to work with > > > pekko-persistence as well. Or writing test case with akka-persistence > and > > > pekko-persistence would much better (by adding test dependency on > > > akka-persistence) > > > > > > In our company we are using akka-persistence in more than 2 or 3 > > projects, > > > so I can test it with the release candidates (unfortunately our > > > applications also depends on alpakaka that means I can not upgrade it > > until > > > pekko-connectors <https://github.com/apache/incubator-pekko-connectors > > > > are > > > ready) > > > > > > On Fri, Feb 17, 2023 at 5:27 PM PJ Fanning <[email protected]> > wrote: > > > > > > > I must admit to never really having used akka-persistence. I guess we > > > > would like pekko-persistence to be able to handle any data that has > > been > > > > durably persisted using akka-persistence. > > > > > > > > Does anyone know what in practice is stored in the > > akka-persistence-jdbc > > > > lib? Does the data stored in the database include things like Fully > > > > Qualified Class Names or key value pairs that might include key names > > > > prefixed with 'akka'? As we go along, pekko-persistence-jdbc is going > > to > > > > change any values that include 'akka' in its data. > > > > > > > > It could be that the durable data that is stored avoids these issues > - > > so > > > > that there would be little issue in someone switching from Akka to > > Pekko. > > > > What I'm interested in is hearing from people with more experience > > with the > > > > Persistence libs. > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > -- > > > Regards, > > > Seeta Ramayya Vadali > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > -- > > Matthew de Detrich > > *Aiven Deutschland GmbH* > > Immanuelkirchstraße 26, 10405 Berlin > > Amtsgericht Charlottenburg, HRB 209739 B > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > *m:* +491603708037 > > *w:* aiven.io *e:* [email protected] > -- Regards, Seeta Ramayya Vadali
