Skip to content

KAFKA-10459: Document IQ APIs where order does not hold between stores #9251

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mjsax merged 2 commits into from
Sep 22, 2020
Merged

KAFKA-10459: Document IQ APIs where order does not hold between stores #9251

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
13995b9
Document IQ APIs where order does not hold between stores
showuon Sep 4, 2020
c7f7c8f
Update streams/src/main/java/org/apache/kafka/streams/state/ReadOnlyW…
mjsax Sep 22, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions streams/src/main/java/org/apache/kafka/streams/state/ReadOnlyWindowStore.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,11 @@
* A window store that only supports read operations.
* Implementations should be thread-safe as concurrent reads and writes are expected.
*
* <p>Note: The current implementation of either forward or backward fetches on range-key-range-time does not
* obey the ordering when there are multiple local stores hosted on that instance. For example,
* if there are two stores from two tasks hosting keys {1,3} and {2,4}, then a range query of key [1,4]
* would return in the order of [1,3,2,4] but not [1,2,3,4] since it is just looping over the stores only.
*
* @param <K> Type of keys
* @param <V> Type of values
*/
Expand Down