[jira] [Comment Edited] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

["Apurva Mehta (JIRA)" <ji...@apache.org>]

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

Apurva Mehta edited comment on KAFKA-5366 at 6/5/17 6:59 PM:
-------------------------------------------------------------

[~ijuma] I originally marked this as a 'Major' item for 0.11.0.1, but am upgrading it to a blocker for 0.11.0.0 . 

The reason is that with these improvements, we are testing a behavior which would be used at the core of streams EOS (reading and writing transactionally and concurrently at the tail of the log). If this behavior doesn't work, streams EOS won't work.

So we need these upgraded tests to pass (have filed KAFKA-5375 and KAFKA-5376 to fix the failures), and then we can merge this. Let me know if  you have any objections.


was (Author: apurva):
[~ijuma] I originally marked this as a 'Major' item for 0.11.0.1, but am upgrading it to a blocker for 0.11.0.0 . 

The reason is that with these improvements, we are testing a behavior which would be used at the core of streams EOS (reading and writing transactionally and concurrently at the tail of the log). If this behavior doesn't work, streams EOS won't work.

So we need this upgraded tests to pass (have filed KAFKA-5375 and KAFKA-5376 to fix the failures), and then we can merge this. Let me know if  you have any objections.

> Add cases for concurrent transactional reads and writes in system tests
> -----------------------------------------------------------------------
>
>                 Key: KAFKA-5366
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5366
>             Project: Kafka
>          Issue Type: Test
>    Affects Versions: 0.11.0.0
>            Reporter: Apurva Mehta
>            Assignee: Apurva Mehta
>            Priority: Blocker
>              Labels: exactly-once
>             Fix For: 0.11.0.0
>
>
> Currently the transactions system test does a transactional copy while bouncing brokers and clients, and then does a verifying read on the output topic to ensure that it exactly matches the input. 
> We should also have a transactional consumer reading the tail of the output topic as the writes are happening, and then assert that the values _it_ reads also exactly match the values in the source topics. 
> This test really exercises the abort index, and we don't have any of them in the system or integration tests right now. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)