aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCody Hiar <cody@hiar.ca>2021-10-25 15:36:41 -0600
committerCody Hiar <cody@hiar.ca>2021-10-25 15:36:41 -0600
commit3cc0989bcf229b04d08a16d925d81e536e72b53d (patch)
treecc6a4919e3126a43eaa2ad4d8850c41a733ad0b7
parente3d2ffca585660f0c088ab8323bfe78a86ba75e3 (diff)
Updating readmeHEADmaster
-rw-r--r--README.md27
1 files changed, 24 insertions, 3 deletions
diff --git a/README.md b/README.md
index 903e0db..eca2c64 100644
--- a/README.md
+++ b/README.md
@@ -1,13 +1,32 @@
# Dockerized Apache Storm
-To run the `wordcount` project:
+To create a jar and submit to storm:
```
-make up && make enter
+make enter
cd wordcount
-sparse run
+mvn clean compile package
+exit
+
+make enter_nimbus
+cd /usr/src/app/wordcount/target
+storm jar WordCount-1.0-SNAPSHOT.jar org.apache.storm.flux.Flux -r -R /topology.yaml
```
+The backend and nimbus containers both mount the local directory to access
+files. The sample wordcount is just [Azure-Samples/hdinsight-python-storm-wordcount][1]
+with `storm.version` updated in pom.xml. The project is set up to give you a
+full jar that you can submit to storm.
+
+## Experimenting with streamparse
+
+I also experimented with creating a streamparse example but the tricky part is
+that streamparse won't generate a jar containing the topology definition
+because it submits the topology information via thrift. This means I'd need to
+set up inter-container communication so I just decided to use the above
+solution to generate a jar. If you want to use streamparse there are a few
+little notes below to help you get around some issues that I ran into.
+
## How did I get here?
Setting up a sample project with Apache Storm using streamparse. The
@@ -36,3 +55,5 @@ Updated these versions to match my local storm version
```
Adding the snippet above to my project.clj seemed to fix this issue
+
+[1]: https://github.com/Azure-Samples/hdinsight-python-storm-wordcount