You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Balaji Rao (Jira)" <ji...@apache.org> on 2022/07/12 14:03:00 UTC

[jira] [Updated] (KAFKA-14070) Improve documentation for queryMetadataForKey

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

Balaji Rao updated KAFKA-14070:
-------------------------------
    Summary: Improve documentation for queryMetadataForKey  (was: queryMetadataForKey)

> Improve documentation for queryMetadataForKey
> ---------------------------------------------
>
>                 Key: KAFKA-14070
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14070
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 3.2.0
>            Reporter: Balaji Rao
>            Priority: Minor
>
> When using key-value state stores with Processor API, one can add key-value state stores of arbitrary key types. This could lead to the method `queryMetadataForKey` in `KafkaStreams` to be used with incorrect expectations.
> In my understanding, `queryMetadataForKey` uses the source topics of the processor connected to the store to return the `KeyQueryMetadata`. This means that it could provide "incorrect" answers when used with key-value stores of arbitrary key types. The description of the method should be improved to make users aware of this pitfall.



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