You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -125,7 +125,7 @@ Visit the UI and see if the topology is up. You should see the ```DataSource```
125
125
126
126
!!! note "Where is this data coming from?"
127
127
128
-
This data is randomly generated by the [custom Storm spout](https://github.com/bullet-db/bullet-db.github.io/blob/src/examples/storm/src/main/java/com/yahoo/bullet/storm/examples/RandomSpout.java) that is in the example topology you just launched. In practice, your spout would read from an actual data source such as Kafka instead. See [below](#storm-topology) for more details about this random data spout.
128
+
This data is randomly generated by the [custom Storm spout](https://github.com/bullet-db/bullet-db.github.io/blob/src/examples/storm/src/main/java/com/yahoo/bullet/storm/examples/RandomSpout.java) that is in the example topology you just launched. In practice, your spout would read from an actual data source such as Kafka etc. See [below](#storm-topology) for more details about this random data spout.
129
129
130
130
### Setting up the Bullet Web Service
131
131
@@ -271,43 +271,47 @@ This method above emits the tuples. The Storm framework calls this method. This
271
271
When the spout emits the randomly generated tuple, it attaches a ```DUMMY_ID``` to it. In Storm terms, this is a message ID. By adding a message ID, this tuple can be made to flow reliably. The Bullet component that receives this tuple (Filter bolt) acknowledges or "acks" this tuple. If the tuple did not make it to Filter bolt within a configured timeout window, Storm will call a ```fail(Object messageId)``` method on the spout. This particular spout does not define one and hence the usage of a ```DUMMY_ID```. If your source of data can identify records uniquely and you can re-emit them on a fail, you should attach that actual ID in place of the ```DUMMY_ID```.
This method generates some fields randomly and inserts them into a BulletRecord. Note that the BulletRecord is typed and all data must be inserted with the proper types.
314
+
This ```generateRecord```method generates some fields randomly and inserts them into a BulletRecord. Note that the BulletRecord is typed and all data must be inserted with the proper types.
311
315
312
316
If you put Bullet on your data, you will need to write a Spout (or a topology if your reading is complex), that reads from your data source and emits BulletRecords with the fields you wish to be query-able placed into a BulletRecord similar to this example.
Copy file name to clipboardExpand all lines: docs/ui/usage.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,10 @@
2
2
3
3
The UI should (hopefully) be self-explanatory. Any particular section that requires additional information has the  icon next to it. Clicking this will display information relevant to that section.
4
4
5
-
The interactions in this page are running on the topology that was set up in the [Quick Start on Storm](../quick-start/storm.md). Recall that the example backend is configured to produce *20 data records every 101 ms.*.
5
+
The interactions in this page are running on the topology that was set up in the [Quick Start on Storm](../quick-start/storm.md). Recall that that example backend is configured to produce *20 data records every 101 ms.*.
6
6
7
7
!!! note "NOTE: Some of these videos use an old version of the Bullet UI"
8
-
We are currently in progress adding new videos with windowing, etc.
8
+
We are currently in progress adding new videos with windowing and other new features from the latest UI version etc.
# Remove this 88 - THIS STILL NEEDS to be implemented - download the thing (it's not available online yet because we haven't released this version yet):
182
-
# Something like this: curl -Lo bullet-spark.jar http://jcenter.bintray.com/com/yahoo/bullet/bullet-spark/0.1.1/bullet-spark-0.1.1-standalone.jar
183
-
}
184
-
185
180
launch_bullet_spark() {
181
+
local BULLET_KAFKA_JAR=bullet-kafka-${BULLET_KAFKA_VERSION}-fat.jar
182
+
183
+
println "Copying Bullet Spark configuration and artifacts..."
# <------------- Remove this 88 - the above line needs to be uncommented and all the below stuff should be removed once this artifact actualy exists on the git cloud or whatever
tar -xzf "${BULLET_DOWNLOADS}/examples_artifacts.tar.gz" -C "${BULLET_HOME}"# <------------ Remove this 88 - remove this line and the one above it once the artifact is actulaly on github
291
+
install_bullet_examples
296
292
297
293
install_kafka
298
294
install_bullet_kafka
299
295
launch_kafka
300
296
create_topics
301
297
302
-
install_web_service
303
-
launch_web_service
304
-
305
298
install_spark
306
-
# install_bullet_spark
307
-
# <------------- Remove this 88 - the above line needs to be uncommented and all the below stuff should be removed once this artifact actualy exists on the git cloud or whatever
308
-
cp $BULLET_HOME/bullet-examples/backend/spark/*$BULLET_SPARK# <------------ Remove this 88
309
-
cp ~/bullet/bullet-spark/target/bullet-spark-0.1.1-SNAPSHOT-standalone.jar $BULLET_SPARK/bullet-spark.jar # <------------ Remove this 88
310
-
311
299
launch_bullet_spark
312
300
313
-
# Remove this 88 - deal with the following two lines:
314
-
# Now do the UI stuff once the new UI is ready
315
-
# ALSO - DON'T FORGET! The teardown stuff doesn't work unless you run the whole script (the "else" block at the bottom won't work) because the KAFKA_DIR isn't defined unless you run install_kafka function) - so fix that somehow
316
-
317
-
318
-
319
-
320
-
301
+
install_web_service
302
+
launch_web_service
321
303
322
-
#install_node
323
-
#launch_bullet_ui
304
+
install_node
305
+
launch_bullet_ui
324
306
325
-
#println "All components launched! Visit http://localhost:8800 (default) for the UI"
326
-
#unset_all
307
+
println "All components launched! Visit http://localhost:8800 (default) for the UI"
0 commit comments