[jira] [Assigned] (KAFKA-18054) Automatically detect missed configs needed by a topology

["Lorcan (Jira)" <ji...@apache.org>]

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

Lorcan reassigned KAFKA-18054:
------------------------------

    Assignee: Lorcan

> Automatically detect missed configs needed by a topology
> --------------------------------------------------------
>
>                 Key: KAFKA-18054
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18054
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>            Reporter: A. Sophie Blee-Goldman
>            Assignee: Lorcan
>            Priority: Major
>
> See umbrella ticket for problem summary.
> This ticket would help tackle the first issue and would be a signifciant improvement without requiring a KIP.
> Basically, we should help users avoid accidentally misconfiguring their application by setting one of the topology-specific configs in their StreamsConfig but only passing it into the KafkaStreams constructor and not into the topology where it actually is applied.
> We should be able to detect this case pretty easily: when the topology and application configs are passed into the KafkaStreams constructor, we just compare the topology's configs with the provided application configs and look for each of the topology-specific configs (see umbrella ticket for the list).
> If any of these configs were set by the user in the application configs but not set in the topology's configs, we can throw an exception.
> We should also log a warning if the config is set in both cases but have a different value.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)