You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Sagar Rao (Jira)" <ji...@apache.org> on 2021/07/28 18:38:00 UTC

[jira] [Assigned] (KAFKA-12957) Refactor Streams Logical Plan Generation

     [ https://issues.apache.org/jira/browse/KAFKA-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sagar Rao reassigned KAFKA-12957:
---------------------------------

    Assignee: Sagar Rao

> Refactor Streams Logical Plan Generation
> ----------------------------------------
>
>                 Key: KAFKA-12957
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12957
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Guozhang Wang
>            Assignee: Sagar Rao
>            Priority: Major
>
> There is a general issue of Streams logical plan -> physical plan generation, where the physical processor nodes are generated at the parsing phase rather than the logical plan compilation phase. The former stage is agnostic to any user configurations while only the latter stage have access to it, and hence we would not generate physical processor nodes during the parsing phase (i.e. any code related to StreamsBuilder), but defer them to the logical plan phase (i.e. XXNode.writeToTopology). This has several issues such that many physical processor instantiation requires to access the configs, and hence we have to defer it to the `init` procedure of the node, which is scattered in many places from logical nodes to physical processors.
> This would be a big refactoring on Stream's logical plan generation, but I think it would worth to get this in a cleaner state.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)