You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Boris Shkolnik (JIRA)" <ji...@apache.org> on 2018/10/09 23:31:00 UTC
[jira] [Commented] (SAMZA-1921) Upgrade SamzaKafkaSystemAdmin to
use latest AdminClient
[ https://issues.apache.org/jira/browse/SAMZA-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644238#comment-16644238 ]
Boris Shkolnik commented on SAMZA-1921:
---------------------------------------
As per [~yipan] suggestion, consider extracting metadataconsumer and admin client into a separate class for admin operations.
> Upgrade SamzaKafkaSystemAdmin to use latest AdminClient
> -------------------------------------------------------
>
> Key: SAMZA-1921
> URL: https://issues.apache.org/jira/browse/SAMZA-1921
> Project: Samza
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Priority: Major
>
> Currently it uses kafka.admin.AdminClient, whis is old and soon to be deprecated version.
> We need to move to org.apache.kafka.clients.admin.AdminClient (which uses Java).
> Among other things, it should give us a callback facility to synchnorize some async operations (like create and clear streams). After that we can rewrite create/clear stream for SamzaKafkaAdmin.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)