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

Qingsheng Ren commented on FLINK-22198:
---------------------------------------

Thanks [~lindong] for the investigation! Yes there are indeed some Kafka table 
test cases explicitly assigning record timestamp, such as this one[1]. These 
cases tests metadata column feature of Kafka sink table so I think we have to 
keep them. 

I would suggest to disable log deletion by setting Kafka broker conf 
{{log.retention.ms}} to -1 in KafkaTableTestBase. This will prevent records 
from being delete. I can submit a patch to fix this. 

[1] 
[https://github.com/apache/flink/blob/706cd677888312d2f71b498bf02447c750634d52/flink-connectors/flink-connector-kafka/src/test/java/org/apache/flink/streaming/connectors/kafka/table/KafkaTableITCase.java#L278]

> KafkaTableITCase hang.
> ----------------------
>
>                 Key: FLINK-22198
>                 URL: https://issues.apache.org/jira/browse/FLINK-22198
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka
>    Affects Versions: 1.14.0, 1.12.4
>            Reporter: Guowei Ma
>            Assignee: Qingsheng Ren
>            Priority: Blocker
>              Labels: pull-request-available, stale-blocker, test-stability
>             Fix For: 1.14.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=16287&view=logs&j=c5f0071e-1851-543e-9a45-9ac140befc32&t=1fb1a56f-e8b5-5a82-00a0-a2db7757b4f5&l=6625
> There is no any artifacts.



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

Reply via email to