Yicong-Huang opened a new issue, #4948: URL: https://github.com/apache/texera/issues/4948
### Task Summary The project migrated from Akka to Pekko, but several internal Scala identifiers still carry the `Akka` prefix even though they wrap Pekko APIs. Rename them so the source matches the runtime: - `AkkaConfig` → `PekkoConfig` (`common/config/.../config/AkkaConfig.scala`, with `akkaConfig` method → `pekkoConfig`) - `AkkaActorService` → `PekkoActorService` (`amber/.../architecture/common/AkkaActorService.scala`) - `AkkaActorRefMappingService` → `PekkoActorRefMappingService` (same package) - `AkkaMessageTransferService` → `PekkoMessageTransferService` (same package) - Method/parameter names: `akkaConfig`, `akkaActorService` → `pekkoConfig`, `pekkoActorService` Inventory across 26 .scala files: `AkkaActorService` ×20, `akkaConfig` ×17, `AkkaActorRefMappingService` ×17, `AkkaMessageTransferService` ×7, `akkaActorService` ×4, `AkkaConfig` ×3. No string-literal config keys are affected (`cluster.conf` already uses `pekko.*`); pure Scala rename. The intentional `"akka"` comment in `DeployStrategiesSpec.scala` (which contrasts pekko vs akka address strings) stays. ### Task Type - [x] Refactor / cleanup -- 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]
