[
https://issues.apache.org/jira/browse/KAFKA-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hashan Gayasri Udugahapattuwa updated KAFKA-7233:
-------------------------------------------------
Description:
When querying externally from via the
[ReadOnlyKeyValueStore|https://github.com/apache/kafka/blob/1.0/streams/src/main/java/org/apache/kafka/streams/state/ReadOnlyKeyValueStore.java]
API (Interactive Queries), the InMemoryKeyValueStore does not protect its
internal map from concurrent reads and writes which may produce incorrect
results to the ReadOnlyKeyValueStore API. Note that reads(query thread) and
writes(stream thread) can happen concurrently.
EDIT: This issue is invalid as the implementation behaves as intended.
was:When querying externally from via the
[ReadOnlyKeyValueStore|https://github.com/apache/kafka/blob/1.0/streams/src/main/java/org/apache/kafka/streams/state/ReadOnlyKeyValueStore.java]
API (Interactive Queries), the InMemoryKeyValueStore does not protect its
internal map from concurrent reads and writes which may produce incorrect
results to the ReadOnlyKeyValueStore API. Note that reads(query thread) and
writes(stream thread) can happen concurrently.
> InMemoryKeyValueStore is not thread-safe for Interactive Queries
> ----------------------------------------------------------------
>
> Key: KAFKA-7233
> URL: https://issues.apache.org/jira/browse/KAFKA-7233
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 1.1.0, 2.0.0
> Environment: Fedora 27
> Reporter: Hashan Gayasri Udugahapattuwa
> Priority: Critical
>
> When querying externally from via the
> [ReadOnlyKeyValueStore|https://github.com/apache/kafka/blob/1.0/streams/src/main/java/org/apache/kafka/streams/state/ReadOnlyKeyValueStore.java]
> API (Interactive Queries), the InMemoryKeyValueStore does not protect its
> internal map from concurrent reads and writes which may produce incorrect
> results to the ReadOnlyKeyValueStore API. Note that reads(query thread) and
> writes(stream thread) can happen concurrently.
>
> EDIT: This issue is invalid as the implementation behaves as intended.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
