[SAMZA-1834] Too many IDs for processors in Samza

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Yi Pan
• Created: 30/Aug/18 20:02
• Updated: 01/Sep/18 01:15

Description

Currently, we have many different places that we introduced "id"s that are essentially used to identify a single processor performing the stream processing logic:

• run.id in LocalApplicationRunner
• processorId from JobCoordinator
• containerId from environment vars when we launch LocalContainerRunner

It becomes super confusing and they all essentially serving the same purpose. It would be good to consolidate those "id"s in to one.

Issue Links

• is related to: 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