You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Sanil Jain (JIRA)" <ji...@apache.org> on 2018/05/30 22:42:00 UTC
[jira] [Updated] (SAMZA-1737) SystemProducers in
TaskInstanceCollector do not resolve logical name (stream-id) to a
physicalName if the configs for physical name are set
[ https://issues.apache.org/jira/browse/SAMZA-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanil Jain updated SAMZA-1737:
------------------------------
Description:
- A samza configuration streams.stream-id.samza.physical.name assigns a physical name which for example is actual name of a kafka topic
- If this config is set, the resolution of stream-id -> physicalName should occur in SystemProducers before TaskInstanceCollector dispatches the message
- Currently this works because most of the jobs use same stream-id and physicalName
Link: https://docs.google.com/document/d/1YQkhBwPw3Fl1NPt2rPQk2luCvaq0x4-BU1XqvfhazQk/edit?usp=sharing
was:
- A samza configuration streams.stream-id.samza.physical.name assigns a physical name which for example is actual name of a kafka topic
- If this config is set, the resolution of stream-id -> physicalName should occur in SystemProducers before TaskInstanceCollector dispatches the message
- Currently this works because most of the jobs use same stream-id and physicalName
> SystemProducers in TaskInstanceCollector do not resolve logical name (stream-id) to a physicalName if the configs for physical name are set
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SAMZA-1737
> URL: https://issues.apache.org/jira/browse/SAMZA-1737
> Project: Samza
> Issue Type: Bug
> Reporter: Sanil Jain
> Assignee: Sanil Jain
> Priority: Major
>
> - A samza configuration streams.stream-id.samza.physical.name assigns a physical name which for example is actual name of a kafka topic
> - If this config is set, the resolution of stream-id -> physicalName should occur in SystemProducers before TaskInstanceCollector dispatches the message
> - Currently this works because most of the jobs use same stream-id and physicalName
>
> Link: https://docs.google.com/document/d/1YQkhBwPw3Fl1NPt2rPQk2luCvaq0x4-BU1XqvfhazQk/edit?usp=sharing
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)