hyperscaledesignhub opened a new pull request, #8:
URL: https://github.com/apache/fluss-benchmarks/pull/8

   <!--
   *Thank you very much for contributing to Fluss - we are happy that you want 
to help us improve Fluss. To help the community review your contribution in the 
best possible way, please go through the checklist below, which will get the 
contribution into a shape in which it can be best reviewed.*
   
   ## Contribution Checklist
   
     - Make sure that the pull request corresponds to a: 
https://github.com/apache/fluss-benchmarks/issues/7
   
     - Name the pull request in the format "[component] Title of the pull 
request", where *[component]* should be replaced by the name of the component 
being changed. Typically, this corresponds to the component label assigned to 
the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are 
unsure about which is the best component.
   
     - Fill out the template below to describe the changes contributed by the 
pull request. That will give reviewers the context they need to do the review.
   
     - Make sure that the change passes the automated tests, i.e., `mvn clean 
verify` passes.
   
     - Each pull request should address only one issue, not mix up code from 
multiple issues.
   
   
   **(The sections below can be removed for hotfixes or typos)**
   -->
   
   ### Purpose
   
   <!-- Linking this pull request to the issue -->
   Linked issue: NA
   
   This pull request is for creating end to end fluss benchmark for IOT case 
where complete realtime IOT system that is inserting 2 million rows/sec into 
apache fluss and   flink job is consuming and aggregating the data from fluss 
in realtime
    
   ### Brief change log
   
   complete end to end system. Which can be deployed in AWS and create the 
platform and stress the platform with 2 million rows/sec
   
   ### Tests
   
   NA
   
   ### API and Format
   NA
   
   ### Documentation
   
   NA
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to