[
https://issues.apache.org/jira/browse/INLONG-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388520#comment-17388520
]
Charles Zhang commented on INLONG-72:
-------------------------------------
TubeMQ has updated to InLong, it will support more MQ services, like
Kafka、Pulsar, TubeMQ will not consider the compatibility of other MQ.
the detail at
https://issues.apache.org/jira/browse/INLONG-720
https://issues.apache.org/jira/browse/INLONG-721
> Support Kafka Compatible Protocol in TubeMQ
> -------------------------------------------
>
> Key: INLONG-72
> URL: https://issues.apache.org/jira/browse/INLONG-72
> Project: Apache InLong
> Issue Type: New Feature
> Reporter: Junping Du
> Priority: Major
>
> The Kafka protocol is general used in MQ area, and Apache Pulsar (another MQ)
> did work to support it. TubeMQ should do the same thing - given there are
> only six core client requests APIs.
> *Metadata* - Describes the currently available brokers, their host and port
> information, and gives information about which broker hosts which partitions.
> *Send* - Send messages to a broker
> *Fetch* - Fetch messages from a broker, one which fetches data, one which
> gets cluster metadata, and one which gets offset information about a topic.
> *Offsets* - Get information about the available offsets for a given topic
> partition.
> *Offset Commit* - Commit a set of offsets for a consumer group
> *Offset Fetch* - Fetch a set of offsets for a consumer group
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
