Skip to content

Commit 09198c1

Browse files
committed
docs: text adaptions
1 parent 311ce14 commit 09198c1

2 files changed

Lines changed: 17 additions & 21 deletions

File tree

docs/modules/demos/pages/nifi-kafka-druid-earthquake-data.adoc

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,6 @@ $ stackablectl stacklet list
7272
│ kafka ┆ kafka ┆ default ┆ broker-default-0-listener-broker-kafka-tls 172.19.0.4:32321 ┆ Available, Reconciling, Running │
7373
│ ┆ ┆ ┆ broker-default-0-listener-broker-metrics 172.19.0.4:30556 ┆ │
7474
│ ┆ ┆ ┆ broker-default-bootstrap-kafka-tls 172.19.0.4:31352 ┆ │
75-
│ ┆ ┆ ┆ broker-default-bootstrap-metrics 172.19.0.4:30241 ┆ │
7675
├╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
7776
│ nifi ┆ nifi ┆ default ┆ node-https https://172.19.0.2:32348 ┆ Available, Reconciling, Running │
7877
├╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
@@ -213,8 +212,8 @@ image::nifi-kafka-druid-earthquake-data/nifi_2.png[]
213212

214213
You can see the started ProcessGroup consisting of three processors.
215214
The first one - `InvokeHTTP`, fetches the CSV file from the Internet and puts it into the queue of the next processor.
216-
The second processor - `SplitRecords`, takes the single FlowFile (NiFi Record) which contains all CSV records and splits it into chunks of 2000 records, which are then separately put into the queue of the next processor.
217-
The third one - `PublishKafkaRecord`, parses the CSV chunk, converts it to JSON records and writes them out into Kafka.
215+
The second processor - `SplitRecord`, takes the single FlowFile (NiFi Record) which contains all CSV records and splits it into chunks of 2000 records, which are then separately put into the queue of the next processor.
216+
The third one - `PublishKafka`, parses the CSV chunk, converts it to JSON records and writes them out into Kafka.
218217

219218
Double-click on the `InvokeHTTP` processor to show the processor details.
220219

@@ -265,8 +264,8 @@ You can see the available data sources by clicking on `Datasources` at the top.
265264

266265
image::nifi-kafka-druid-earthquake-data/druid_4.png[]
267266

268-
You can see the data source's segments by clicking on `segments` under `Availability` for the `earthquake` data source.
269-
In this case, the `earthquake` data source is partitioned by the year of the earthquakes, resulting in 73 segments.
267+
You can see the data source's segments by clicking on `segments` under `Availability` for the `earthquakes` data source.
268+
In this case, the `earthquakes` data source is partitioned by the year of the earthquakes, resulting in 73 segments.
270269

271270
image::nifi-kafka-druid-earthquake-data/druid_5.png[]
272271

docs/modules/demos/pages/nifi-kafka-druid-water-level-data.adoc

Lines changed: 13 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,6 @@ $ stackablectl stacklet list
7777
│ kafka ┆ kafka ┆ default ┆ broker-default-0-listener-broker-kafka-tls 172.19.0.3:31041 ┆ Available, Reconciling, Running │
7878
│ ┆ ┆ ┆ broker-default-0-listener-broker-metrics 172.19.0.3:31503 ┆ │
7979
│ ┆ ┆ ┆ broker-default-bootstrap-kafka-tls 172.19.0.3:30793 ┆ │
80-
│ ┆ ┆ ┆ broker-default-bootstrap-metrics 172.19.0.3:32540 ┆ │
8180
├╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
8281
│ nifi ┆ nifi ┆ default ┆ node-https https://172.19.0.6:32038 ┆ Available, Reconciling, Running │
8382
├╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┼╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
@@ -111,7 +110,7 @@ You can execute a command on the Kafka broker to list the available topics as fo
111110

112111
[source,console]
113112
----
114-
$ kubectl k exec kafka-broker-default-0 -c kafka -- \
113+
$ kubectl exec kafka-broker-default-0 -c kafka -- \
115114
/stackable/kafka/bin/kafka-topics.sh \
116115
--describe \
117116
--bootstrap-server kafka-broker-default-headless.default.svc.cluster.local:9093 \
@@ -259,9 +258,8 @@ network traffic and storage usage. The solution is only to send a station's know
259258
process is called data normalization. The downside is that when analyzing the data, you need to combine the records from
260259
multiple tables in Druid (`stations` and `measurements`).
261260

262-
If you are interested in how many records have been produced to the Kafka topic so far, use the following command. It
263-
will print the last record produced to the topic partition, formatted with the pattern specified in the `-f` parameter.
264-
The given pattern will print some metadata of the record.
261+
If you are interested in how many records have been produced to the Kafka topic so far, use the following command.
262+
It prints the current offset for each partition, which tells you how many records have been produced to it.
265263

266264
[source,console]
267265
----
@@ -281,7 +279,7 @@ measurements:6:1344362
281279
measurements:7:1369651
282280
----
283281

284-
Multiplying `1,324,098` records by `8` partitions, we end up with ~ 10,592,784 records.
282+
Summing all partition offsets gives the total number of records produced. In this example, that is roughly 10.9 million measurement records.
285283

286284
To inspect the last produced records, use the following command. Here, we consume the last three records from partition
287285
`0` of the `measurements` topic.
@@ -296,7 +294,7 @@ $ kubectl exec kafka-broker-default-0 -c kafka -- \
296294
--offset latest \
297295
--partition 0 \
298296
--max-messages 3
299-
-...
297+
...
300298
{"timestamp":"2025-10-21T11:00:00+02:00","value":369.54,"station_uuid":"5cdc6555-87d7-4fcd-834d-cbbe24c9d08b"}
301299
{"timestamp":"2025-10-21T11:15:00+02:00","value":369.54,"station_uuid":"5cdc6555-87d7-4fcd-834d-cbbe24c9d08b"}
302300
{"timestamp":"2025-10-21T11:00:00+02:00","value":8.0,"station_uuid":"7deedc21-2878-40cc-ab47-f6da0d9002f1"}
@@ -502,19 +500,18 @@ effect.
502500

503501
image::nifi-kafka-druid-water-level-data/superset_6.png[]
504502

505-
// Comment out the next section as long as the mapbox api key is not active.
506-
// === View the Station Distribution on the World Map
503+
=== View the Station Distribution on the World Map
507504

508-
// To look at the stations' geographical distribution, you have to click on the tab `Charts` at the top again. Afterwards,
509-
// click on the chart `Stations distribution`.
505+
To look at the stations' geographical distribution, you have to click on the tab `Charts` at the top again. Afterwards,
506+
click on the chart `Stations distribution`.
510507

511-
// image::nifi-kafka-druid-water-level-data/superset_7.png[]
508+
image::nifi-kafka-druid-water-level-data/superset_7.png[]
512509

513-
// The stations are, of course, placed alongside waterways. They are coloured by the waters they measure, so all stations
514-
// alongside a body of water have the same colour. You can move and zoom the map with your mouse to interactively explore
515-
// the map. You can, e.g. have a detailed look at the water https://en.wikipedia.org/wiki/Rhine[Rhein].
510+
The stations are, of course, placed alongside waterways. They are coloured by the waters they measure, so all stations
511+
alongside a body of water have the same colour. You can move and zoom the map with your mouse to interactively explore
512+
the map. You can, e.g. have a detailed look at the water https://en.wikipedia.org/wiki/Rhine[Rhein].
516513

517-
// image::nifi-kafka-druid-water-level-data/superset_8.png[]
514+
image::nifi-kafka-druid-water-level-data/superset_8.png[]
518515

519516
=== Execute arbitrary SQL statements
520517

0 commit comments

Comments
 (0)