[
https://issues.apache.org/jira/browse/KAFKA-18206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911202#comment-17911202
]
Divij Vaidya commented on KAFKA-18206:
--------------------------------------
Jumping in to present an FYI with Embedded Cluster. When it is created by the
tests, we use MockTime initialized to when the cluster was created. But in
certain streams tests, we use actual Thread.Sleep (instead of incrementing the
mock time). This leads to a situation where the time on the cluster is waaay
behind the current time of test execution (ie clients have a time in future).
It doesn't matter in usual scenarios but I found this problematic when working
with constraints around create_time timestamp for messages. I will create a
separate Jira to fix this once I have a better understanding of the bug.
> EmbeddedKafkaCluster must set features
> --------------------------------------
>
> Key: KAFKA-18206
> URL: https://issues.apache.org/jira/browse/KAFKA-18206
> Project: Kafka
> Issue Type: Bug
> Components: streams, unit tests
> Reporter: David Jacot
> Assignee: Kuan Po Tseng
> Priority: Blocker
> Fix For: 4.0.0
>
>
> The EmbeddedKafkaCluster classes respectively used by Streams and Connect
> relies on
> KafkaClusterTestKit. We just found out that they do not set the features at
> all. They should.
>
> The other integration tests rely on classes wrapping KafkaClusterTestKit and
> they take care of setting the features. This is not ideal. I wonder whether
> we could push that functionality to KafkaClusterTestKit.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
