[jira] [Commented] (KAFKA-9224) State store should not see uncommitted transaction result

["John Roesler (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-9224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085121#comment-17085121 ] 

John Roesler commented on KAFKA-9224:
-------------------------------------

Hi [~bchen225242] , this ticket has just come to my attention again. In the description, it says that some writes to the store may not be guaranteed to happen after the transaction commits, but it's not clear to me how that can be the case. Since this is the whole basis for this feature request, can you elaborate, please?

> 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 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)