[
https://issues.apache.org/jira/browse/KAFKA-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17566414#comment-17566414
]
Guozhang Wang commented on KAFKA-14070:
---------------------------------------
Hello [~balajirrao], thanks for filing this ticket. Could you provide a
specific example of key types that would break `queryMetadataForKey`? Note that
the function takes in a partitioner still to ask users to provide the
partitioner if possible to determine which partition contains the specific key.
> 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 to a topology. 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)
