pjfanning opened a new pull request, #476: URL: https://github.com/apache/pekko-projection/pull/476
Now available under Apache License v2.0. Ports the non-grpc, non-r2dbc changes from [pjfanning/akka-projection](https://github.com/pjfanning/akka-projection) (1.4.x branch, SHA `90dbc3a4`) that were missing from this repo. ## Changes ### New file: `core/.../projection/internal/CanTriggerReplay.scala` A new internal trait that allows a projection source provider (specifically an `EventsBySliceQuery`) to signal that it supports replay triggering for a given persistence ID and sequence number. Used by `EventSourcedProvider` factories when the underlying query supports it. ### `core/.../projection/internal/SourceProviderAdapter.scala` Added `ScalaBySlicesSourceProviderAdapter` — adapts a Scala DSL `SourceProvider with BySlicesSourceProvider` to the Java DSL interface. Without this, a slice-based source created via the Scala API could not be bridged to the Java API. ### `eventsourced/.../scaladsl/EventSourcedProvider.scala` The `eventsBySlices` factory that accepts a raw query now checks whether the query implements `CanTriggerReplay`. If so, the returned `SourceProvider` also mixes in `CanTriggerReplay`, delegating to the query — enabling downstream consumers (e.g. offset stores) to trigger event replay for specific persistence IDs. ### `eventsourced/.../javadsl/EventSourcedProvider.scala` Same `CanTriggerReplay` mixin wired in for the Java API counterpart. ## What was intentionally skipped - **gRPC and R2DBC modules** — excluded per requirements (changes are large) - **Scala 3 compatibility changes** (`ProjectionContextImpl` private constructor + `withGroupSize`) — already present in this repo Agent-Logs-Url: https://github.com/pjfanning/incubator-pekko-projection/sessions/5ed34547-44f6-4f51-ad38-2ce0babfb1be -- 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]
