[
https://issues.apache.org/jira/browse/KAFKA-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson updated KAFKA-5366:
-----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 3217
[https://github.com/apache/kafka/pull/3217]
> 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)
