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

RJ Nowling commented on BIGTOP-1744:
------------------------------------

I was able to successfully:

1. Create a fat jar and run the transaction queue from the fat jar
2. Built a distribution zip, create a Docker container, and run the generator 
from the Docker container
3. Run tests

Comments:

1. Jar name on lines 65 and 79 of the README should be 
bigpetstore-transaction-queue-all-1.0.jar, not 
bigpetstore-transaction-queue-1.0.jar
2. On line 79 of the README, can we use the more succinct java -jar ... instead 
of the more verbose java -cp ... ?
3. One lines 60 and 74 of the README, the path to the binary should 
/opt/bigpetstore-transaction-queue-1.0/bin/bigpetstore-transaction-queue not 
/opt/bigpetstore-transaction-queue

Once the README is updated, I can give a +1


> 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
>         Attachments: 13.patch
>
>
> 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