[
https://issues.apache.org/jira/browse/KAFKA-10459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Chen reassigned KAFKA-10459:
---------------------------------
Assignee: Luke Chen
> Document IQ APIs where order does not hold between stores
> ---------------------------------------------------------
>
> Key: KAFKA-10459
> URL: https://issues.apache.org/jira/browse/KAFKA-10459
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Jorge Esteban Quilcate Otoya
> Assignee: Luke Chen
> Priority: Minor
>
> From [https://github.com/apache/kafka/pull/9138#discussion_r480469688] :
>
> This is out of the scope of this PR, but I'd like to point out that the
> current IQ does not actually 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 looping
> over the stores only. This would be the case for either forward or backward
> fetches on range-key-range-time.
> For single key time range fetch, or course, there's no such issue.
> I think it worth documenting this for now until we have a fix (and actually
> we are going to propose something soon).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
