You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Apurva Mehta (JIRA)" <ji...@apache.org> on 2017/06/02 07:07:04 UTC
[jira] [Updated] (KAFKA-5366) Add cases for concurrent
transactional reads and writes in system tests
[ https://issues.apache.org/jira/browse/KAFKA-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apurva Mehta updated KAFKA-5366:
--------------------------------
Description:
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.
was:
Currently the transactions system test does 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.
> 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
> Fix For: 0.11.1.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)