[
https://issues.apache.org/jira/browse/KAFKA-9224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boyang Chen updated KAFKA-9224:
-------------------------------
Description: Currently under EOS, the uncommitted write could be reflected
in the state store before the ongoing transaction is finished. This means
interactive query could see uncommitted data within state store which is not
ideal for users relying on state stores for strong consistency. Ideally, we
should have an option to include state store commit as part of ongoing
transaction, however an immediate step towards a better reasoned system is to
`write after transaction commit`, which means we always buffer data within
stream cache for EOS until the ongoing transaction is committed. (was:
Currently under EOS, the write to state store is not guaranteed to happen after
the ongoing transaction is finished. This means interactive query could see
uncommitted data within state store which is not ideal for users relying on
state stores for strong consistency. Ideally, we should have an option to
include state store commit as part of ongoing transaction, however an immediate
step towards a better reasoned system is to `write after transaction commit`,
which means we always buffer data within stream cache for EOS until the ongoing
transaction is committed.)
> State store should not see uncommitted transaction result
> ---------------------------------------------------------
>
> Key: KAFKA-9224
> URL: https://issues.apache.org/jira/browse/KAFKA-9224
> Project: Kafka
> Issue Type: Improvement
> Reporter: Boyang Chen
> Assignee: Boyang Chen
> Priority: Major
>
> Currently under EOS, the uncommitted write could be reflected in the state
> store before the ongoing transaction is finished. This means interactive
> query could see uncommitted data within state store which is not ideal for
> users relying on state stores for strong consistency. Ideally, we should have
> an option to include state store commit as part of ongoing transaction,
> however an immediate step towards a better reasoned system is to `write after
> transaction commit`, which means we always buffer data within stream cache
> for EOS until the ongoing transaction is committed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
