[
https://issues.apache.org/jira/browse/KAFKA-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383632#comment-17383632
]
Konstantine Karantasis commented on KAFKA-12994:
------------------------------------------------
Hi [~iekpo]. You mentioned on the dev mailing list that a PR was in the works
for this issue.
https://lists.apache.org/thread.html/r25f41514ae9751f260b5773abc039dfc828b00154297f20b4a14a151%40%3Cdev.kafka.apache.org%3E
However, I don't see a link on this issue here yet.
We are now past code freeze for 3.0. We'll need to either get a PR for this
issue, review soon and possibly accept as a blocker or postpone for the next
release. Do you have an update you could share?
> Migrate all Tests to New API and Remove Suppression for Deprecation Warnings
> related to KIP-633
> -----------------------------------------------------------------------------------------------
>
> Key: KAFKA-12994
> URL: https://issues.apache.org/jira/browse/KAFKA-12994
> Project: Kafka
> Issue Type: Improvement
> Components: streams, unit tests
> Affects Versions: 3.0.0
> Reporter: Israel Ekpo
> Assignee: Israel Ekpo
> Priority: Blocker
> Labels: kip, kip-633
> Fix For: 3.0.0
>
>
> Due to the API changes for KIP-633 a lot of deprecation warnings have been
> generated in tests that are using the old deprecated APIs. There are a lot of
> tests using the deprecated methods. We should absolutely migrate them all to
> the new APIs and then get rid of all the applicable annotations for
> suppressing the deprecation warnings.
> The applies to all Java and Scala examples and tests using the deprecated
> APIs in the JoinWindows, SessionWindows, TimeWindows and SlidingWindows
> classes.
>
> This is based on the feedback from reviewers in this PR
>
> https://github.com/apache/kafka/pull/10926
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
