The async TCP client currently only exposes 5 of the 9 sub-client interfaces that the blocking client has. Four interfaces are missing from the async side:
SystemClient (ping, getStats, getMe, getClient, getClients)
PersonalAccessTokensClient (create, list, delete, loginWithPersonalAccessToken)
PartitionsClient (createPartitions, deletePartitions)
ConsumerOffsetsClient (storeConsumerOffset, getConsumerOffset)
Additionally, the async ConsumerGroupsClient only has joinConsumerGroup and leaveConsumerGroup, while the blocking version also includes getConsumerGroup, getConsumerGroups, createConsumerGroup, and deleteConsumerGroup.
That's 17 methods total that exist in the blocking client with no async equivalent. The command codes and serialization logic already exist in the codebase, they just need async wrappers following the same pattern as the existing async sub-clients.
The async TCP client currently only exposes 5 of the 9 sub-client interfaces that the blocking client has. Four interfaces are missing from the async side:
SystemClient (ping, getStats, getMe, getClient, getClients)
PersonalAccessTokensClient (create, list, delete, loginWithPersonalAccessToken)
PartitionsClient (createPartitions, deletePartitions)
ConsumerOffsetsClient (storeConsumerOffset, getConsumerOffset)
Additionally, the async ConsumerGroupsClient only has joinConsumerGroup and leaveConsumerGroup, while the blocking version also includes getConsumerGroup, getConsumerGroups, createConsumerGroup, and deleteConsumerGroup.
That's 17 methods total that exist in the blocking client with no async equivalent. The command codes and serialization logic already exist in the codebase, they just need async wrappers following the same pattern as the existing async sub-clients.