Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Currently, the processorId creation function createProcessorId() is repeated in three different implementation of JobCoordinator: ZkJobCoordinator, PassthroughJobCoordinator, and AzureJobCoordinator.
Making the processId generation dependent on JobCoordinator is also not required now and each processor should know the durable processorId at the startup time, not depending on the creation of JobCoordinator. Hence, consolidating the createProcessorId() code to StreamProcessor and pass the processId to the JobCoordinator constructor should be the right thing to do.
Attachments
Issue Links
- is a child of
-
SAMZA-1789 Refactor the application runtime classes so that we have a unified pattern to write and launch applications in high- and low-level APIs in YARN and standalone
- Resolved
- links to