As of January 31, 2021, this tutorial references legacy products that no longer represent Cloudera’s current product offerings.
Please visit recommended tutorials:
- How to Create a CDP Private Cloud Base Development Cluster
- All Cloudera Data Platform (CDP) related tutorials
Let's walk through the demo and get an understanding for the data pipeline before we dive deeper into Storm internals.
- Environment Setup
- Generate Sensor Data
- Deploy the Storm Topology
- Verify the Processed Data
- Next: Building a Storm Topology
SSH into your Cloudera DataFlow (CDF) environment and download the corresponding demo project.
git clone https://github.com/orendain/trucking-iot-demo-storm-on-scala cd trucking-iot-demo-storm-on-scala
The demo application leverages a very robust data simulator, which generates data of two types and publishes them to Kafka topics as a CSV string.
EnrichedTruckData: Data simulated by sensors onboard each truck. For the purposes of this demo, this data has been pre-enriched with data from a weather service.
1488767711734|26|1|Edgar Orendain|107|Springfield to Kansas City Via Columbia|38.95940879245423|-92.21923828125|65|Speeding|1|0|1|60
TrafficData: Data simulated from an online traffic service, which reports on traffic congestion on any particular trucking route.
Start the data generator by executing the appropriate script:
Let's wait for the simulator to finish generating data. Once that's done, we can look at the data that was generated and stored in Kafka:
Note: "Ctrl + c" to exit out from the Kafka command.
/usr/hdf/current/kafka-broker/bin/kafka-console-consumer.sh --bootstrap-server sandbox-hdf.hortonworks.com:6667 --from-beginning --topic trucking_data_truck_enriched
/usr/hdf/current/kafka-broker/bin/kafka-console-consumer.sh --bootstrap-server sandbox-hdf.hortonworks.com:6667 --from-beginning --topic trucking_data_traffic
With simulated data now being pumped into Kafka topics, we power up Storm and process this data. In a separate terminal window, run the following command:
Note: We'll cover what exactly a "topology" is in the next section.
Here is a slightly more in-depth look at the steps Storm is taking in processing and transforming the two types of simulated data from above.
With the data now fully processed by Storm and published back into accessible Kafka topics, it's time to verify our handiwork. Run the following command to list the joined set of data.
/usr/hdf/current/kafka-broker/bin/kafka-console-consumer.sh --bootstrap-server sandbox-hdf.hortonworks.com:6667 --from-beginning --topic trucking_data_joined
Nice! Our topology joined data from two separate streams of data.
Now that we know how Storm fits into this data pipeline and what type of work it is performing, let's dive into the actual code and see exactly how it is built.