[jira] [Commented] (TUBEMQ-118) Provide MQ upstream and downstream supporting capabilities

["Guocheng Zhang (Jira)" <ji...@apache.org>]

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

Guocheng Zhang commented on TUBEMQ-118:
---------------------------------------

*Stage feedback: *

the requirement is being tracked and implemented in different sub requirements:

1. Access proxy provides: including support for different access protocols, such as http, kafka client, UDP client, etc., to access in the form of proxy

*see TUBEMQ-163 Flume sink for TubeMQ:* you can use this contribution to report data through Flume in different ways

2. Consumer capacity provision: including the existing component implementation codes of flink, spark and other centers, making open source contributions and forming supporting capabilities

*see TUBEMQ-197 and TUBEMQ-238: *you can use TubeMQ in flink and spark

3. Contribution of existing C/C++ SDK
*see ： *
C/C++ TUBEMQ-3
Go TUBEMQ-25
Python TUBEMQ-162
Rust TUBEMQ-164

4. Web page: The Web page is too old, if it can provide the rendering of the updated program, and it can support the new features of tubemq until now
*see TUBEMQ-137:*

5. Other supporting capacity contributions

> Provide MQ upstream and downstream supporting capabilities
> ----------------------------------------------------------
>
>                 Key: TUBEMQ-118
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-118
>             Project: Apache TubeMQ
>          Issue Type: Task
>            Reporter: Guocheng Zhang
>            Priority: Major
>              Labels: features
>             Fix For: 0.6.0
>
>
> Based on TubeMQ's upstream and downstream capabilities, forming supporting capabilities open source, avoiding repeated development by users
> 	
> 1. Access proxy provides: including support for different access protocols, such as http, kafka client, UDP client, etc., to access in the form of proxy
> 	
> 2. Consumer capacity provision: including the existing component implementation codes of flink, spark and other centers, making open source contributions and forming supporting capabilities
> 	
> 3. Contribution of existing C/C++ SDK
> 	
> 4. Web page: The Web page is too old, if it can provide the rendering of the updated program, and it can support the new features of tubemq until now
> 	
> 5. Other supporting capacity contributions



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