New logo, updating examples and some code (#36)

Author: akshaisarma

docs/about/contact.md

@@ -12,7 +12,10 @@ If you have any issues with any of the particular Bullet sub-components, feel fr
 | UI            | [https://github.com/bullet-db/bullet-ui/issues](https://github.com/bullet-db/bullet-ui/issues)                     |
 | Record        | [https://github.com/bullet-db/bullet-record/issues](https://github.com/bullet-db/bullet-record/issues)             |
 | Core          | [https://github.com/bullet-db/bullet-core/issues](https://github.com/bullet-db/bullet-core/issues)                 |
+| DSL           | [https://github.com/bullet-db/bullet-dsl/issues](https://github.com/bullet-db/bullet-dsl/issues)                   |
+| BQL           | [https://github.com/bullet-db/bullet-bql/issues](https://github.com/bullet-db/bullet-bql/issues)                   |
 | Kafka PubSub  | [https://github.com/bullet-db/bullet-kafka/issues](https://github.com/bullet-db/bullet-kafka/issues)               |
+| Pulsar PubSub | [https://github.com/bullet-db/bullet-pulsar/issues](https://github.com/bullet-db/bullet-pulsar/issues)             |
 | Documentation | [https://github.com/bullet-db/bullet-db.github.io/issues](https://github.com/bullet-db/bullet-db.github.io/issues) |
 
 ## Mailing Lists

docs/apidocs/bullet-service/0.5.0/index.html

@@ -0,0 +1 @@
+Replace me with the real documentation.

docs/backend/storm-performance.md

@@ -29,6 +29,10 @@ Using the pluggable metrics interface in Bullet on Storm, we captured worker lev
 
 See [0.3.0](https://github.com/bullet-db/bullet-storm/releases/tag/bullet-storm-0.3.0) for how to plug in your own metrics collection.
 
+!!!note "Old Version of Bullet"
+
+    This was tested with a relatively old version of Bullet Storm and has not been updated since. With the latest changes in Storm, Bullet Storm, using a proper PubSub, and partitioning in Bullet Core, the performance is actually a lot better. However, the point of this performance section is to simply conclude that (Spoilers Ahead) scaling out is pretty linear and queries mostly fit into the overhead of reading the data when the simultaneous queries desired is in the hundreds.
+
 ### Tools used
 
   * [jq](https://stedolan.github.io/jq/) - a nice tool to parse Bullet JSON responses
@@ -573,15 +577,15 @@ The following table summarizes the results:
 
 The following figure summarizes the minimum number of CPU cores (which are also the number of Filter Bolts) needed to support the the maximum number of ```RAW``` queries with latency < 200 ms.
 
-#### Figure 15. Data Volume vs Memory
+#### Figure 15. CPU vs Max Concurrent Queries
 
 ![Queries](../img/queries-cpu.png)
 
 This shows that the queries supported also scale pretty linearly.
 
 You may have noticed how when latency starts to increase, it increases pretty rapidly. This suggests that there is a *knee* or *exponential* curve for latency. The following figure shows this in the graph of the latency for queries with ```20``` Filter Bolts.
 
-#### Figure 16. Data Volume vs Memory
+#### Figure 16. Max Concurrent Queries vs Latency
 
 ![Queries](../img/queries-20-fb.png)
 

docs/css/extra.css

@@ -1,3 +1,12 @@
+#bullet-logo-wrapper {
+  text-align: center;
+  margin-bottom: 30px;
+}
+
+#bullet-logo {
+  height: 200px;
+}
+
 .navbar-brand > .small-brand-text {
   margin-left: 5px;
   font-size: 50%;

docs/img/bullet-logo.png

@@ -1,4 +1,5 @@
-  ![Bullet](../img/bullet-logo.png)
+![Bullet](../img/bullet-logo.svg){: #bullet-logo}
+{: #bullet-logo-wrapper}
 
 * A real-time query engine for very large data streams
 

docs/img/bullet-logo.svg

@@ -37,7 +37,7 @@ mkdir -p $BULLET_HOME/pubsub
 mkdir -p $BULLET_HOME/service
 mkdir -p $BULLET_HOME/ui
 cd $BULLET_HOME
-curl -LO https://github.com/bullet-db/bullet-db.github.io/releases/download/v0.6.0/examples_artifacts.tar.gz
+curl -LO https://github.com/bullet-db/bullet-db.github.io/releases/download/v0.6.1/examples_artifacts.tar.gz
 tar -xzf examples_artifacts.tar.gz
 export BULLET_EXAMPLES=$BULLET_HOME/bullet-examples
 ```
@@ -96,7 +96,7 @@ tar -xzf spark-2.2.1-bin-hadoop2.7.tgz
 
 ```bash
 cp $BULLET_HOME/bullet-examples/backend/spark/* $BULLET_SPARK
-curl -Lo bullet-spark.jar http://jcenter.bintray.com/com/yahoo/bullet/bullet-spark/0.2.1/bullet-spark-0.2.1-standalone.jar
+curl -Lo bullet-spark.jar http://jcenter.bintray.com/com/yahoo/bullet/bullet-spark/0.2.2/bullet-spark-0.2.2-standalone.jar
 ```
 
 #### Step 8: Launch the Bullet Spark Backend
@@ -174,8 +174,8 @@ nvm use v6.9.4
 #### Step 13: Install the Bullet UI
 
 ```bash
-curl -LO https://github.com/bullet-db/bullet-ui/releases/download/v0.6.1/bullet-ui-v0.6.1.tar.gz
-tar -xzf bullet-ui-v0.6.1.tar.gz
+curl -LO https://github.com/bullet-db/bullet-ui/releases/download/v0.6.2/bullet-ui-v0.6.2.tar.gz
+tar -xzf bullet-ui-v0.6.2.tar.gz
 cp $BULLET_EXAMPLES/ui/env-settings.json config/
 ```
 

docs/img/favicon.ico

@@ -7,13 +7,13 @@ At the end of this section, you will have:
   * Setup the Bullet topology using a custom spout on [bullet-storm-0.8.5](https://github.com/bullet-db/bullet-storm/releases/tag/bullet-storm-0.8.5)
   * Setup the [Web Service](../ws/setup.md) talking to the topology and serving a schema for your UI using [bullet-service-0.4.3](https://github.com/bullet-db/bullet-service/releases/tag/bullet-service-0.4.3)
   * Setup the [REST PubSub](../pubsub/rest.md) talking to the topology and Web Service using [bullet-core-0.6.4](https://github.com/bullet-db/bullet-core/releases/tag/bullet-core-0.6.4).
-  * Setup the [UI](../ui/setup.md) talking to the Web Service using [bullet-ui-0.6.1](https://github.com/bullet-db/bullet-ui/releases/tag/v0.6.1)
+  * Setup the [UI](../ui/setup.md) talking to the Web Service using [bullet-ui-0.6.2](https://github.com/bullet-db/bullet-ui/releases/tag/v0.6.2)
 
 **Prerequisites**
 
   * You will need to be on an Unix-based system (Mac OS X, Ubuntu ...) with ```curl``` installed
   * You will need [JDK 8](http://www.oracle.com/technetwork/java/javase/downloads/index.html) installed
-  * You will need enough CPU and RAM on your machine to run about 8-10 JVMs in ```server``` mode. You should have at least 2 GB free space on your disk. We will be setting up a Storm cluster with multiple components, a couple of Jetty instances and a Node server.
+  * You will need enough CPU and RAM on your machine to run about 8-10 JVMs in ```server``` mode. You should have at least 2 GB free space on your disk. We will be setting up a Storm cluster with multiple components, an embedded Tomcat server and a Node server.
 
 ## Install Script
 
@@ -43,7 +43,7 @@ mkdir -p $BULLET_HOME/backend/storm
 mkdir -p $BULLET_HOME/service
 mkdir -p $BULLET_HOME/ui
 cd $BULLET_HOME
-curl -LO https://github.com/bullet-db/bullet-db.github.io/releases/download/v0.6.0/examples_artifacts.tar.gz
+curl -LO https://github.com/bullet-db/bullet-db.github.io/releases/download/v0.6.1/examples_artifacts.tar.gz
 tar -xzf examples_artifacts.tar.gz
 export BULLET_EXAMPLES=$BULLET_HOME/bullet-examples
 ```
@@ -168,8 +168,8 @@ nvm use v6.9.4
 
 ```bash
 cd $BULLET_HOME/ui
-curl -LO https://github.com/bullet-db/bullet-ui/releases/download/src/bullet-ui-v0.6.1.tar.gz
-tar -xzf bullet-ui-v0.6.1.tar.gz
+curl -LO https://github.com/bullet-db/bullet-ui/releases/download/src/bullet-ui-v0.6.2.tar.gz
+tar -xzf bullet-ui-v0.6.2.tar.gz
 cp $BULLET_EXAMPLES/ui/env-settings.json config/
 ```
 
@@ -204,7 +204,7 @@ If you were performing the steps yourself, you can also manually cleanup **all t
 | UI             | ```pkill -f [e]xpress-server.js```                               |
 | Web Service    | ```pkill -f [e]xample_rest_pubsub_config.yaml```                      |
 | Storm          | ```pkill -f [a]pache-storm-1.2.2```                              |
-| File System    | ```rm -rf $BULLET_HOME /tmp/dev-storm-zookeeper /tmp/jetty-*```  |
+| File System    | ```rm -rf $BULLET_HOME /tmp/dev-storm-zookeeper```  |
 
 This does *not* delete ```$HOME/.nvm``` and some extra lines nvm may have added to your ```$HOME/{.profile, .bash_profile, .zshrc, .bashrc}```.