[jira] [Commented] (TUBEMQ-164) Rust SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142166#comment-17142166 ] lan.liang commented on TUBEMQ-164: -- Cool (y) > Rust SDK support in TubeMQ > -- > > Key: TUBEMQ-164 > URL: https://issues.apache.org/jira/browse/TUBEMQ-164 > Project: Apache TubeMQ > Issue Type: New Feature >Reporter: misakachen >Assignee: misakachen >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-247) Example run fail about Cannot resolve symbol 'protobuf'
[ https://issues.apache.org/jira/browse/TUBEMQ-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142080#comment-17142080 ] lan.liang commented on TUBEMQ-247: -- Yes,It's worked after i compile the project. I just think that example should not be used by the user to compile the project. This is confusing me. > Example run fail about Cannot resolve symbol 'protobuf' > --- > > Key: TUBEMQ-247 > URL: https://issues.apache.org/jira/browse/TUBEMQ-247 > Project: Apache TubeMQ > Issue Type: Wish > Components: Client >Reporter: lan.liang >Priority: Major > Attachments: 111.jpg > > > > I just want to `quick start ` for message producer and consumer. > > org.apache.tubemq.example.MAMessageProducerExample#main > > org.apache.tubemq.example.MessageConsumerExample#main > > But failed, it need to mvn install the project. I think that if you run the > client code, you should not need the server code, > > > BTW, What is the progress of the JAVA SDK now? Thanks! > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (TUBEMQ-248) Always loading of web console
[ https://issues.apache.org/jira/browse/TUBEMQ-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lan.liang resolved TUBEMQ-248. -- Resolution: Works for Me > Always loading of web console > - > > Key: TUBEMQ-248 > URL: https://issues.apache.org/jira/browse/TUBEMQ-248 > Project: Apache TubeMQ > Issue Type: Wish > Components: Portal >Reporter: lan.liang >Priority: Major > Attachments: Always loading.jpg > > > > deploy: > > docker run -p 8080:8080 -p 8000:8000 --name tubemq -d > apachetubemq/tubemq-all:latest > > And log have not found error log > > ``` > [INFO] 2020-06-21 12:47:18,196 [TMaster] [Rebalance End] 317 > [INFO] 2020-06-21 12:47:18,741 [TMaster] [ResetRebalance Start] 318, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:47:18,741 [TMaster] [ResetRebalance End] 318 > [INFO] 2020-06-21 12:47:48,196 [TMaster] [Rebalance Start] 319, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:47:48,196 [TMaster] [Rebalance End] 319 > [INFO] 2020-06-21 12:47:48,741 [TMaster] [ResetRebalance Start] 320, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:47:48,741 [TMaster] [ResetRebalance End] 320 > [INFO] 2020-06-21 12:48:18,197 [TMaster] [Rebalance Start] 321, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:18,197 [TMaster] [Rebalance End] 321 > [INFO] 2020-06-21 12:48:18,741 [TMaster] [ResetRebalance Start] 322, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:18,741 [TMaster] [ResetRebalance End] 322 > [INFO] 2020-06-21 12:48:48,199 [TMaster] [Rebalance Start] 323, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:48,199 [TMaster] [Rebalance End] 323 > [INFO] 2020-06-21 12:48:48,742 [TMaster] [ResetRebalance Start] 324, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:48,742 [TMaster] [ResetRebalance End] 324 > ``` > > Please remind me if I missed something -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-248) Always loading of web console
[ https://issues.apache.org/jira/browse/TUBEMQ-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142078#comment-17142078 ] lan.liang commented on TUBEMQ-248: -- My bad, the tubemq deployed by docker is not on the local machine, I can access it after trying to deploy the tubemq using docker on the local machine . [~gosonzhang] thank you for your reply! > Always loading of web console > - > > Key: TUBEMQ-248 > URL: https://issues.apache.org/jira/browse/TUBEMQ-248 > Project: Apache TubeMQ > Issue Type: Wish > Components: Portal >Reporter: lan.liang >Priority: Major > Attachments: Always loading.jpg > > > > deploy: > > docker run -p 8080:8080 -p 8000:8000 --name tubemq -d > apachetubemq/tubemq-all:latest > > And log have not found error log > > ``` > [INFO] 2020-06-21 12:47:18,196 [TMaster] [Rebalance End] 317 > [INFO] 2020-06-21 12:47:18,741 [TMaster] [ResetRebalance Start] 318, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:47:18,741 [TMaster] [ResetRebalance End] 318 > [INFO] 2020-06-21 12:47:48,196 [TMaster] [Rebalance Start] 319, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:47:48,196 [TMaster] [Rebalance End] 319 > [INFO] 2020-06-21 12:47:48,741 [TMaster] [ResetRebalance Start] 320, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:47:48,741 [TMaster] [ResetRebalance End] 320 > [INFO] 2020-06-21 12:48:18,197 [TMaster] [Rebalance Start] 321, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:18,197 [TMaster] [Rebalance End] 321 > [INFO] 2020-06-21 12:48:18,741 [TMaster] [ResetRebalance Start] 322, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:18,741 [TMaster] [ResetRebalance End] 322 > [INFO] 2020-06-21 12:48:48,199 [TMaster] [Rebalance Start] 323, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:48,199 [TMaster] [Rebalance End] 323 > [INFO] 2020-06-21 12:48:48,742 [TMaster] [ResetRebalance Start] 324, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:48,742 [TMaster] [ResetRebalance End] 324 > ``` > > Please remind me if I missed something -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [incubator-tubemq-website] erienniu edited a comment on pull request #40: [TUBEMQ-249] [website] RPC General Introduction.
erienniu edited a comment on pull request #40: URL: https://github.com/apache/incubator-tubemq-website/pull/40#issuecomment-647506494 @guangxuCheng ok. i will finish it in days.(if sth bother just close this mr, i will reopen when it is done.) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-tubemq-website] erienniu commented on pull request #40: [TUBEMQ-249] [website] RPC General Introduction.
erienniu commented on pull request #40: URL: https://github.com/apache/incubator-tubemq-website/pull/40#issuecomment-647506494 ok. i will finish it in days.(if sth bother just close this mr, i will reopen when it is done.) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-tubemq-website] guangxuCheng commented on pull request #40: [TUBEMQ-249] [website] RPC General Introduction.
guangxuCheng commented on pull request #40: URL: https://github.com/apache/incubator-tubemq-website/pull/40#issuecomment-647494619 Hi @erienniu , can you translate the whole article? It's strange that the language is not unified This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (TUBEMQ-249) [Website] Translate introduction of Client RPC
[ https://issues.apache.org/jira/browse/TUBEMQ-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng updated TUBEMQ-249: - Component/s: website > [Website] Translate introduction of Client RPC > -- > > Key: TUBEMQ-249 > URL: https://issues.apache.org/jira/browse/TUBEMQ-249 > Project: Apache TubeMQ > Issue Type: Improvement > Components: website >Reporter: Erien Deng >Assignee: Erien Deng >Priority: Major > Labels: pull-request-available > Original Estimate: 96h > Remaining Estimate: 96h > > [Website] Translate introduction of Client RPC > [https://tubemq.apache.org/en-us/docs/client_rpc.html]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TUBEMQ-249) [Website] Translate introduction of Client RPC
[ https://issues.apache.org/jira/browse/TUBEMQ-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated TUBEMQ-249: -- Labels: pull-request-available (was: ) > [Website] Translate introduction of Client RPC > -- > > Key: TUBEMQ-249 > URL: https://issues.apache.org/jira/browse/TUBEMQ-249 > Project: Apache TubeMQ > Issue Type: Improvement >Reporter: Erien Deng >Assignee: Erien Deng >Priority: Major > Labels: pull-request-available > Original Estimate: 96h > Remaining Estimate: 96h > > [Website] Translate introduction of Client RPC > [https://tubemq.apache.org/en-us/docs/client_rpc.html]] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [incubator-tubemq-website] erienniu opened a new pull request #40: [TUBEMQ-249] [website] RPC General Introduction.
erienniu opened a new pull request #40: URL: https://github.com/apache/incubator-tubemq-website/pull/40 [TUBEMQ-249] [website] RPC General Introduction. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (TUBEMQ-190) Start a local dev environment with embedded zookeeper
[
https://issues.apache.org/jira/browse/TUBEMQ-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
netroby closed TUBEMQ-190.
--
Resolution: Won't Fix
> Start a local dev environment with embedded zookeeper
> -
>
> Key: TUBEMQ-190
> URL: https://issues.apache.org/jira/browse/TUBEMQ-190
> Project: Apache TubeMQ
> Issue Type: Wish
>Reporter: netroby
>Priority: Major
>
> TubeMQ require zookeeper , if you start local dev environment, you may not
> want to set up zookeeper. so may we start embedded zookeeper?
>
> for example code : start emmbedded zookeeper
> {code:java}
> Properties startupProperties = ...
> QuorumPeerConfig quorumConfiguration = new QuorumPeerConfig();
> try {
> quorumConfiguration.parseProperties(startupProperties);
> } catch(Exception e) {
> throw new RuntimeException(e);
> }
> zooKeeperServer = new ZooKeeperServerMain();
> final ServerConfig configuration = new ServerConfig();
> configuration.readFrom(quorumConfiguration);
> new Thread() {
> public void run() {
> try {
> zooKeeperServer.runFromConfig(configuration);
> } catch (IOException e) {
> log.error("ZooKeeper Failed", e);
> }
> }
> }.start();{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (TUBEMQ-208) Change the test resource file's folder name to 'resources'
[ https://issues.apache.org/jira/browse/TUBEMQ-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] duli resolved TUBEMQ-208. - Resolution: Fixed > Change the test resource file's folder name to 'resources' > -- > > Key: TUBEMQ-208 > URL: https://issues.apache.org/jira/browse/TUBEMQ-208 > Project: Apache TubeMQ > Issue Type: Bug >Reporter: duli >Assignee: duli >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently, the the test resource files are located in 'resource' folder, > it's better to change their folder name to 'resources', and later we can put > all resource files into it. > > The related modules current file path are: > ../tubemq-core/src/test/resource > ../tubemq-server/src/test/resource -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (TUBEMQ-226) Add Windows startup scripts
[ https://issues.apache.org/jira/browse/TUBEMQ-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhou closed TUBEMQ-226. Finished, nothing else for this request. > Add Windows startup scripts > --- > > Key: TUBEMQ-226 > URL: https://issues.apache.org/jira/browse/TUBEMQ-226 > Project: Apache TubeMQ > Issue Type: Improvement >Reporter: Jeff Zhou >Assignee: Jeff Zhou >Priority: High > Labels: pull-request-available, ready-to-commit > Fix For: 0.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently there's no starting up on Windows platform, one has to set much to > start relating servers, while manually control each options and > specifications. Moreover, it could be difficult to maintain a stable runtime > configurations. > So here it's to add scripts to: > # Setting up the environment on Windows, which is also imported as parameter > settings; > # Startup Master node and Broker node, in the same way as it does in Linux > systems by shell scripts. > At last, it's best to be composed in plain command script (cmd), which could > be widely accepted on various versions of Windows, meanwhile, it's not so > complex to introduce Powershell. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (TUBEMQ-226) Add Windows startup scripts
[ https://issues.apache.org/jira/browse/TUBEMQ-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhou resolved TUBEMQ-226. -- Resolution: Fixed PR has been merged. > Add Windows startup scripts > --- > > Key: TUBEMQ-226 > URL: https://issues.apache.org/jira/browse/TUBEMQ-226 > Project: Apache TubeMQ > Issue Type: Improvement >Reporter: Jeff Zhou >Assignee: Jeff Zhou >Priority: High > Labels: pull-request-available, ready-to-commit > Fix For: 0.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently there's no starting up on Windows platform, one has to set much to > start relating servers, while manually control each options and > specifications. Moreover, it could be difficult to maintain a stable runtime > configurations. > So here it's to add scripts to: > # Setting up the environment on Windows, which is also imported as parameter > settings; > # Startup Master node and Broker node, in the same way as it does in Linux > systems by shell scripts. > At last, it's best to be composed in plain command script (cmd), which could > be widely accepted on various versions of Windows, meanwhile, it's not so > complex to introduce Powershell. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-247) Example run fail about Cannot resolve symbol 'protobuf'
[ https://issues.apache.org/jira/browse/TUBEMQ-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141757#comment-17141757 ] Guocheng Zhang commented on TUBEMQ-247: --- If it is built with source code, it needs to be recompiled once, and part of the code comes from the compilation result of protobuf (mainly considering that the protobuf version on the corresponding business machine is inconsistent with the version we issued) You need to install protobuf locally and then compile > Example run fail about Cannot resolve symbol 'protobuf' > --- > > Key: TUBEMQ-247 > URL: https://issues.apache.org/jira/browse/TUBEMQ-247 > Project: Apache TubeMQ > Issue Type: Wish > Components: Client >Reporter: lan.liang >Priority: Major > Attachments: 111.jpg > > > > I just want to `quick start ` for message producer and consumer. > > org.apache.tubemq.example.MAMessageProducerExample#main > > org.apache.tubemq.example.MessageConsumerExample#main > > But failed, it need to mvn install the project. I think that if you run the > client code, you should not need the server code, > > > BTW, What is the progress of the JAVA SDK now? Thanks! > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-248) Always loading of web console
[ https://issues.apache.org/jira/browse/TUBEMQ-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141752#comment-17141752 ] Guocheng Zhang commented on TUBEMQ-248: --- [~lan.liang] This is the Master's load balancing thread printing, your configuration is to do a load balancing check process every 30 seconds. From the log, there is no problem. > Always loading of web console > - > > Key: TUBEMQ-248 > URL: https://issues.apache.org/jira/browse/TUBEMQ-248 > Project: Apache TubeMQ > Issue Type: Wish > Components: Portal >Reporter: lan.liang >Priority: Major > Attachments: Always loading.jpg > > > > deploy: > > docker run -p 8080:8080 -p 8000:8000 --name tubemq -d > apachetubemq/tubemq-all:latest > > And log have not found error log > > ``` > [INFO] 2020-06-21 12:47:18,196 [TMaster] [Rebalance End] 317 > [INFO] 2020-06-21 12:47:18,741 [TMaster] [ResetRebalance Start] 318, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:47:18,741 [TMaster] [ResetRebalance End] 318 > [INFO] 2020-06-21 12:47:48,196 [TMaster] [Rebalance Start] 319, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:47:48,196 [TMaster] [Rebalance End] 319 > [INFO] 2020-06-21 12:47:48,741 [TMaster] [ResetRebalance Start] 320, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:47:48,741 [TMaster] [ResetRebalance End] 320 > [INFO] 2020-06-21 12:48:18,197 [TMaster] [Rebalance Start] 321, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:18,197 [TMaster] [Rebalance End] 321 > [INFO] 2020-06-21 12:48:18,741 [TMaster] [ResetRebalance Start] 322, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:18,741 [TMaster] [ResetRebalance End] 322 > [INFO] 2020-06-21 12:48:48,199 [TMaster] [Rebalance Start] 323, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:48,199 [TMaster] [Rebalance End] 323 > [INFO] 2020-06-21 12:48:48,742 [TMaster] [ResetRebalance Start] 324, > isMaster=true, isPrimaryNodeActive=false > [INFO] 2020-06-21 12:48:48,742 [TMaster] [ResetRebalance End] 324 > ``` > > Please remind me if I missed something -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-25) Go SDK support for TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141750#comment-17141750 ] Guocheng Zhang commented on TUBEMQ-25: -- [~tangcunzhou], I think it would be better to put the above part in the Description, so that everyone will see your plan first, and you can disassemble the sub-tasks according to your plan > Go SDK support for TubeMQ > - > > Key: TUBEMQ-25 > URL: https://issues.apache.org/jira/browse/TUBEMQ-25 > Project: Apache TubeMQ > Issue Type: New Feature >Reporter: Guocheng Zhang >Assignee: Cunzhou Tang >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-164) Rust SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141751#comment-17141751 ] Guocheng Zhang commented on TUBEMQ-164: --- Thanks [~misaka] > Rust SDK support in TubeMQ > -- > > Key: TUBEMQ-164 > URL: https://issues.apache.org/jira/browse/TUBEMQ-164 > Project: Apache TubeMQ > Issue Type: New Feature >Reporter: misakachen >Assignee: misakachen >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141748#comment-17141748 ] Guocheng Zhang commented on TUBEMQ-3: - Thanks! I want to do the development of some of the modules, first I will understand what your thoughts, then I will claim the related sub-tasks. > C++ SDK support in TubeMQ > - > > Key: TUBEMQ-3 > URL: https://issues.apache.org/jira/browse/TUBEMQ-3 > Project: Apache TubeMQ > Issue Type: New Feature >Reporter: zhangguocheng >Assignee: charleli >Priority: Normal > Attachments: TubeMQCpp.png > > > I will contribute the SDK of C + +, which is currently being sorted out. > Without changing the server-side interaction protocol, the semantics will be > the same as the Java implementation. > !TubeMQCpp.png! > Task > 1.io thread management > 2. Connection interface > 3. Connection pool management > 4.IO Buffer > 5.Futrue/Promise support > 6.Codec interface and TubeMQ interactive encoding > 7. Functionalization of service interface parameter settings > 8.Futrue service interface > 9.Master implementation, metadata acquisition and reading interface > 10. Consumer realization > 11. Producer Realization > 12.Client configuration > 13. Producer API package > 14. Consumer API package > Plan > Phase 1 (Available)-Implement basic functions and ensure unit test coverage > RPC support > Message consumption (pull mode) > Write message (synchronous) > Connection pool implementation-automatic reconnection of broken links, > automatic recovery of idle connections, shared according to sessionFactory > Test case and specification construction- > Phase 2 (Practical)-Realize the features of each function and be able to > adapt to a certain level of pressure measurement > Asynchronous production > Authentication and authentication && Prevent production and consumption > around the master > Accurately specify offset partition consumption > Frequency control > Consumption of multiple topics in a single group > Server filter consumption > Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, > realizing the latest function points according to priority > Inactive for more than specified minutes, mainly at the production end, such > as 3 minutes > Automatically shield the dead pixels, detect the dead pixels through the > algorithm, and automatically shield the fault Broker's data transmission > TLS > push consumption > > Featrue > 1.rpc development > Pre-research--asio development > Connection interface > Connection pool management-connection reuse, automatic reconnection of > broken links, automatic recovery of idle connections, sharing according to > sessionFactory > Streaming request support-based on serialNo > Futrue/Promise interface > Codec interface > Log > Config > Buffer > 2. Service interface development > API service interface, such as heartbeat package variable function > Request Futrue/Promise function encapsulation > Config: client, consumer, producer, Master, rpc > Message id > 3.Client > turn stop > Configuration input > Consumer API > Producer API > 4.Master > Authentication > Prevent the production and consumption around the Master: get the token from > the Master and update it to the local metadata > Metadata management: Topic, Group, Master > Master Heartbeat > 5. Consumer > User interface > Heartbeat support > pull consumption > Consumption of multiple topics in a single group > Authentication > Precisely specify offset partition consumption > 6. Producer > User interface > Simultaneous production > Asynchronous production > Load balancing algorithm: polling > Load balancing algorithm: hash > 7. Advanced features > Master disconnects and reconnects, traversing dns to obtain Master host IP > Limiting > Effectively-Once > tls:asio+openssl > Filter consumption > Inactive for more than the specified minutes, mainly at the production end, > for example 3 minutes > Fuse: Automatically shield the dead spots, detect the dead spots through the > algorithm, automatically shield the fault Broker's data transmission > Reporting time-consuming, failure; static weight (number of partitions), > dynamic weight > Connection pool management-automatic recovery of idle connections, shared > according to sessionFactory > Push consumptio > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Description: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. !TubeMQCpp.png! Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features of each function and be able to adapt to a certain level of pressure measurement Asynchronous production Authentication and authentication && Prevent production and consumption around the master Accurately specify offset partition consumption Frequency control Consumption of multiple topics in a single group Server filter consumption Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, realizing the latest function points according to priority Inactive for more than specified minutes, mainly at the production end, such as 3 minutes Automatically shield the dead pixels, detect the dead pixels through the algorithm, and automatically shield the fault Broker's data transmission TLS push consumption Featrue 1.rpc development Pre-research--asio development Connection interface Connection pool management-connection reuse, automatic reconnection of broken links, automatic recovery of idle connections, sharing according to sessionFactory Streaming request support-based on serialNo Futrue/Promise interface Codec interface Log Config Buffer 2. Service interface development API service interface, such as heartbeat package variable function Request Futrue/Promise function encapsulation Config: client, consumer, producer, Master, rpc Message id 3.Client turn stop Configuration input Consumer API Producer API 4.Master Authentication Prevent the production and consumption around the Master: get the token from the Master and update it to the local metadata Metadata management: Topic, Group, Master Master Heartbeat 5. Consumer User interface Heartbeat support pull consumption Consumption of multiple topics in a single group Authentication Precisely specify offset partition consumption 6. Producer User interface Simultaneous production Asynchronous production Load balancing algorithm: polling Load balancing algorithm: hash 7. Advanced features Master disconnects and reconnects, traversing dns to obtain Master host IP Limiting Effectively-Once tls:asio+openssl Filter consumption Inactive for more than the specified minutes, mainly at the production end, for example 3 minutes Fuse: Automatically shield the dead spots, detect the dead spots through the algorithm, automatically shield the fault Broker's data transmission Reporting time-consuming, failure; static weight (number of partitions), dynamic weight Connection pool management-automatic recovery of idle connections, shared according to sessionFactory Push consumptio was: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. !TubeMQCpp.png! Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features of each function and be able to adapt to a certain level of pressure measurement Asynchronous production
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Attachment: TubeMQCpp.png > C++ SDK support in TubeMQ > - > > Key: TUBEMQ-3 > URL: https://issues.apache.org/jira/browse/TUBEMQ-3 > Project: Apache TubeMQ > Issue Type: New Feature >Reporter: zhangguocheng >Assignee: charleli >Priority: Normal > Attachments: TubeMQCpp.png > > > I will contribute the SDK of C + +, which is currently being sorted out. > Without changing the server-side interaction protocol, the semantics will be > the same as the Java implementation. > !TubeMQCpp.png! > Task > 1.io thread management > 2. Connection interface > 3. Connection pool management > 4.IO Buffer > 5.Futrue/Promise support > 6.Codec interface and TubeMQ interactive encoding > 7. Functionalization of service interface parameter settings > 8.Futrue service interface > 9.Master implementation, metadata acquisition and reading interface > 10. Consumer realization > 11. Producer Realization > 12.Client configuration > 13. Producer API package > 14. Consumer API package > Plan > Phase 1 (Available)-Implement basic functions and ensure unit test coverage > RPC support > Message consumption (pull mode) > Write message (synchronous) > Connection pool implementation-automatic reconnection of broken links, > automatic recovery of idle connections, shared according to sessionFactory > Test case and specification construction- > Phase 2 (Practical)-Realize the features of each function and be able to > adapt to a certain level of pressure measurement > Asynchronous production > Authentication and authentication && Prevent production and consumption > around the master > Accurately specify offset partition consumption > Frequency control > Consumption of multiple topics in a single group > Server filter consumption > Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, > realizing the latest function points according to priority > Inactive for more than specified minutes, mainly at the production end, such > as 3 minutes > Automatically shield the dead pixels, detect the dead pixels through the > algorithm, and automatically shield the fault Broker's data transmission > TLS > push consumption > > Featrue > 1.rpc development > Pre-research--asio development > Connection interface > Connection pool management-connection reuse, automatic reconnection of > broken links, automatic recovery of idle connections, sharing according to > sessionFactory > Streaming request support-based on serialNo > Futrue/Promise interface > Codec interface > Log > Config > Buffer > 2. Service interface development > API service interface, such as heartbeat package variable function > Request Futrue/Promise function encapsulation > Config: client, consumer, producer, Master, rpc > Message id > 3.Client > turn stop > Configuration input > Consumer API > Producer API > 4.Master > Authentication > Prevent the production and consumption around the Master: get the token from > the Master and update it to the local metadata > Metadata management: Topic, Group, Master > Master Heartbeat > 5. Consumer > User interface > Heartbeat support > pull consumption > Consumption of multiple topics in a single group > Authentication > Precisely specify offset partition consumption > 6. Producer > User interface > Simultaneous production > Asynchronous production > Load balancing algorithm: polling > Load balancing algorithm: hash > 7. Advanced features > Master disconnects and reconnects, traversing dns to obtain Master host IP > Limiting > Effectively-Once > tls:asio+openssl > Filter consumption > Inactive for more than the specified minutes, mainly at the production end, > for example 3 minutes > Fuse: Automatically shield the dead spots, detect the dead spots through the > algorithm, automatically shield the fault Broker's data transmission > Reporting time-consuming, failure; static weight (number of partitions), > dynamic weight > Connection pool management-automatic recovery of idle connections, shared > according to sessionFactory > Push consumptio > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Attachment: (was: TubeMQCpp.png) > C++ SDK support in TubeMQ > - > > Key: TUBEMQ-3 > URL: https://issues.apache.org/jira/browse/TUBEMQ-3 > Project: Apache TubeMQ > Issue Type: New Feature >Reporter: zhangguocheng >Assignee: charleli >Priority: Normal > Attachments: TubeMQCpp.png > > > I will contribute the SDK of C + +, which is currently being sorted out. > Without changing the server-side interaction protocol, the semantics will be > the same as the Java implementation. > !TubeMQCpp.png! > Task > 1.io thread management > 2. Connection interface > 3. Connection pool management > 4.IO Buffer > 5.Futrue/Promise support > 6.Codec interface and TubeMQ interactive encoding > 7. Functionalization of service interface parameter settings > 8.Futrue service interface > 9.Master implementation, metadata acquisition and reading interface > 10. Consumer realization > 11. Producer Realization > 12.Client configuration > 13. Producer API package > 14. Consumer API package > Plan > Phase 1 (Available)-Implement basic functions and ensure unit test coverage > RPC support > Message consumption (pull mode) > Write message (synchronous) > Connection pool implementation-automatic reconnection of broken links, > automatic recovery of idle connections, shared according to sessionFactory > Test case and specification construction- > Phase 2 (Practical)-Realize the features of each function and be able to > adapt to a certain level of pressure measurement > Asynchronous production > Authentication and authentication && Prevent production and consumption > around the master > Accurately specify offset partition consumption > Frequency control > Consumption of multiple topics in a single group > Server filter consumption > Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, > realizing the latest function points according to priority > Inactive for more than specified minutes, mainly at the production end, such > as 3 minutes > Automatically shield the dead pixels, detect the dead pixels through the > algorithm, and automatically shield the fault Broker's data transmission > TLS > push consumption > > Featrue > 1.rpc development > Pre-research--asio development > Connection interface > Connection pool management-connection reuse, automatic reconnection of > broken links, automatic recovery of idle connections, sharing according to > sessionFactory > Streaming request support-based on serialNo > Futrue/Promise interface > Codec interface > Log > Config > Buffer > 2. Service interface development > API service interface, such as heartbeat package variable function > Request Futrue/Promise function encapsulation > Config: client, consumer, producer, Master, rpc > Message id > 3.Client > turn stop > Configuration input > Consumer API > Producer API > 4.Master > Authentication > Prevent the production and consumption around the Master: get the token from > the Master and update it to the local metadata > Metadata management: Topic, Group, Master > Master Heartbeat > 5. Consumer > User interface > Heartbeat support > pull consumption > Consumption of multiple topics in a single group > Authentication > Precisely specify offset partition consumption > 6. Producer > User interface > Simultaneous production > Asynchronous production > Load balancing algorithm: polling > Load balancing algorithm: hash > 7. Advanced features > Master disconnects and reconnects, traversing dns to obtain Master host IP > Limiting > Effectively-Once > tls:asio+openssl > Filter consumption > Inactive for more than the specified minutes, mainly at the production end, > for example 3 minutes > Fuse: Automatically shield the dead spots, detect the dead spots through the > algorithm, automatically shield the fault Broker's data transmission > Reporting time-consuming, failure; static weight (number of partitions), > dynamic weight > Connection pool management-automatic recovery of idle connections, shared > according to sessionFactory > Push consumptio > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Description: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. !TubeMQCpp.png! Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features of each function and be able to adapt to a certain level of pressure measurement Asynchronous production Authentication and authentication && Prevent production and consumption around the master Accurately specify offset partition consumption Frequency control Consumption of multiple topics in a single group Server filter consumption Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, realizing the latest function points according to priority Inactive for more than specified minutes, mainly at the production end, such as 3 minutes Automatically shield the dead pixels, detect the dead pixels through the algorithm, and automatically shield the fault Broker's data transmission TLS push consumption Featrue 1.rpc development Pre-research--asio development Connection interface Connection pool management-connection reuse, automatic reconnection of broken links, automatic recovery of idle connections, sharing according to sessionFactory Streaming request support-based on serialNo Futrue/Promise interface Codec interface Log Config Buffer 2. Service interface development API service interface, such as heartbeat package variable function Request Futrue/Promise function encapsulation Config: client, consumer, producer, Master, rpc Message id 3.Client turn stop Configuration input Consumer API Producer API 4.Master Authentication Prevent the production and consumption around the Master: get the token from the Master and update it to the local metadata Metadata management: Topic, Group, Master Master Heartbeat 5. Consumer User interface Heartbeat support pull consumption Consumption of multiple topics in a single group Authentication Precisely specify offset partition consumption 6. Producer User interface Simultaneous production Asynchronous production Load balancing algorithm: polling Load balancing algorithm: hash 7. Advanced features Master disconnects and reconnects, traversing dns to obtain Master host IP Limiting Effectively-Once tls:asio+openssl Filter consumption Inactive for more than the specified minutes, mainly at the production end, for example 3 minutes Fuse: Automatically shield the dead spots, detect the dead spots through the algorithm, automatically shield the fault Broker's data transmission Reporting time-consuming, failure; static weight (number of partitions), dynamic weight Connection pool management-automatic recovery of idle connections, shared according to sessionFactory Push consumptio was: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. !企业微信截图_15927950018183.png! Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features of each function and be able to adapt to a certain level of pressure measurement Asynchronous
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Attachment: (was: 企业微信截图_15927950018183.png) > C++ SDK support in TubeMQ > - > > Key: TUBEMQ-3 > URL: https://issues.apache.org/jira/browse/TUBEMQ-3 > Project: Apache TubeMQ > Issue Type: New Feature >Reporter: zhangguocheng >Assignee: charleli >Priority: Normal > Attachments: TubeMQCpp.png > > > I will contribute the SDK of C + +, which is currently being sorted out. > Without changing the server-side interaction protocol, the semantics will be > the same as the Java implementation. > !TubeMQCpp.png! > Task > 1.io thread management > 2. Connection interface > 3. Connection pool management > 4.IO Buffer > 5.Futrue/Promise support > 6.Codec interface and TubeMQ interactive encoding > 7. Functionalization of service interface parameter settings > 8.Futrue service interface > 9.Master implementation, metadata acquisition and reading interface > 10. Consumer realization > 11. Producer Realization > 12.Client configuration > 13. Producer API package > 14. Consumer API package > Plan > Phase 1 (Available)-Implement basic functions and ensure unit test coverage > RPC support > Message consumption (pull mode) > Write message (synchronous) > Connection pool implementation-automatic reconnection of broken links, > automatic recovery of idle connections, shared according to sessionFactory > Test case and specification construction- > Phase 2 (Practical)-Realize the features of each function and be able to > adapt to a certain level of pressure measurement > Asynchronous production > Authentication and authentication && Prevent production and consumption > around the master > Accurately specify offset partition consumption > Frequency control > Consumption of multiple topics in a single group > Server filter consumption > Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, > realizing the latest function points according to priority > Inactive for more than specified minutes, mainly at the production end, such > as 3 minutes > Automatically shield the dead pixels, detect the dead pixels through the > algorithm, and automatically shield the fault Broker's data transmission > TLS > push consumption > > Featrue > 1.rpc development > Pre-research--asio development > Connection interface > Connection pool management-connection reuse, automatic reconnection of > broken links, automatic recovery of idle connections, sharing according to > sessionFactory > Streaming request support-based on serialNo > Futrue/Promise interface > Codec interface > Log > Config > Buffer > 2. Service interface development > API service interface, such as heartbeat package variable function > Request Futrue/Promise function encapsulation > Config: client, consumer, producer, Master, rpc > Message id > 3.Client > turn stop > Configuration input > Consumer API > Producer API > 4.Master > Authentication > Prevent the production and consumption around the Master: get the token from > the Master and update it to the local metadata > Metadata management: Topic, Group, Master > Master Heartbeat > 5. Consumer > User interface > Heartbeat support > pull consumption > Consumption of multiple topics in a single group > Authentication > Precisely specify offset partition consumption > 6. Producer > User interface > Simultaneous production > Asynchronous production > Load balancing algorithm: polling > Load balancing algorithm: hash > 7. Advanced features > Master disconnects and reconnects, traversing dns to obtain Master host IP > Limiting > Effectively-Once > tls:asio+openssl > Filter consumption > Inactive for more than the specified minutes, mainly at the production end, > for example 3 minutes > Fuse: Automatically shield the dead spots, detect the dead spots through the > algorithm, automatically shield the fault Broker's data transmission > Reporting time-consuming, failure; static weight (number of partitions), > dynamic weight > Connection pool management-automatic recovery of idle connections, shared > according to sessionFactory > Push consumptio > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Attachment: TubeMQCpp.png > C++ SDK support in TubeMQ > - > > Key: TUBEMQ-3 > URL: https://issues.apache.org/jira/browse/TUBEMQ-3 > Project: Apache TubeMQ > Issue Type: New Feature >Reporter: zhangguocheng >Assignee: charleli >Priority: Normal > Attachments: TubeMQCpp.png > > > I will contribute the SDK of C + +, which is currently being sorted out. > Without changing the server-side interaction protocol, the semantics will be > the same as the Java implementation. > !企业微信截图_15927950018183.png! > Task > 1.io thread management > 2. Connection interface > 3. Connection pool management > 4.IO Buffer > 5.Futrue/Promise support > 6.Codec interface and TubeMQ interactive encoding > 7. Functionalization of service interface parameter settings > 8.Futrue service interface > 9.Master implementation, metadata acquisition and reading interface > 10. Consumer realization > 11. Producer Realization > 12.Client configuration > 13. Producer API package > 14. Consumer API package > Plan > Phase 1 (Available)-Implement basic functions and ensure unit test coverage > RPC support > Message consumption (pull mode) > Write message (synchronous) > Connection pool implementation-automatic reconnection of broken links, > automatic recovery of idle connections, shared according to sessionFactory > Test case and specification construction- > Phase 2 (Practical)-Realize the features of each function and be able to > adapt to a certain level of pressure measurement > Asynchronous production > Authentication and authentication && Prevent production and consumption > around the master > Accurately specify offset partition consumption > Frequency control > Consumption of multiple topics in a single group > Server filter consumption > Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, > realizing the latest function points according to priority > Inactive for more than specified minutes, mainly at the production end, such > as 3 minutes > Automatically shield the dead pixels, detect the dead pixels through the > algorithm, and automatically shield the fault Broker's data transmission > TLS > push consumption > > Featrue > 1.rpc development > Pre-research--asio development > Connection interface > Connection pool management-connection reuse, automatic reconnection of > broken links, automatic recovery of idle connections, sharing according to > sessionFactory > Streaming request support-based on serialNo > Futrue/Promise interface > Codec interface > Log > Config > Buffer > 2. Service interface development > API service interface, such as heartbeat package variable function > Request Futrue/Promise function encapsulation > Config: client, consumer, producer, Master, rpc > Message id > 3.Client > turn stop > Configuration input > Consumer API > Producer API > 4.Master > Authentication > Prevent the production and consumption around the Master: get the token from > the Master and update it to the local metadata > Metadata management: Topic, Group, Master > Master Heartbeat > 5. Consumer > User interface > Heartbeat support > pull consumption > Consumption of multiple topics in a single group > Authentication > Precisely specify offset partition consumption > 6. Producer > User interface > Simultaneous production > Asynchronous production > Load balancing algorithm: polling > Load balancing algorithm: hash > 7. Advanced features > Master disconnects and reconnects, traversing dns to obtain Master host IP > Limiting > Effectively-Once > tls:asio+openssl > Filter consumption > Inactive for more than the specified minutes, mainly at the production end, > for example 3 minutes > Fuse: Automatically shield the dead spots, detect the dead spots through the > algorithm, automatically shield the fault Broker's data transmission > Reporting time-consuming, failure; static weight (number of partitions), > dynamic weight > Connection pool management-automatic recovery of idle connections, shared > according to sessionFactory > Push consumption > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Attachment: 企业微信截图_15927950018183.png > C++ SDK support in TubeMQ > - > > Key: TUBEMQ-3 > URL: https://issues.apache.org/jira/browse/TUBEMQ-3 > Project: Apache TubeMQ > Issue Type: New Feature >Reporter: zhangguocheng >Assignee: charleli >Priority: Normal > Attachments: 企业微信截图_15927950018183.png > > > I will contribute the SDK of C + +, which is currently being sorted out. > Without changing the server-side interaction protocol, the semantics will be > the same as the Java implementation. > > Task > 1.io thread management > 2. Connection interface > 3. Connection pool management > 4.IO Buffer > 5.Futrue/Promise support > 6.Codec interface and TubeMQ interactive encoding > 7. Functionalization of service interface parameter settings > 8.Futrue service interface > 9.Master implementation, metadata acquisition and reading interface > 10. Consumer realization > 11. Producer Realization > 12.Client configuration > 13. Producer API package > 14. Consumer API package > Plan > Phase 1 (Available)-Implement basic functions and ensure unit test coverage > RPC support > Message consumption (pull mode) > Write message (synchronous) > Connection pool implementation-automatic reconnection of broken links, > automatic recovery of idle connections, shared according to sessionFactory > Test case and specification construction- > Phase 2 (Practical)-Realize the features of each function and be able to > adapt to a certain level of pressure measurement > Asynchronous production > Authentication and authentication && Prevent production and consumption > around the master > Accurately specify offset partition consumption > Frequency control > Consumption of multiple topics in a single group > Server filter consumption > Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, > realizing the latest function points according to priority > Inactive for more than specified minutes, mainly at the production end, such > as 3 minutes > Automatically shield the dead pixels, detect the dead pixels through the > algorithm, and automatically shield the fault Broker's data transmission > TLS > push consumption > > Featrue > 1.rpc development > Pre-research--asio development > Connection interface > Connection pool management-connection reuse, automatic reconnection of > broken links, automatic recovery of idle connections, sharing according to > sessionFactory > Streaming request support-based on serialNo > Futrue/Promise interface > Codec interface > Log > Config > Buffer > 2. Service interface development > API service interface, such as heartbeat package variable function > Request Futrue/Promise function encapsulation > Config: client, consumer, producer, Master, rpc > Message id > 3.Client > turn stop > Configuration input > Consumer API > Producer API > 4.Master > Authentication > Prevent the production and consumption around the Master: get the token from > the Master and update it to the local metadata > Metadata management: Topic, Group, Master > Master Heartbeat > 5. Consumer > User interface > Heartbeat support > pull consumption > Consumption of multiple topics in a single group > Authentication > Precisely specify offset partition consumption > 6. Producer > User interface > Simultaneous production > Asynchronous production > Load balancing algorithm: polling > Load balancing algorithm: hash > 7. Advanced features > Master disconnects and reconnects, traversing dns to obtain Master host IP > Limiting > Effectively-Once > tls:asio+openssl > Filter consumption > Inactive for more than the specified minutes, mainly at the production end, > for example 3 minutes > Fuse: Automatically shield the dead spots, detect the dead spots through the > algorithm, automatically shield the fault Broker's data transmission > Reporting time-consuming, failure; static weight (number of partitions), > dynamic weight > Connection pool management-automatic recovery of idle connections, shared > according to sessionFactory > Push consumption > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Description: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. !企业微信截图_15927950018183.png! Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features of each function and be able to adapt to a certain level of pressure measurement Asynchronous production Authentication and authentication && Prevent production and consumption around the master Accurately specify offset partition consumption Frequency control Consumption of multiple topics in a single group Server filter consumption Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, realizing the latest function points according to priority Inactive for more than specified minutes, mainly at the production end, such as 3 minutes Automatically shield the dead pixels, detect the dead pixels through the algorithm, and automatically shield the fault Broker's data transmission TLS push consumption Featrue 1.rpc development Pre-research--asio development Connection interface Connection pool management-connection reuse, automatic reconnection of broken links, automatic recovery of idle connections, sharing according to sessionFactory Streaming request support-based on serialNo Futrue/Promise interface Codec interface Log Config Buffer 2. Service interface development API service interface, such as heartbeat package variable function Request Futrue/Promise function encapsulation Config: client, consumer, producer, Master, rpc Message id 3.Client turn stop Configuration input Consumer API Producer API 4.Master Authentication Prevent the production and consumption around the Master: get the token from the Master and update it to the local metadata Metadata management: Topic, Group, Master Master Heartbeat 5. Consumer User interface Heartbeat support pull consumption Consumption of multiple topics in a single group Authentication Precisely specify offset partition consumption 6. Producer User interface Simultaneous production Asynchronous production Load balancing algorithm: polling Load balancing algorithm: hash 7. Advanced features Master disconnects and reconnects, traversing dns to obtain Master host IP Limiting Effectively-Once tls:asio+openssl Filter consumption Inactive for more than the specified minutes, mainly at the production end, for example 3 minutes Fuse: Automatically shield the dead spots, detect the dead spots through the algorithm, automatically shield the fault Broker's data transmission Reporting time-consuming, failure; static weight (number of partitions), dynamic weight Connection pool management-automatic recovery of idle connections, shared according to sessionFactory Push consumption was: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features of each function and be able to adapt to a certain level of pressure measurement Asynchronous production
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Description: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features of each function and be able to adapt to a certain level of pressure measurement Asynchronous production Authentication and authentication && Prevent production and consumption around the master Accurately specify offset partition consumption Frequency control Consumption of multiple topics in a single group Server filter consumption Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, realizing the latest function points according to priority Inactive for more than specified minutes, mainly at the production end, such as 3 minutes Automatically shield the dead pixels, detect the dead pixels through the algorithm, and automatically shield the fault Broker's data transmission TLS push consumption Featrue 1.rpc development Pre-research--asio development Connection interface Connection pool management-connection reuse, automatic reconnection of broken links, automatic recovery of idle connections, sharing according to sessionFactory Streaming request support-based on serialNo Futrue/Promise interface Codec interface Log Config Buffer 2. Service interface development API service interface, such as heartbeat package variable function Request Futrue/Promise function encapsulation Config: client, consumer, producer, Master, rpc Message id 3.Client turn stop Configuration input Consumer API Producer API 4.Master Authentication Prevent the production and consumption around the Master: get the token from the Master and update it to the local metadata Metadata management: Topic, Group, Master Master Heartbeat 5. Consumer User interface Heartbeat support pull consumption Consumption of multiple topics in a single group Authentication Precisely specify offset partition consumption 6. Producer User interface Simultaneous production Asynchronous production Load balancing algorithm: polling Load balancing algorithm: hash 7. Advanced features Master disconnects and reconnects, traversing dns to obtain Master host IP Limiting Effectively-Once tls:asio+openssl Filter consumption Inactive for more than the specified minutes, mainly at the production end, for example 3 minutes Fuse: Automatically shield the dead spots, detect the dead spots through the algorithm, automatically shield the fault Broker's data transmission Reporting time-consuming, failure; static weight (number of partitions), dynamic weight Connection pool management-automatic recovery of idle connections, shared according to sessionFactory Push consumption was: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features of each function and be able to adapt to a certain level of pressure measurement Asynchronous production Authentication and
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Description: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features of each function and be able to adapt to a certain level of pressure measurement Asynchronous production Authentication and authentication && Prevent production and consumption around the master Accurately specify offset partition consumption Frequency control Consumption of multiple topics in a single group Server filter consumption Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, realizing the latest function points according to priority Inactive for more than specified minutes, mainly at the production end, such as 3 minutes Automatically shield the dead pixels, detect the dead pixels through the algorithm, and automatically shield the fault Broker's data transmission TLS push consumption Featrue 1.rpc development Pre-research--asio development Connection interface Connection pool management-connection reuse, automatic reconnection of broken links, automatic recovery of idle connections, sharing according to sessionFactory Streaming request support-based on serialNo Futrue/Promise interface Codec interface Log Config Buffer 2. Service interface development API service interface, such as heartbeat package variable function Request Futrue/Promise function encapsulation Config: client, consumer, producer, Master, rpc Message id 3.Client turn stop Configuration input Consumer API Producer API 4.Master Authentication Prevent the production and consumption around the Master: get the token from the Master and update it to the local metadata Metadata management: Topic, Group, Master Master Heartbeat 5. Consumer User interface Heartbeat support pull consumption Consumption of multiple topics in a single group Authentication Precisely specify offset partition consumption 6. Producer User interface Simultaneous production Asynchronous production Load balancing algorithm: polling Load balancing algorithm: hash 7. Advanced features Master disconnects and reconnects, traversing dns to obtain Master host IP Limiting Effectively-Once tls:asio+openssl Filter consumption Inactive for more than the specified minutes, mainly at the production end, for example 3 minutes Fuse: Automatically shield the dead spots, detect the dead spots through the algorithm, automatically shield the fault Broker's data transmission Reporting time-consuming, failure; static weight (number of partitions), dynamic weight Connection pool management-automatic recovery of idle connections, shared according to sessionFactory Push consumption was: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. !file:///C:/Users/charleli/Documents/WXWork/1688851418270443/Cache/Image/2020-06/%E4%BC%81%E4%B8%9A%E5%BE%AE%E4%BF%A1%E6%88%AA%E5%9B%BE_15927950018183.png! Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Description: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features of each function and be able to adapt to a certain level of pressure measurement Asynchronous production Authentication and authentication && Prevent production and consumption around the master Accurately specify offset partition consumption Frequency control Consumption of multiple topics in a single group Server filter consumption Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, realizing the latest function points according to priority Inactive for more than specified minutes, mainly at the production end, such as 3 minutes Automatically shield the dead pixels, detect the dead pixels through the algorithm, and automatically shield the fault Broker's data transmission TLS push consumption Featrue 1.rpc development Pre-research--asio development Connection interface Connection pool management-connection reuse, automatic reconnection of broken links, automatic recovery of idle connections, sharing according to sessionFactory Streaming request support-based on serialNo Futrue/Promise interface Codec interface Log Config Buffer 2. Service interface development API service interface, such as heartbeat package variable function Request Futrue/Promise function encapsulation Config: client, consumer, producer, Master, rpc Message id 3.Client turn stop Configuration input Consumer API Producer API 4.Master Authentication Prevent the production and consumption around the Master: get the token from the Master and update it to the local metadata Metadata management: Topic, Group, Master Master Heartbeat 5. Consumer User interface Heartbeat support pull consumption Consumption of multiple topics in a single group Authentication Precisely specify offset partition consumption 6. Producer User interface Simultaneous production Asynchronous production Load balancing algorithm: polling Load balancing algorithm: hash 7. Advanced features Master disconnects and reconnects, traversing dns to obtain Master host IP Limiting Effectively-Once tls:asio+openssl Filter consumption Inactive for more than the specified minutes, mainly at the production end, for example 3 minutes Fuse: Automatically shield the dead spots, detect the dead spots through the algorithm, automatically shield the fault Broker's data transmission Reporting time-consuming, failure; static weight (number of partitions), dynamic weight Connection pool management-automatic recovery of idle connections, shared according to sessionFactory Push consumption was: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. > C++ SDK support in TubeMQ > - > > Key: TUBEMQ-3 > URL: https://issues.apache.org/jira/browse/TUBEMQ-3 > Project: Apache TubeMQ > Issue Type: New Feature >Reporter: zhangguocheng >Assignee: charleli >Priority: Normal > > I will contribute the SDK of C + +, which is currently being sorted out. > Without changing the server-side interaction protocol, the semantics will be > the same as the Java implementation. > > Task > 1.io thread management > 2. Connection interface > 3. Connection pool management > 4.IO Buffer > 5.Futrue/Promise support > 6.Codec interface and TubeMQ interactive encoding > 7. Functionalization of service interface parameter settings > 8.Futrue service interface > 9.Master implementation, metadata acquisition and reading interface > 10. Consumer realization > 11. Producer Realization > 12.Client configuration > 13. Producer API package > 14. Consumer API package > Plan > Phase 1 (Available)-Implement basic
[jira] [Updated] (TUBEMQ-3) C++ SDK support in TubeMQ
[ https://issues.apache.org/jira/browse/TUBEMQ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] charleli updated TUBEMQ-3: -- Description: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. !file:///C:/Users/charleli/Documents/WXWork/1688851418270443/Cache/Image/2020-06/%E4%BC%81%E4%B8%9A%E5%BE%AE%E4%BF%A1%E6%88%AA%E5%9B%BE_15927950018183.png! Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features of each function and be able to adapt to a certain level of pressure measurement Asynchronous production Authentication and authentication && Prevent production and consumption around the master Accurately specify offset partition consumption Frequency control Consumption of multiple topics in a single group Server filter consumption Phase 3 (Easy to use)-Continuous iteration, full-featured implementation, realizing the latest function points according to priority Inactive for more than specified minutes, mainly at the production end, such as 3 minutes Automatically shield the dead pixels, detect the dead pixels through the algorithm, and automatically shield the fault Broker's data transmission TLS push consumption Featrue 1.rpc development Pre-research--asio development Connection interface Connection pool management-connection reuse, automatic reconnection of broken links, automatic recovery of idle connections, sharing according to sessionFactory Streaming request support-based on serialNo Futrue/Promise interface Codec interface Log Config Buffer 2. Service interface development API service interface, such as heartbeat package variable function Request Futrue/Promise function encapsulation Config: client, consumer, producer, Master, rpc Message id 3.Client turn stop Configuration input Consumer API Producer API 4.Master Authentication Prevent the production and consumption around the Master: get the token from the Master and update it to the local metadata Metadata management: Topic, Group, Master Master Heartbeat 5. Consumer User interface Heartbeat support pull consumption Consumption of multiple topics in a single group Authentication Precisely specify offset partition consumption 6. Producer User interface Simultaneous production Asynchronous production Load balancing algorithm: polling Load balancing algorithm: hash 7. Advanced features Master disconnects and reconnects, traversing dns to obtain Master host IP Limiting Effectively-Once tls:asio+openssl Filter consumption Inactive for more than the specified minutes, mainly at the production end, for example 3 minutes Fuse: Automatically shield the dead spots, detect the dead spots through the algorithm, automatically shield the fault Broker's data transmission Reporting time-consuming, failure; static weight (number of partitions), dynamic weight Connection pool management-automatic recovery of idle connections, shared according to sessionFactory Push consumption was: I will contribute the SDK of C + +, which is currently being sorted out. Without changing the server-side interaction protocol, the semantics will be the same as the Java implementation. Task 1.io thread management 2. Connection interface 3. Connection pool management 4.IO Buffer 5.Futrue/Promise support 6.Codec interface and TubeMQ interactive encoding 7. Functionalization of service interface parameter settings 8.Futrue service interface 9.Master implementation, metadata acquisition and reading interface 10. Consumer realization 11. Producer Realization 12.Client configuration 13. Producer API package 14. Consumer API package Plan Phase 1 (Available)-Implement basic functions and ensure unit test coverage RPC support Message consumption (pull mode) Write message (synchronous) Connection pool implementation-automatic reconnection of broken links, automatic recovery of idle connections, shared according to sessionFactory Test case and specification construction- Phase 2 (Practical)-Realize the features
