[
https://issues.apache.org/jira/browse/SAMZA-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599445#comment-16599445
]
Yi Pan (Data Infrastructure) commented on SAMZA-1834:
-----------------------------------------------------
One more: the configuration key processor.id is defined in both
ApplicationConfig and JobConfig and only marked as deprecated in one class.
Also, there are many places where the processorId is accessed via either
ApplicationConfig or JobConfig. This is super confusing.
> Too many IDs for processors in Samza
> ------------------------------------
>
> Key: SAMZA-1834
> URL: https://issues.apache.org/jira/browse/SAMZA-1834
> Project: Samza
> Issue Type: Improvement
> Reporter: Yi Pan (Data Infrastructure)
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
