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

ASF GitHub Bot commented on BIGTOP-1744:
----------------------------------------

Github user rnowling commented on a diff in the pull request:

    https://github.com/apache/bigtop/pull/13#discussion_r26142986
  
    --- Diff: bigtop-bigpetstore/bigpetstore-transaction-queue/README.md ---
    @@ -0,0 +1,147 @@
    +# BigPetStore transaction queue #
    +
    +This is a rotating queue for Apache BigTop which uses the BigPetStore 
libraries to generate realistic streaming transactional data.
    +
    +It runs infinitely as a single java process, repeatedly re running itself 
every time a simulation is done.  
    +
    +It is a part of the BigPetStore ecosystem of projects which Apache BigTop 
leverages for real world validation of the stack.
    +
    +# I'm in a hude rush, how do I use it? #
    --- End diff --
    
    s/hude/huge/


> Add BigPigPetstore File and REST Load Generation.
> -------------------------------------------------
>
>                 Key: BIGTOP-1744
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1744
>             Project: Bigtop
>          Issue Type: New Feature
>          Components: blueprints
>            Reporter: jay vyas
>
> We have an example of using BPS to generate data for spark.
> A more realistic thing, however, which is increasingly important, is 
> streaming data.
> So, I would like to now add in 
> https://github.com/jayunit100/PetStoreLoadGenerator/ as a direct project 
> inside the {{bigtop-bigpetstore}} repository.  Its essentially a way to  
> generate (1) HTTP load or (2) Disk load using the existing BigPetStore data 
> generation algorithm.
> Im tagging this as 0.9, because I think its a great feature to release with.  
>   I can create a patch this week.  It will be a good way, for example, to do 
> scale tests of flume and kafka.
> Open to ideas/opinions on this. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to